dudeman Posted August 20, 2003 Posted August 20, 2003 I've uploaded the tar file to my archive_in folder with chmod of 666. I then log in to my admincp, and I clicked Skins & Template -> Import Skin files. The problem is I don't see the file I'd uploaded. Is the permission wrong? Am I missing some other file(s)? What am I doing wrong? -dudeman Quote
Twisted Posted August 20, 2003 Posted August 20, 2003 I have the same problem with my IPB v1.2. I contacted IPB about it and they won't do a thing to fix it. Quote
borfast Posted August 20, 2003 Posted August 20, 2003 Should Invision do anything to fix it? I mean, is there something to fix? Have they told you that it is indeed a problem with IPB and they won't fix it or have you posted something on their forums and haven't got an answer yet? Note that these are two completely different things. If it's a bug, I'm sure Invision Power Services will correct it and post a patch. If it's not a bug but something you're doing wrong, you should post some more details about what you did and hope that someone will know what you're doing wrong. And note that Invision Power Services has discontinued their free support to IPB users: http://forums.invisionpower.com/index.php?...=ST&f=1&t=82460 Now if you want IPB support from Invision Power Services you have to pay, so it's not strange if you don't have an official response from them. Quote
dudeman Posted August 20, 2003 Author Posted August 20, 2003 Status: Resolved Remedy: 1.) FTP the tar file to your forum folder, e.g. /public_html/forum/archive_in. DO NOT put the tar under /public_html/archive_in. The admincp will not pick it up from there. 2.) chmod the tar to 755. 3.) chmod the following folders to 777: ..... /public_html/forum/Skin ..... /public_html/forum/archive_in ..... /public_html/forum/style_images 4.) Log in to admincp on your forum. Make sure it's an account with admin privileges. 5.) On the left navigation menu, click 'Skins & Templates' -> 'Import Skin files'. You should see the skin name you uploaded in Step 1. 6.) For safety sake, chmod the folder in Step 3 to 755. That's it. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.