-
-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bypass DISALLOW_FILE_MODS introduced in 2.5.0 #512
Comments
Right, when Because the "Enable Cache" button will be disabled regardless if |
Yes and no... You can have What I try to say it´s that are two totally different cases and should be treated that way. For example, as I said, in my server I uploaded all files with my user and the server is running with apache user. I detected it becauses when I try to enable cache, It´s says the filesystem is not writable and I need a sysadmin to correcte the permissions. And then, If I enable I need any way to enable cache with And, sorry for my language, it's difficult to explain well when it's not your native language. |
Thanks for the details! If I think you're right. If |
Thank you for your explanation. One last question.
I believed that in order to activate the cache it was necessary to be able to write to the So, can I activate the cache with the Thank you very much again. |
Yep, that works! |
Description
On my site I have the
DISALLOW_FILE_MODS
constant activated because I control file modifications through GIT. In this way, I am blocked from editing the theme files, installing / updating WordPress, plugins, themes, etc...The problem is that with this constant configured, in the latest version of the plugin the error appears indicating that the file system is not writable as checked in
redis-cache/includes/class-plugin.php
Lines 1352 to 1376 in b582fba
I don´t consider that writing the object-cache.php file to manage the cache should be prohibited even if the rest of the modifications to WordPress files are.
Expected Behavior
Can enable Redis cache with
DISALLOW_FILE_MODS
Actual Behavior
Filesystem not writable error
Possible Fix
Not sure. Maybe create a new constant like
WP_REDIS_SKIP_DISABLE_FILE_MODS
or something like that. Or maybe use the actualWP_REDIS_DISABLE_DROPIN_CHECK
to skipDISALLOW_FILE_MODS
.Steps to Reproduce
DISALLOW_FILE_MODS
totrue
inwp-config.php
Additional context
Environment
The text was updated successfully, but these errors were encountered: