[Plugin: WP Super Cache] WP-Super-Cache DOES NOT work with 2.7!
I am writing this to give everyone a heads up. WP-SUPER-CACHE does NOT, I repeat, DOES NOT WORK with verson 2.7. Sometime during the development stages of 2.7. WP-Super-Cache stopped functioning. I notified the author, and he WANTED ME to “Debug” the bloody thing. Which is impossible, because for starters, I know zero about debugging or programming, not to mention, I am on shared hosting and have no access to Apache logs. My Blog is on site5.com’s servers, which piggy back on The Planet’s servers.
It just will not cache pages, like it was doing. It will install, but if you turn it on, it does not cache at all. it changes your .htaccess like it is supposed to, But no cache at all. I even tried turning off compression the numbers stay at zero.
Just letting everyone know, before the heartache begins.
Thanks for the reminder Pat, your original comment never mentioned WP 2.7, and was left on my blog at 6.25pm on a Saturday evening. Hardly the best time of the week to look for unpaid support of Free Software.
Your reaction on Twitter on Sunday didn’t really help however. Slight overreaction? (Warning! NSFW text)
Anyway, to put your mind at ease, the plugin will be updated and will work with WP 2.7 before it’s released.
I would like to add, that I am currently using WordPress 2.7-RC1 and there are no problems with WP Super Cache. All cached pages contain these comments:
<!-- Dynamic Page Served (once) in 2,015 seconds --> <!-- Cached page served by WP-Super-Cache --> <!-- Compression = gzip -->
So what exactly is the problem?
I’ve just verified that WP Super Cache works with the latest WP 2.7 code out of SVN. It’s running on http://notspam.org/ just fine.
I think there’s something else wrong, either something in PHP5 or some local configuration issue. If anyone is seeing this same issue (no cache files being created in the supercache directory), please send login details to your server to donncha @ gmail.com and I’ll investigate.
I’m off to try PHP5.
PHP5 works fine too. Pages are cached, and static files are served to anonymous users.
And it works fine with fastcgi too. I wonder if it’s an suexec problem?
For what it’s worth, it doesn’t work for me on 2.7B3 or RC1 either. If you’d like me to assist you with debugging, feel free to contact me and I’ll be happy to help in any way I can.
Thank you for the time you’ve spent working on this free plugin. It’s one of the top several plugins for WordPress.
I’m on a Bluehost shared server and Super Cache was working fine with all previous versions of WP back into the 2.5 series all the way through the 2.7 trunk builds until a few days ago when the cached pages stopped being served altogether. Nothing changed on my server with the exception of the MySQL database being upgraded from 5.0.45-community to 5.0.67-community and I really don’t think that was the problem.
I’ve been running PHP 5.2.6 (fastcgi) with no problem either until the last few trunk builds (via the “Stay Updated” link) prior to RC1 when the plugin simply stopped working. At RC1, I enabled “compression” on Super Cache’s settings page and the plugin started working again. This makes no sense to me.
Yesterday, I upgraded a client’s site from 2.6.3 to 2.6.5 and Super Cache simply stopped working for her as well and enabling compression, uninstalling and reinstalling Super Cache, re-entering the .htaccess rules had no effect. I just left the plugin activated and logged out since her site was still loading fast enough (.55* average). She’s running the same MySQL and PHP versions as I am on a different Bluehost server entirely.
Just on a whim I checked her site’s source code this morning and there was the Super Cache entry at the bottom just like it should be and just like it wasn’t the day before. Nothing changed at all overnight.
No errors in the error logs. No errors in the Apache logs. Nothing to give me a clue as to what went wrong. Paleo Pat and the others who had problems do not run on Bluehost that I know of and most likely have different set ups then myself and my client. Some folks are having problems and some are not (all running either 2.6.5 or 2.7 trunk or RC1)
Ghost in the machine?
And many thanks for this most excellent plugin. Us shared server bloggers would be lost without it.
hallsofmontezuma and KirkM – Can you download the updated scripts from here and copy into plugins/wp-super-cache/ ?
I’ve changed the plugin so it uses uniqid() instead of tempnam() which is the only reason I can think of for the cache to stop working as that change was added in 0.8.5.
Was it after you upgraded to the latest version that the problems started?
It’s working for me on my site. Absolute latest 2.7 SVN, I just updated.
Was it after you upgraded to the latest version that the problems started?
It seems so, at least in my case. The funny thing was that I had two sites both running the same versions of 2.7, upgraded at the same time (nightly builds) and the only thing that changed the day Super Cache stopped working was updating to Super Cache 0.8.5 from 0.8.4
Strangely enough, 0.8.5 was working fine all morning on both sites (then at RC1 beta3-almost RC1-almost), I went to lunch, came back, checked the sites, and both sites were no longer being cached. The next morning, both sites were being cached but no more than an hour later–no caching. Upgrading to 0.8.5 was all that changed over that period of time.
Currently, only the site running WP 2.6.5 is not being cached. The other two 2.7 RC1 sites are currently being cached properly with 0.8.5 (go figure).
Oh yeah, I see that 0.8.6 has been released. I’ll give it a try. I’ve got 3 sites that are running 2.7 RC1 to test it out on. .htaccess Rules can stay the same I’m assuming?
Sorry for the long replies. I have a bad habit of being too wordy.
Check your wp-config.php before you upgrade. Is there a “define( ‘WP_CACHE’, true );” in there?
The check for that was modified in the last month to handle whitespace in front of the define() and also to handle when that constant is defined elsewhere. I didn’t do the “pre existing” check properly.
I presume that after you upgraded you may have disabled the plugin and then reenabled, or turned off caching and then on again and the WP_CACHE define was removed or commented out.
Anyway, hopefully upgrading to 0.8.6 will solve the problem. It’s not a mysterious WordPress 2.7 issue!
I tend to agree after working with the problem that it’s not a WP 2.7 problem specifically.
Just by long habit I checked my “wp-config.php” file for “define( ‘WP_CACHE’, true );” while experiencing the problem and it was there. Now that I think about it, I regularly turn off caching if I’m working on the sidebar content or other items that need caching to be off while viewing any changes made. I’ve always been able to turn caching back on and have it just start working successfully without having to check “wp-config.php” for the entry.
Super Cache has always been well behaved in the past. Turn it on/turn it off/deactivate it/reactivate it…no problems. Pretty amazing considering what it does (nice job that one).
Well, I installed the new version. Still not working, at all.
Here’s what my host runs:
Operating system Linux
Kernel version 2.6.9-67.0.22.ELsmp
Machine Type i686
Apache version 2.2.9 (Unix)
PERL version 5.8.8
Path to PERL /usr/bin/perl
Path to sendmail /usr/sbin/sendmail
PHP version 5.2.5
MySQL version 5.0.51a-community-log
cPanel Build 11.23.6-STABLE 27698
Theme cPanel X v2.6.0
Documentation Click to View
cPanel Pro 1.0 (RC1)
All I know is, that it was working. and sometime during the development process, it stopped working, totally.
If Donncha wants to be a serious programmer and a real man, and possibly see why it is not working, I’ll work with him. But if he wants to be your a-typical programmer and blame the user, he can have a nice day.
Sorry, the stupid “it’s free software” argument doesn’t fly with me. You provide a service and if you’re not a big enough man to back that service up, you should withdraw it for the market.
Just that simple.
- The topic ‘[Plugin: WP Super Cache] WP-Super-Cache DOES NOT work with 2.7!’ is closed to new replies.