Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 1203208 bytes) in /home/*****/public_html/wp-admin/includes/class-pclzip.php on line 4215

This happens quite a bit but it’s not a bug in WordPress or your new plugin or theme, you simply need to let PHP use more memory on your server. Thankfully WordPress makes it easy to do this. You must define a constant, WP_MEMORY_LIMIT in your server’s wp-config.php like this:

define(‘WP_MEMORY_LIMIT’, ’128M’);

The error message will give you an idea of how much memory is required. The error message says it tried to allocate 1203208 bytes or just over 1MB of memory. The limit here is 67108864 bytes, or 65536KB which is 64MB so here I’d need a WP_MEMORY_LIMIT of more than 66M. The error message will go away once PHP has enough memory but be sure to test it.

If you allocate too much memory your server could start eating into disk swap space. Also be aware that each Apache child process is allowed to use that much memory so if you had ten processes it could use ten times the memory limit in a worst case scenario. If that happens you’ll need more RAM or you’ll have to figure out what’s using so much memory.

There’s also a WP_MAX_MEMORY_LIMIT constant. By default it’s 256M and it’s currently only used when uploading images.

On the off chance that you don’t have WordPress installed and you came here from a search engine, then you’ll want to use ini_set() somewhere early in the PHP process to increase the memory limit:

ini_set(‘memory_limit’, ’128M’);

Finally, I love that the wp-config.php codex page is the first result of a search for WP_MEMORY_LIMIT.

Related Posts

• Memory stick weirdness
• There is a memory leak in PHP. …
• Update on the status of php ac …

There are a lot of changes there so if you have a self hosted blog I would really appreciate if you download the development version, wp-super-cache.zip and install it in your plugins folder.

• Use $_SERVER[ 'SERVER_NAME' ] to create cache directories.
• Only create blogs cached directories if valid requests and blogs exist.
• Only clear current blog’s cache files if navigation menu is modified
• Added clean_post_cache action to clear cache on post actions
• Removed garbage collection details on Contents tab
• Added wp_cache_check_mobile cacheaction filter to shortcircuit mobile device check.
• Don’t delete cache files for draft posts
• Added action on wp_trash_post to clear the cache when trashed posts are deleted
• Show a warning when 304 browser caching is disabled (because mod_rewrite caching is on)
• New check for safe mode if using less that PHP 5.3.0
• Added wp_supercache_remove_cookies filter to disable anonymous browsing mode.
• Fixed garbage collection schedule dropdown
• Fixed preload problem clearing site’s cache on “page on front” sites.
• Fix for PHP variable not defined warnings
• Fixed problem refreshing cache when comments made as siteurl() sometimes didn’t work
• Preloading of taxonomies is now optional
• Domain mapping fixes.
• Better support for https sites. Remove https:// to get cache paths.
• Added AddDefaultCharset .htaccess rule back in and added an option to remove it if required.
• Added multisite plugin that adds a “Cached” column to Network->Sites to disable caching on a per site basis.
• Added WPTouch plugin to modify browser and prefix list in mobile detection code. Added support for that plugin’s exclude list.
• Fixed cache tester
• Filter the tags that are used to detect end-of-page using the wp_cache_eof_tags filter.

Related Posts

• WP Super Cache 0.8.4, the garbage collector
• WP Super Cache 0.8.7
• WP Super Cache 0.9.9

WordPress on Mickopedia via r/Ireland.

Related Posts

• Irish language – Wikipedia
• Back to the Eighties
• Vicipéid – Wikipedia as Gaeilge!

Oh, hi from Iceland!

Related Posts

• No related posts

It was 8 years ago and WordPress didn’t have a plugin system and wouldn’t have until later. I had integrated Smarty into the b2++ project, with a nifty versioned template editor and even looked at doing the same with WordPress. Smarty had a plugin system that could be used in theory but nothing came of it.

What was your first post on the WordPress.org forum? Look in your profile to find out!

Related Posts

• First Post!
• Sitewide Tags 0.4 for WordPress MU
• Me and WordPress.com

WP Super Cache (and I presume other caching plugins) will delete everything in the cache directory. It’s like putting important files in /tmp/ where files are routinely cleaned out on reboot.

My replies on the thread above might paint me as a cold heartless bastard but I am sorry those websites suffered data loss. However I’m shocked that they put links to uploaded images in a folder containing temporary files!

Edit (20 minutes later): the codex page has been updated, thanks Westi for your help. It now recommends using wp-content/ms-filemap/ rather than wp-content/cache/

Related Posts

• Brians Latest Comments Cached
• Irish Blogs Directory, the new boggersphere!
• Cork LUG – Fish, ftp over ssh …

Mobile plugins need to tell WP Super Cache what user agents they support. I documented the filters you can use (“cached_mobile_browsers” and others) to do this but I don’t think they’ve been used by any plugin. It’s not hard to do and I added code that checks for WPTouch so when you visit the WP Super Cache settings page it updates the mobile user agents. So far it works for me but please feel free to view this site on your mobile phone and tell me if it looks ok! I also added support for the theme switcher in WPTouch based on code posted on the wporg forum.

It appears that the “random post on the front page” problem is a side effect of how PHP works. WordPress incorrectly reported that the current page wasn’t a search page, even though it was. I put an extra bit of code in checking if $_GET is non empty and that fixed it, so far.

