Not too long ago a bug in sure variations of PHP got here to our consideration that would trigger a safety vulnerability in your weblog. We’re capable of work round it pretty simply, so we’ve determined to launch 2.0.7 to repair the PHP safety drawback and the Feedburner subject that was in 2.0.6. It’s endorsed that everybody operating WordPress 2.0.6 or decrease upgrade to this new version.
As a result of this can be a a lot smaller replace than earlier variations, you wouldn’t have to replace all of WordPress’ information in the event you’re upgrading from model 2.0.6. Right here is the checklist of information which have modified since 2.0.6:
We all know it sucks to have a launch solely 10 days after our final one, however we expect it’s vital sufficient to your weblog to be safe to do it, and hopefully solely having to alter just a few information will make the improve simpler than regular.
Listed below are the modifications which have been made since 2.0.6:
- Safety repair for
wp_unregister_GLOBALS()to work across the zend_hash_del_key_or_index bug in PHP 4 variations lower than 4.4.3 and PHP 5 variations lower than 5.1.4 with
register_globalsset to “On.”
- Feeds now correctly serve
304 Not Modifiedheaders as a substitute of mismatched 200/304 headers (a.ok.a. the FeedBurner bug).
- Backport of one other
304 Not Modifiedrepair from WordPress 2.1
- Deleting WordPress Pages now not provides an “Are You Certain?” immediate.
- After deleting a WordPress Web page, you are actually correctly redirected to the Edit Pages display.
- Sending a picture at unique dimension in Web Explorer now not provides an incorrect “top” attribute.
And simply as a reminder, the subsequent main model of WordPress (2.1) is due out by the top of the month, however the 2.0 department of WordPress will proceed to be maintained for a number of years.