When WordPress 3.0 was released yesterday I ran into a problem. I used Memcached to cache database objects for WordPress, and I’ve used Xcache in the past, for several single install blogs that do not use WordPress MU. I used the drop-in plugin http://plugins.trac.wordpress.org/browser/memcached/.
When I setup WordPress 3.0 I could not get it to work properly with the Memcached plugin linked above. The logins were no longer unique, and I could not find a solution. I thought perhaps WordPress would have documented a solution since they integrated WordPress MU into the 3.0 release, but I couldn’t find the information for single blog installs to keep the logins unique with a wp-config.php entry as I’ve used for years.
In wp-config.php I entered the following two lines to make my single blog installation logins, and database object caching, unique in Memcached:
$blog_id = ‘www_domainname_com’;
At the end of my efforts I had to stop using Super Cache and switch over to W3 Total Cache, only because W3TC had built-in support for Memcached, APC, Xcache, and eAccelerator for database and page caching.
When using the drop-in plugin linked above I averaged 99% efficiency with Memcached, but the W3TC the efficiency is only 66%, which is why I would prefer not to use it at all.
My preference is to use Super Cache, and the drop-in Memcached plugin linked above as I’ve been using for years, but I cannot find a solution to keep the logins unique. If you can write a solution into Super Cache, or send me some links to where I mind find a solution to my problem I would continue to use Super Cache.
I am very grateful for all the time you put into Super Cache, and even more grateful because you offer free support for a free plugin that could be sold for a lot of money since we all need it, and the quality is so good.
Any help in solving this problem would be appreciated greatly.