{"id":134,"date":"2004-10-06T12:42:41","date_gmt":"2004-10-06T18:42:41","guid":{"rendered":"http:\/\/wordpress.org\/development\/2004\/10\/wp-121\/"},"modified":"2021-06-04T11:57:58","modified_gmt":"2021-06-04T11:57:58","slug":"wp-121","status":"publish","type":"post","link":"https:\/\/wordpress.org\/news\/2004\/10\/wp-121\/","title":{"rendered":"WordPress 1.2.1"},"content":{"rendered":"

I am relieved to announce that WordPress 1.2.1 is now available for download<\/a>. This release addresses a few bugs and minor security issues with 1.2. We’ve also backported the new login system from 1.3 that is much friendlier and should address many of the problems people have had with logging in and cookies.<\/p>\n

Upgrading<\/h4>\n

Upgrading from 1.2 is very easy. Your existing templates and plugins should work just fine; all you need to do is overwrite the WordPress files and folders<\/strong>. To upgrade:<\/p>\n

    \n
  1. Download 1.2.1<\/a><\/li>\n
  2. Unzip<\/li>\n
  3. Upload the new files to your site, taking care not to overwrite anything you may have modified like index.php<\/code><\/li>\n<\/ol>\n

    Security Issues<\/h4>\n

    Those of you who follow security lists may have noticed there was an announcement about WordPress a few days ago. This announcement was not entirely accurate and several articles have been published subsequently that feed off the hype. We take security very seriously, and the last WordPress advisory was over a year ago despite the astronomical growth we’ve experienced. Unfortunately the author of the advisory did not<\/em> contact us before he published the problem so we found out about this when everyone else did. Most responsible security professionals contact the vendor first and in that case we could have released the fix at the same time the problem was announced. Fortunately it was a fairly low-risk problem and we have had no reports of anyone being affected.<\/p>\n

    At the same time we were responsibly notified of a related but separate problem in the code related to HTTP response splitting<\/a> (PDF link) by “Chaotic Evil.” Some have asked why it took a few days for 1.2.1 to be released, and this is why. We wanted to be sure we addressed both problems and fully tested everything because a premature release would do more harm than good.<\/p>\n

    I want to thank Chaotic Evil for professionally notifying us of the problem and letting us address it before he announced it. Also thank you to our fantastic beta testers who helped us with this very rapid release cycle, and finally to the WordPress community for being so supportive while we prepared these fixes.<\/p>\n","protected":false},"excerpt":{"rendered":"

    I am relieved to announce that WordPress 1.2.1 is now available for download. This release addresses a few bugs and minor security issues with 1.2. We’ve also backported the new login system from 1.3 that is much friendlier and should address many of the problems people have had with logging in and cookies. Upgrading Upgrading […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"episode_type":"","audio_file":"","cover_image":"","cover_image_id":"","duration":"","filesize":"","date_recorded":"","explicit":"","block":"","filesize_raw":"","jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[14],"tags":[],"class_list":["post-134","post","type-post","status-publish","format-standard","hentry","category-releases"],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/pZhYe-2a","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts\/134","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/comments?post=134"}],"version-history":[{"count":1,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts\/134\/revisions"}],"predecessor-version":[{"id":10464,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/posts\/134\/revisions\/10464"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/media?parent=134"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/categories?post=134"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/wordpress.org\/news\/wp-json\/wp\/v2\/tags?post=134"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}