Hello csigncsign,
I actually don’t know what you mean by “writing access to the dashboard box”. We are not writing to any “box”. Because of our file based caching system option (so you don’t run with unsecure sessions), the general backup system and the automatic backup of changes to your .htaccess/robots.txt (when using the corresponding editor), we need a folder to write these files. This folder is located under “WP_CONTENT_DIR/bst/”. If this folder is not found BST will try to create it. If it can’t (because WP_CONTENT_DIR is not writable) it will fail. As backups and cache are core functions we have disabled the plugin when this error occours. “Fixing” this would take a while, as we need to make a version that doesn’t rely on any file operation.
However, you could just create a folder “bst” in the specified directory, make it writable to the WordPress/Apache user and you are fine. The check you are seeing here is only to create this folder. All file operations happen inside that folder and thus it’s scope. We will rewrite this notification to express this more clearly. But be aware: .htaccess/robots.txt and sitemap generation all rely on these files being writable to the system user. If the don’t exist, the parent directory needs to be writable, so we can create them.
I hope we could help you.
[ Signature deleted ]
PS: Don’t mix up system and wordpress user. File permissions are not related to a single WP user.
-
This reply was modified 6 years, 5 months ago by
bavoko.tools.
-
This reply was modified 6 years, 5 months ago by
Jan Dembowski.