Error message: WARNING: Your config.xml is not writable. Settings cannot be saved.

Is the fix just as simple as changing the permissions on the config.xml file?

Hi Ron,

Yes. Change them to make the file writable.

(Remember to change them back once you are done making changes.)

Hello... sorry for the basic quesiton, but... where is this config.xml file located at?

What directory?
Much thanks!

/vbseo/resources/xml/

Originally Posted by Brian Cummiskey

/vbseo/resources/xml/

Thank you for the quick reply!

Should it be modded to 444?
Thanks!
Have been using vBSEO for 5-6 hours... and so far... EXCELLENT SOFTWARE!

Hello,

chmod it to 666 to make it writable. Then chmod again to 644 when you are done .

Originally Posted by creativeLiquid

Have been using vBSEO for 5-6 hours... and so far... EXCELLENT SOFTWARE!

Yep, the best vBulletin plugin I ever seen.

Originally Posted by Chuta

Hello,

chmod it to 666 to make it writable. Then chmod again to 644 when you are done .



Yep, the best vBulletin plugin I ever seen.

Done!
AWESOME! Much thanks sir!
wow! ¡Hablas español también! ¡Gracias!

Originally Posted by creativeLiquid

Done!
AWESOME! Much thanks sir!
wow! ¡Hablas español también! ¡Gracias!

¡Claro que sí! . Complacido de que vBSEO sea un producto de tu agrado.

Saludos compatriota!.

Ok, maybe I'm doing something wrong.

Went to the directory:::
HOME/public_html/forums/vbseo/resources/xml

There, I chmod the file config.xml with the following command:::
chmod -v 0644 config.xml

Confirmation message successful.
In addition, Windows FTP program shows permission set as 644.

Yet the Control Panel says:

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

Where am I going wrong?
Thanks! ¡Gracias!

I've seen a few customers with the same problem:

3.5.2 upgrade showing "Your config.xml is writable"
config.xml is writable (even though its not)

Mert gave a light on this post:

3.5.2 upgrade showing "Your config.xml is writable"

Originally Posted by Chuta

I've seen a few customers with the same problem:

3.5.2 upgrade showing "Your config.xml is writable"
config.xml is writable (even though its not)

Mert gave a light on this post:

3.5.2 upgrade showing "Your config.xml is writable"

Thanks! On my way to check it out... will update soon.

====
EDIT::
Ok, no problem.
Seems to be a hiccup somewhere.

I checked once more the permission with the "Legacy File Manager" via CPanel (hosted account), and it showed Permission set to 644.

I'll be looking for any updates or changes, yet I think it's ok for now.

Originally Posted by creativeLiquid

Thanks! On my way to check it out... will update soon.

====
EDIT::
Ok, no problem.
Seems to be a hiccup somewhere.

I checked once more the permission with the "Legacy File Manager" via CPanel (hosted account), and it showed Permission set to 644.

I'll be looking for any updates or changes, yet I think it's ok for now.

If the vbseocp is saying the file is still writeable at 644 you should change the permissions to 444 when you want it secure and 666 when you want to make a change. This is only needed in the event that 644 doesn't work though which seems to be the case with people using shared hosing who utilizes suPHP or similar.

Originally Posted by Ceri May

If the vbseocp is saying the file is still writeable at 644 you should change the permissions to 444 when you want it secure and 666 when you want to make a change. This is only needed in the event that 644 doesn't work though which seems to be the case with people using shared hosing who utilizes suPHP or similar.

Set to 444!
Thanks for the correction.