-
Notifications
You must be signed in to change notification settings - Fork 17
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
Should super-cache enable / disable modify $cache_enabled? #17
Comments
Ok #16 resolves all. |
This is still an issue, as #16 was never merged. |
Especially with the new |
I'm working on this issue. We should better handle errors because enabling caching should modify |
In this case, there's already a discrepancy between what Checking errors is of course important, but checking the result consistently is probably an easy first step. |
I just made quick fix - PR #25. We need to check only I'll try to review preload command and then I'll try to make better error checking. @playmono Could you test these changes? |
Hi all,
I did some tests using this package on my wordpress installations and because I don't know much how works wordpress cache, I was wondering some questions.
As I can see, if run this
The only thing that changes is in
wp-cache-config.php - $super_cache_enabled = 'true';
But in wordpress frontend, cache still remains disabled:
The same thing happens with
variable
$super_cache_enabled
changes tofalse
but in frontend, cache remains enabled.So, I did some research and I see that in frontend if you enable or disable cache, two variables of
wp-cache-config.php
changes:$cache_enabled
and$super_cache_enabled
My workaround to solve this was in enable / disable functions of super-cache package adding
wp_cache_disable();
andwp_cache_enable();
.super-cache.txt
But my concern is if maybe super-cache enable / disable should affect only to super-cache plugin (as it is now). In the other side, in wordpress frontend, if you check / uncheck enabling cache, you are modifying the two values.
What do you think guys?
Thank you.
The text was updated successfully, but these errors were encountered: