{"id":533,"date":"2008-07-19T11:26:21","date_gmt":"2008-07-19T15:26:21","guid":{"rendered":"http:\/\/www.opticality.com\/blog\/?p=533"},"modified":"2008-07-19T11:31:30","modified_gmt":"2008-07-19T15:31:30","slug":"wordpress-26-goodness","status":"publish","type":"post","link":"https:\/\/opticality.com\/blog\/2008\/07\/19\/wordpress-26-goodness\/","title":{"rendered":"WordPress 2.6 Goodness"},"content":{"rendered":"<p>So, I tweeted the other day that I updated to WordPress 2.6 successfully, but didn&#8217;t blog about it. I am very pleased with the changes, though I had two minor frustrations, one was WP&#8217;s fault, the other not.<\/p>\n<p>First, the goodness. When 2.5 came out, they completely changed the media\/image management, changing the upload and selection process to be AJAX based. I really liked the <em>look<\/em>, but <strong>hated<\/strong> the <em>feel<\/em>. It took so many clicks and so much scrolling to edit the various image fields, and to select and insert an image in a post.<\/p>\n<p>2.6 fixes this completely (for me). This is done by making two (theoretically) trivial changes:<\/p>\n<ul>\n<li>Make the pop-up window larger, so that all of the fields for an image fit without scrolling<\/li>\n<li>auto-scroll to the selected image when the user clicks on <strong>show<\/strong><\/li>\n<\/ul>\n<p>That&#8217;s it! Now I don&#8217;t have to scroll after I click show.<\/p>\n<p>Another goodness is that the number of plugins that have newer versions available is now highlighted on every admin screen, with a cute little bubble above the plugins link. Very nice. I was very good about checking regularly anyway, but this will save me a few clicks every day.<\/p>\n<p>There are other new features, most of which I haven&#8217;t played with yet, but they certainly sound useful. The <a title=\"WordPress 2.6 New Features\" href=\"http:\/\/wordpress.org\/development\/2008\/07\/wordpress-26-tyner\/\" target=\"_blank\">video that shows off the new features<\/a> is crisp and gets to the point quickly.<\/p>\n<p>I&#8217;m happy with 2.6.<\/p>\n<p>Now for my two frustrations. The first is a WP problem. I noted in a recent post that <a title=\"WordPress Ate My Posting Date\" href=\"https:\/\/www.opticality.com\/blog\/2008\/06\/18\/wordpress-ate-my-posting-date\/\" target=\"_blank\">WordPress Ate My Posting Date<\/a>. I patched it successfully (a one-liner). The patch documentation led me to believe that it was already in the trunk, and therefore would be part of WP 2.6. It wasn&#8217;t. \ud83d\ude41<\/p>\n<p>When I posted about Chuck Mangione the other day, the RSS feed delivered that post with a date of 1999 again. I reapplied the patch, and I believe all is well again. It was disappointing that this simple one-liner missed the 2.6 release&#8230;<\/p>\n<p>The second frustration had nothing to do with 2.6. After I saw the new plugin update notification, I updated the two plugins that had newer versions available. When I went back to the admin screen and reloaded, it still claimed that both plugins needed updating, and the new bubble still showed a two in it.<\/p>\n<p>After some playing around, I decided to clear the XCache cache completely. That solved the problem. So, somehow, there was PHP code cached that didn&#8217;t update when I installed the new WP 2.6. I will try to remember not to make that mistake again, and just clear the cache whenever I update WP. Now the question is whether I need to clear the cache when a plugin gets updated, etc. Frustrating that somehow date stamps on the files don&#8217;t over-ride the cacheing&#8230;<\/p>\n<p>In any event, all is well again (at least for the moment). \ud83d\ude09<\/p>\n","protected":false},"excerpt":{"rendered":"<p>So, I tweeted the other day that I updated to WordPress 2.6 successfully, but didn&#8217;t blog about it. I am very pleased with the changes, though I had two minor frustrations, one was WP&#8217;s fault, the other not. First, the goodness. When 2.5 came out, they completely changed the media\/image management, changing the upload and [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"activitypub_content_warning":"","activitypub_content_visibility":"","activitypub_max_image_attachments":4,"activitypub_interaction_policy_quote":"anyone","activitypub_status":"","footnotes":""},"categories":[4,3,2],"tags":[23,21,303],"class_list":["post-533","post","type-post","status-publish","format-standard","hentry","category-4","category-3","category-2","tag-blog-software","tag-wordpress","tag-xcache"],"_links":{"self":[{"href":"https:\/\/opticality.com\/blog\/wp-json\/wp\/v2\/posts\/533","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/opticality.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/opticality.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/opticality.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/opticality.com\/blog\/wp-json\/wp\/v2\/comments?post=533"}],"version-history":[{"count":3,"href":"https:\/\/opticality.com\/blog\/wp-json\/wp\/v2\/posts\/533\/revisions"}],"predecessor-version":[{"id":536,"href":"https:\/\/opticality.com\/blog\/wp-json\/wp\/v2\/posts\/533\/revisions\/536"}],"wp:attachment":[{"href":"https:\/\/opticality.com\/blog\/wp-json\/wp\/v2\/media?parent=533"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/opticality.com\/blog\/wp-json\/wp\/v2\/categories?post=533"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/opticality.com\/blog\/wp-json\/wp\/v2\/tags?post=533"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}