{"id":38,"date":"2005-08-18T08:46:54","date_gmt":"2005-08-18T06:46:54","guid":{"rendered":"http:\/\/blog.blackdown.de\/?p=38"},"modified":"2016-10-29T03:51:02","modified_gmt":"2016-10-29T01:51:02","slug":"wordpress-security-annoyances","status":"publish","type":"post","link":"https:\/\/blackdown.de\/articles\/wordpress-security-annoyances\/","title":{"rendered":"WordPress Security Annoyances"},"content":{"rendered":"

As if the unprofessional handling of WordPress<\/a> security announcements (see Another WordPress Security Update<\/a> and More on Security Announcements<\/a>) wouldn’t be bad enough, the WordPress developers also seem to have problems with organizing releases.<\/p>\n

Stefan Esser reports<\/a> that there are two WordPress 1.5.2 versions. The first one, which didn’t fix the problem it was supposed to fix, was available for download for several hours before it silently was replaced by the fixed second version.<\/p>\n

It’s hard to understand why the version number wasn’t bumped for the second release and why the WordPress developers didn’t inform users about the mistake.<\/p>\n

The comments<\/a> from the WordPress crowd are a bit weak in my opinion. If there’s FUD about WordPress’ security it’s the sole fault of the WordPress developers!<\/p>\n","protected":false},"excerpt":{"rendered":"

As if the unprofessional handling of WordPress security announcements (see Another WordPress Security Update and More on Security Announcements) wouldn’t be bad enough, the WordPress developers also seem to have problems with organizing releases. Stefan Esser reports that there are two WordPress 1.5.2 versions. The first one, which didn’t fix the problem it was supposed
[→
Read the rest of this entry<\/a>]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"spay_email":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false,"jetpack_publicize_feature_enabled":true},"categories":[8,20],"tags":[],"yoast_head":"\n\n\n\n\n\n\n\n\n\n\n\n\n\t\n\t\n\t\n