Just in case anyone else is interested, this is why is_search() fails randomly when run during PHP shutdown. When a PHP process shuts down it starts by killing off objects. Unfortunately this happens before PHP stops executing your code, something that changed after PHP4.

Anything that runs when the output buffer finishes or that is registered by register_shutdown_function() better not depend on objects or classes. That means no using $wpdb, the object cache may disappear or to be completely paranoid don’t expect $wp_query to be around either! The functions is_search(), is_feed() and other related WordPress functions depend on $wp_query so you should cache the values of those functions earlier in the process. I’m thinking of hooking into wp_head but that depends on the theme unfortunately. Not every theme uses that action.

Many years ago I changed the format of the cache “meta file” from an object to an array because of the way the PHP desctruction process works. More recently, but still two years ago I had to remove all calls to get_option() and update_option() in the output buffer handler because occasionally people saw the error, “Call to a member function get() on a non-object in cache.php” in their error log. The object cache object had been destroyed by PHP! That was a right pain to figure out as the code looked perfect yet didn’t work right some of the time.

To help figure out problems I’ve added a lot more debugging to the plugin too. If $wp_query disappears it’ll appear in your debug log, and preloading will generate a lot more messages now.

Next up is caching is_search(), is_feed(), is_single() etc. Where should those be cached? The “init” action is too early for is_search and probably others but I don’t want to depend on actions that may not be in a theme.

Related Posts

• WP Super Cache 0.9.9
• Looking at a WPMU Object Cache
• WP Super Cache 0.8.4, the garbage collector

The first release of this plugin was in September 2009 so this has been a bit too long in the making. Back then the main caching plugin was WP Cache, which this plugin is based on, but now there are quite a few including W3 Total Cache, Hypercache, Quick Cache and many more.

Version 1.0 is an incremental upgrade from the previous release but it has a number of bugfixes and new features:

1. The all new scheduler and admin bar link should please many people, especially those who want to clear the cache on their site at particular times. The “Delete Cache” admin bar link is something people have been asking about for as long as WordPress has had that bar!
2. You can preload categories and taxonomies although this hasn’t really been tested as well as I’d like. It works for me but YMMV.
3. There’s better support for mobile and https users now. Mobile support should scale a lot more than previously.
4. The cache tester is fixed now and the plugin traps as many errors as possible. It’ll also spit out some helpful text if there is a problem. 99% of the time it’s because the server can’t request a page from itself.
5. At the risk of annoying users who comment on your site you can make them appear to be anonymous users which will drastically help your server if they like commenting a lot. Unfortunately it stops the comment form populating with their details so it might be worth using an external comment system like Intense Debate or Disqus!
6. The Advanced Settings page now lists a “do not cache page” secret key. Use this key to view any page of your site uncached.
7. The cache file listing and delete links should work again now.
8. And many many more bug fixes.

Once you upgrade go visit the settings page and check out what’s new there. The upgrade worked fine for me, but there’s no harm looking. Pay close attention to the new garbage collector. The scheduler is rather powerful and flexible so it’s worth setting up right.

If you have any problems please leave a comment here or use the support forum.

Related Posts

• WP Super Cache 0.8.4, the garbage collector
• WP Super Cache 0.8.7
• WP Super Cache 0.9.9

Another major change was the addition of a “Delete Cache” link on the admin bar for logged in users. This may seem strange, but it will only show if you have disabled caching for known users. Unfortunately this is needed because of the security measures required. It only deletes the supercache file(s) for the current page, not any legacy files associated with it.

If you’re feeling adventurous go download the development version from this page and give it a whirl. I really need feedback that this works well so please leave a comment if you try it.

The version number won’t change and when the next release comes out you’ll still get the upgrade notification!

Related Posts

• WP Super Cache 1.0
• WIP: the Super Cache admin page
• WP Super Cache 0.8.4, the garbage collector

Lupus causes the body’s immune system to go into overdrive and starts to attack itself. It is believed that over 50,000 people throughout the UK suffer with Lupus of whom 90% are female. The symptoms are many and varied, and the condition often seems to mimic other diseases. This gives rise to difficulty in diagnosis and the condition can be overlooked for years, unless the GP or consultant is alert to the possibility of lupus.

The Trust’s website must have experienced a torrent of traffic because Mr Fry is followed by gazillions of people and the tweet was retweeted by over 100 of his followers. The website stayed up and I’m glad that WP Super Cache played a part in helping them.

I wanted to mark the occasion of a website getting a Frying and surviving so I changed the “Digg proof” message in the plugin to “Stephen Fry Proof”. Download the development version from this page if you want a look. The link in the admin page goes to the Trust’s tweet so I hope I can play a small part in spreading the word.

Of course, just because you’re using this plugin is no guarantee that your site will survive a mention by Mr Fry or any other celebrity on Twitter (especially if your hosting is simply too limited) but With WP Super Cache at least it has a fighting chance!

BONUS: In case you didn’t see it, here’s Stephen Fry ag caint as Gaeilge (talking in Irish) as he appeared on an Irish language tv programme a while back:

Related Posts

• Stephen Fry on Ros na Rún
• According to Stephen's referer …
• How well did Super Cache handle the digg?