WordPress MU, the multi blog version of WordPress that runs on such sites as WordPress.com has been updated to version 2.6.5 to address an XSS vulnerability in the feeds offered to users.
More details will be forthcoming but for the time being, there’s also the WordPress.org announcement post.
This release also has a number of bug fixes, including a fix and improvements to rss caching. This is a required upgrade, so please install it as soon as you can.
After you’ve upgraded, check out the nominations for the 2008 WPMU Awards and vote for your favourite!
In related news, a new version of WP Super Cache is also available. This version hopefully fixes:
- Issues with clients seeing compressed pages incorrectly
- Cache clean up
- Warnings if Apache modules are missing
- Better support for WordPress MU. The wp-content/cache/.htaccess rules are now displayed on the admin page
- Better documentation on file locking
- WP Cache files are written to a temporary file first
- Use WP_CONTENT_URL in mod_rewrite rules generator
It also adds a number of filters:
- “supercache_dir” filter so the supercache directory can be manipulated. “wp_cache_key” cache_action to modify the key the wp-cache file is named after. Using both of these should make it easier for plugin authors to manipulate the cache based on user agent or other criteria. ie. iPhone theme? Unfortunately .htaccess rewrite rules will have to be updated manually.
- Added “wpsupercache_buffer” filter so the current page can be manipulated before being stored in the cache.
Argh! 2 things.
1) can you, for this post or the future, try to add a link to the changelog for the actual changes that took place? maybe to Trac?
2) I still can’t figure out why, but whenever I turn “on”, ON (WP Cache and Super Cache enabled), my site, within 24 hours, will start serving a 403 status code instead of 200. Htaccess is setup properly, as far as I know, and the folders are all set to chmod 777, so the files are writing properly, but the status code keeps changing and it’s really bad for SEO.
Any suggestions?
I’m going to be using MU again soon for a client and I’m not looking forward to it, had all kinds of probs with a previous version. Hopin this is better!
@Jonathan,
The list of changes from 2.6.3 to 2.6.5 is here:
http://trac.mu.wordpress.org/changeset?old_path=tags%2F2.6.3&old=&new_path=tags%2F2.6.5&new=
Jonathan – there’s a changelog included in the WP Super Cache zip file. Not sure why you get a 403. Sorry!
Not sure if you can help me, but i’m getting the follow error now that i’ve upgraded (via SVN)
Parse error: syntax error, unexpected T_SL in /var/www/vhosts/uwcblog.com/httpdocs/wp-includes/rss.php on line 1612
This only comes up when i go to the dashboard…
Bummer. Would like to work with you on it, if you have time. I can’t use SuperCache for it’s true value because it returns a bad status code.
Oh no, I just completed updating to 2.6.3 for a dozen of my WP & WPMU clients. Really didn’t expect further upgrade in such a short span of time till the arrival of 2.7 : (
Thanks for your continued work.
I’m looking forward to launching a couple MU sites when the BuddyPress beta plugins are released in a couple of weeks.
Donncha, Will MU 2.7 allow us to update our MU installs online if we give our Admins update capabilities like we can currently in 2.6?
Chris – I hope so, but if you want to make sure it works, download the code from http://svns.automattic.com/wordpress-mu/trunk and test it yourself. I haven’t tested it at all so I can’t really promise anything.
Wondering if this can be installed on Windows IIS? I have mysql database and php installed. Any assistance would be greatly appreciated.
It probably can be installed in IIS, but I wouldn’t recommend it. You’re better off with a Unix based OS and Apache or a webserver with mod_rewrite support.
I don’t know if anyone get ahold of you or not.
But there seems to be a serious bug on WP-Super-Cache. The Super part workers. but the standard Cache part is all but non-functional. I’ve disabled mine until there’s a fix.
Pat – it works fine for me. Can you debug it for me using error_log()? Thanks!
Where could I find this, in the plugin’s directory?
I’m having an issue with WP Super Cache. The WordPress install is in a subdirectory, and with WP Super Cache on, pages (as opposed to posts) do not show up and instead default to the index template. Any idea how I can get this to work?
Anyone found out how to fix the Cashe part? The Super part works but I’ve had to disable the Cashe part till I find a fix.
having the same problem as above “super cache”
any ideas solutions fixes yet?
thanks in advance