Filesystem Security > File Permissions

Hello again, hope you are all well and having a wonderful holiday with family.

I came across something that I wanted to send in to you guys and it involves the proper path for wp-content (default) that has been changed; say for the sake of argument to new-location. The plugin is showing the default path exclusively and appending it to the “server” path which results in the following:

1. As you can see the path is what you would expect as default at the end of my server path but in actuality my path is not the default of wp-content which brings us to the “current permissions”.
2. It shows the permissions as 0 because the path doesn’t exist and so when it queries it’s permission, there is nothing there which brings us to fix buttons.
3. When you click on the button it results in an error, which is expected given the path is wrong and any attempt to set permissions on a non-existent path is going to fail.

Here is the visual on that:

It really should be pulling that information dynamically from the WordPress settings and not using a hard-coded default value appends. Doing that, it will resolve the second issue of getting proper permission and also the button in case it should become needed.

Thank you guys, have a good end of the year and be well.

• This topic was modified 7 years, 11 months ago by Gμ?rD???. Reason: formatting