Plugin Author
AITpro
(@aitpro)
BPS does not require that you change your WordPress Filesystem API Method to “direct” if you have a DSO server type which is very rare (1%). Most folks have a CGI server type (99%) or use the “direct” WordPress Filesystem API Method if they do have a DSO server type: http://forum.ait-pro.com/forums/topic/dso-setup-steps/. It is recommended that you make that change on a DSO server type to avoid all the problems that will occur on your site in general with WordPress itself, all plugins that do file writing, all themes that do file writing, etc. on an ongoing basis when you decide not to use the “direct” WordPress Filesystem API Method. This other forum topic problem that you posted a week ago is caused because you are not using the “direct” WordPress Filesystem API Method: https://ww.wp.xz.cn/support/topic/after-43-update-im-unable-to-update-plugins-or-themes/page/2?replies=48#post-7380431
You can of course handle Ownership and Permissions of folders and files any way you would like on your DSO server type instead of changing the WordPress Filesystem API Method to “direct” to let WordPress automatically handle things, but most folks do not understand how to change Ownership of folders and files (or even that a DSO server type requires this) on a DSO Server type so it is much simpler to let WordPress handle this automatically by using the “direct” WordPress Filesystem API Method.
For more information about the WordPress Filesystem API Method see this WordPress Codex page: https://codex.ww.wp.xz.cn/Editing_wp-config.php#Override_of_default_file_permissions
Wordfence is not bad, but it is not BPS of course. 😉
I did get BPS working on my system and fiddled with file permissions given the warning. But I’m self hosting on a Thecus N2310 NAS, so options are limited by the firmware and server modules. Direct method would have been very difficult to implement. Thanks for the discussion points.
I noticed that BPS did alter .htaccess permissions to increase security.
Note to other thecus os6 users: Re-apply the ACL in naswebsite to regain SCP/samba access to the files.
Plugin Author
AITpro
(@aitpro)
Yep, I see that you have had ongoing problems with getting WordPress installations to install for years looking at your thread post history so it is not a new problem with your server setup/configuration. I would not say that it is specific to your server type and is more about Ownership and Permissions problems on your server since this same type of problem occurs on other DSO server types where there are Ownership or Permissions restrictions/problems/misconfiguration/etc.
Note to other thecus os6 users or anyone else: translation in plain english. BPS changes the root htaccess file permissions to 404. Change the htaccess file permission back to what it was before, which is 644 file permissions on a DSO server. If you did anything with any of the standard WordPress Filesystem API Method code/constants/etc. then change things back to what they were before.
In any case, since you have your own server then you should be doing all the htaccess stuff in the server’s conf files anyway.
Plugin Author
AITpro
(@aitpro)
Just trying the best I can to stay on task, get good info out there and actually be helpful to someone in the long run. 🙂 The general idea in my head is to put facts on the page and get right to the root issue instead of looking at symptoms or stuff that is beside the real point. Thanks for changing the star rating. Very much appreciated. 😉
