WordPress MU 2.8.2 has just been released. This is a security release with the same fix as the standalone WordPress.
WordPress 2.8.2 fixes an XSS vulnerability. Comment author URLs were not fully sanitized when displayed in the admin. This could be exploited to redirect you away from the admin to another site.
This release also fixes a number of other bugs, most notably the upgrade notice, but also fixes a number of other problems. See the timeline for a record of the latest activity.
Grab the new release from the download page or upgrade automatically from within WordPress MU.
18 Comments
Pingback: WordPress MU 2.8.2 freigegeben - WordPress MU 282, Ein Update wird dringend empfohlen, WordPress MU 281, WPMU 282, Download von WordPress MU 282, Informationen vom Entwickler - WordPress MU Deutschland
WordSkill (11 comments.) on July 20, 2009 at 7:01 pm.
Brilliant, I love these quick releases!
Adam Dempsey (1 comments.) on July 20, 2009 at 7:17 pm.
Cheers for the extra quick work Donncha!
Lobo Feroz (1 comments.) on July 20, 2009 at 7:44 pm.
Thanks for the quick release!
I still have a problem with the upgrade. I upgraded yesterday and of course after that I’m still getting the “WordPress MU 2.8.1 is available! Please update.”. It’s not showing 2.8.2. If I try to update again it doesn’t work.
Warning: copy(/var/www/wordpressmu/wp-content/upgrade/wordpress-mu-2.8.12/wordpress/wp-admin/includes/update-core.php) [function.copy]: failed to open stream: No such file or directory in /var/www/wordpressmu/wp-admin/includes/class-wp-filesystem-direct.php on line 131
Could not copy files.
Installation Failed
What should I do now? If I download 2.8.2 and deploy it manually, should I make any change to the database?
Best regards,
Lobo Feroz
Kimberly (1 comments.) on July 20, 2009 at 10:27 pm.
Thanks for the awesome work you are doing on the WordPress MU releases.
The automatic upgrades just get easier and faster
Daniel (2 comments.) on July 20, 2009 at 11:23 pm.
Wonderful. I was waiting for it. Now I just wonder why the two MU setups that I manage don’t see the latest version yet. They still say “WordPress MU 2.8.1 is available. Upgrade now.” Is that prompt changing with a time lag? what time frame are we talking about? –oh, they are german language installs. Is that why it takes time?
Daniel (2 comments.) on July 21, 2009 at 12:16 am.
I just installed 2.8.2 over my existing 2.8.1, then also replaced the german language files. Now I still get an error when trying to add a user to a blog. See http://mu.wordpress.org/forums/topic/13372
Pingback: Need WordPress MU Support? Here’s Where You’ll Find it! - WordPress MU and BuddyPress plugins, themes, support, tips and how to's
RaveN (3 comments.) on July 21, 2009 at 6:46 am.
Testing & Installing
Pingback: WordPress MU Also Hits 2.8.2 | The Blog Herald
mwaterous (9 comments.) on July 21, 2009 at 10:54 am.
¡Muchas gracias!
Those are some speedy version ups.
Arturo (1 comments.) on July 21, 2009 at 11:27 am.
is possible have the pot for this version in the svn?
thanks for the great work!
Donncha (1707 comments.) on July 21, 2009 at 12:29 pm.
Not really because the translations are available elsewhere. If translations files were included in the release they would have to be updated before new releases, something that would be impossible with current resources available.
Cheryl Johnson (3 comments.) on July 21, 2009 at 3:11 pm.
On 2 Mu sites I run that were already on 2.8.1; using the upgrade button produced the same fatal error message that Lobo reported.
However, updating The Old Fashioned Way solved the problem. And deeply increased my appreciation for the Update Button.
Pingback: Adding your own hooks to #Wordpress « Mark.
Pingback: blogs.freebsdish.org updated to wordpress-mu 2.8.2 | Florent Thoumie
willy (1 comments.) on July 27, 2009 at 11:40 am.
hi
give me ah mu plsssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss . full stats and fenrir
Vinoth (1 comments.) on July 27, 2009 at 11:44 am.
I know that they have fixed a XSS vulnerability in the new version. Any other significant improvement in this new version?