wp-config.php permissions set to 600

Hey @dimalifragis sorry to hear that you’re still having problems.

I imagine you’re using the latest version (1.9.3). If that’s the case, permissions shouldn’t get updated and it is possible we might have missed something.

Can you tell me when do permissions get updated? Activating/deactivating the plugin, updating specific settings? Anything you could give me as info would be greatly appreciated.

Hi, Yes the latest update.

There is a change from what i see. Now the permissions are changed to 600 ONLY when installing or activating the plugin. When removing the plugin, the permissions are intact.

Previously, during uninstallations the permissions were set at 600.

So this is partially fixed.

Hey!

Thank you for the swift response! That helps narrow it down.

However – I just installed super cache on a fresh instance and activating, deactivating the cache or deactivating and removing the plugin does not update the file permissions.

• This reply was modified 2 years ago by Peter Petrov. Reason: test clarification

Well, i don’t doubt what you say. Still this is what i see in my environment.

I added an edit to my previous reply, but I’ll move it to a separate reply to make things easier to follow.

Would it be possible to disable all plugins except WP Super Cache, and make sure wp-config.php has the right permissions before interacting with WP Super Cache?

Well, the config.php always had 644 permission. As for disabling all plugins, i can’t really do that in a live site. Maybe i could try it to a test site, at some point.

But seems strange that the issue is HALF fixed, meaning that there was a real issue and part of it was fixed.

I bet most of your 2millions installations are affected by this but (as you know probably) 90% of webmasters have no idea about all these ….

• This reply was modified 2 years ago by dimal.

Well, the config.php always had 644 permission.

I suspected as much. Just wanted to make sure it wasn’t set to 600 from the last time there was an issue.

Maybe i could try it to a test site, at some point.

If you could run it on the same server that would be great! As for me – I’m afraid I can’t debug this properly, as I can’t get it to occur on any of the test instances I ran.

But seems strange that the issue is HALF fixed, meaning that there was a real issue and part of it was fixed.What’s more weird is, that the same code is ran every time a file gets updated.

That is strange. There’s only one place in the whole plugin that changes permissions and that code is the same that’s ran for every file update.