Want to get Lullabot article, videocast, and podcast announcements delivered right to your in-box?
Let us know your email address (we won't share it) and we'll let you know when anything exciting happens.
Drupal memcache module 1.2 released
July 29, 2007
UPDATE: see http://www.lullabot.com/blog/drupal_memcache_module_1_3_released
UPDATE: following my recent tradition of botching releases I quickly detected and corrected a critical error introduced in the 1.1 release. This post now applies to the 1.2 release.
The DRUPAL-5--1-2 version of the memcache module has been released. This is a bugfix and documentation release. The mandatory patch has also been rerolled so that there are versions for Drupal 5.1 and 5.2. The largest bugs were fixed in the memcache admin module which is now working nicely. It is not necessary to reapply the patch when upgrading to 1.2 unless you have also upgraded your Drupal version. People upgrading from Drupal 5.1 to 5.2 should revert the memcache patch before attempting the 5.2 upgrade. This is done as follows:
patch -R < sites/all/modules/memcache/DRUPAL-5-1-cache-serialize.patch
No database upgrades are necessary when upgrading to 1.2. It is not necessary to run update.php when upgrading to 1.2.
Comments
not really necessary
I upped to Drupal 5.2 immediately when it came out and we have not seen anything break.
ahem...
Two tables are updated, the comments table, and the users table... ;)
Please clarify. The upgrade
Please clarify. The upgrade from memcache DRUPAL-5--1-0 to memcache DRUPAL-5--1-3 doesn't change any database schemas as far as I know, certainly not the comment or user tables. The upgrade from Drupal 5.1 to Drupal 5.2 might, but I didn't mean that.
Running it on a live site already
I upgraded a site from 5.1 to 5.2 last week the same day 5.2 came out.
The memcache kept working fine, until I saw the new release today. I installed it and had some issues in the beginning (hits to the front page ended up trying to redirect to the memcache admin page). So I commented out the lines having the drupal_goto() in that module.
I was about to report the issue when I noticed there is a 1.3 listed, and installed that, and had no problems (apart from the need to restart memcached).
On a related note, for this one high traffic site on a single box, it is worthwhile to skip the filter cache altogether, when you need the RAM for other things. I created a patch for that in #163023.
Post new comment