{"id":63,"date":"2006-07-05T23:13:09","date_gmt":"2006-07-06T03:13:09","guid":{"rendered":"http:\/\/unitstep.net\/blog\/2006\/07\/05\/wordpress-203-tuneup\/"},"modified":"2006-07-05T23:18:15","modified_gmt":"2006-07-06T03:18:15","slug":"wordpress-203-tuneup","status":"publish","type":"post","link":"https:\/\/unitstep.net\/blog\/2006\/07\/05\/wordpress-203-tuneup\/","title":{"rendered":"WordPress 2.0.3 “tuneup”"},"content":{"rendered":"

I recently updated to WordPress 2.0.3<\/a>, basically as soon as I noticed it was available. It was touted as a “security fix” release, so I thought it would be a good idea to upgrade ASAP. However, it introduced a few bugs, that while not extremely detrimental, were nonetheless annoying.
\n
\nThe first bugs I noticed were WordPress adding backslashes (“\\”) before some quotes in comments and link descriptions, either after they had been posted or edited. This appeared to be an improper call to the PHP<\/acronym> addslashes()<\/code> function, since it was translating phrases like “it’s” into “it\\’s”, and is the common way to escape a string before input in to something like a SQL statement. However, it appears it was being called more than once.<\/p>\n

I found no way to get rid of the backslashes, other than manually editing the table record, and furthermore, didn’t know how to fix this behaviour. I figured I’d just deal with it, since I don’t really blog that much, and surely a new version will be out soon.<\/p>\n

But, while browsing one day, I found this post<\/a> detailing another blogger’s experience with these bugs. Luckily, they had been more persistant than I, and had found a helpful link to a “tuneup<\/a>” plugin that specifically fixed these problems introduced in WordPress 2.0.3. I just installed it, and everything appears to be back to normal. I’m not sure why the WordPress crew hasn’t decided to announce and link to this fix, as I think it’s quite essential for proper operation. <\/p>\n

Recommended as a “must-have” plugin for WordPress 2.0.3.<\/p>","protected":false},"excerpt":{"rendered":"

I recently updated to WordPress 2.0.3, basically as soon as I noticed it was available. It was touted as a “security fix” release, so I thought it would be a good idea to upgrade ASAP. However, it introduced a few bugs, that while not extremely detrimental, were nonetheless annoying.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[12,25],"tags":[],"_links":{"self":[{"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/posts\/63"}],"collection":[{"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/comments?post=63"}],"version-history":[{"count":0,"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/posts\/63\/revisions"}],"wp:attachment":[{"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/media?parent=63"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/categories?post=63"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/unitstep.net\/wp-json\/wp\/v2\/tags?post=63"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}