3.5.2 upgrade showing "Your config.xml is writable"

Originally Posted by Brian Cummiskey

If you get stuck on "please wait..." it's likely hit an error via the ajax command.

Make sure all files have been uploaded correctly and that the setting you are changing holds a valid value.

You should be 666 for writable and 444 to lock it down from the sounds of it.

Brian, do you think the error lies in one of the vbseo js files? I haven't made any manual code modifications. I'm running CentOS 5.5, I did a complete reinstall about 2 days ago, however the problem I mentioned predates this. Would it be easiest to just reinstall or replace the vbseo files on my server? If I backup my settings I won't lose anything, correct?

Yes, please re-upload all js and css files from the resources/ subfilder again with over-write. No need to re-upload the config file (thus, no settings will be over-written)

If after this you still have the same problem, please open a ticket with what you are trying to save for further troubleshooting.

Originally Posted by darren1981

Hi,

Ive just upgraded to 3.5.2 and followed the steps correctly to upgrade... everything seems to be in order... however the VBSEO admincp is showing a "Notice" saying the following:



Now i have set the permissions to "644" as instructed in the readme of the vbseo 3.5.2 package.. however the notice is still saying the config file is writable ?

Please advise me on what i should do.

Regards, Darren

Same for me at vBSEO 3.6.0 GOLD. Anyway - 444 does the Job.

I just want to note for the record I also had this error since the last time (before this) I upgraded. I've never heard of having to chmod to 444 before. I think you need to make the error message a little clearer because at the moment it is confusing/scaring the hell out of people and you're just passing the blame onto the web host. Surely the number of people with this problem and the diverse range of webhosts this covers shows this is an issue with your software? No other software from VBulletin to Wordpress has ever had this issue on my server and has been happy with a file permission of 644.

vBSEO also don't have any issue with leaving permission as 644 . However if your webserver have privilidges to update files when they are set 644 , this holds a security issue on your server. That's the reason we suggest people to set 444.

Your config.xml is writable. Don't forget to update permissions after you finish updating the configuration for security purposes.

no fix Rao v và Vi

Originally Posted by vothanhcam

no fix Rao v và Vi

Hello,

Support is offered for verified vBSEO customers only. If you hold a valid license, please open a ticket with your transaction ID from your payment receipt along with your forum URL so we can assign it to your account:
vBSEO.com Helpdesk.

If you are working on behalf of someone else as a contractor, they need to add you to their Priority Support list:
Customer Profile.