{"id":9,"date":"2007-01-30T12:58:40","date_gmt":"2007-01-30T17:58:40","guid":{"rendered":"https:\/\/www.opticality.com\/blog\/?p=9"},"modified":"2007-10-02T15:03:09","modified_gmt":"2007-10-02T20:03:09","slug":"testing-1-2-3","status":"publish","type":"post","link":"https:\/\/opticality.com\/blog\/2007\/01\/30\/testing-1-2-3\/","title":{"rendered":"Testing 1-2-3"},"content":{"rendered":"<p>I&#8217;m not a happy camper. I started out with WordPress 2.05. After the first post or two (or three), I upgraded to 2.07. That upgrade went flawlessly.<\/p>\n<p>This past weekend, I upgraded to WordPress 2.1. The upgrade &#8220;failed&#8221;. The previous blog posts showed up fine, but I saw a SQL error in the part that shows  which categories each post is in. A little digging, and it became obvious that one of the schema changes failed. Turns out that my &#8220;user&#8221; (at the MySQL level) had insert\/update\/delete rights, but not alter, etc. Ugh.<\/p>\n<p>Nothing I did after granting those rights made it possible to re-run the &#8220;upgrade.php&#8221; script correctly. At least not that I could tell&#8230;<\/p>\n<p>After reading some forum posts, I installed phpMyAdmin, and while looking at the updated schema file, I hand-edited the DB to add the appropriate columns and one new table. It seemed to work, as the SQL error went away.<\/p>\n<p>Then yesterday, I wrote another long post complaining about my saga with the old Dell laptop. When I hit save, it &#8220;appeared&#8221; to save, but the post was gone, forever&#8230; The title was there, with a blank post. Another test, and sure enough, no posts were making it to the DB.<\/p>\n<p>Man, the people that &#8220;encouraged&#8221; me to start blogging owe me quite a number of hours to be added back to my life (not that I&#8217;m anything less than a world-class time-waster all on my own, but I really didn&#8217;t need any help here) \ud83d\ude09<\/p>\n<p>So, I exported all of my previous posts (yep, all 5 of them). Today, I created a new DB, updated the wp-config.php to point to the new DB, made sure to grant my user ALL privileges on that DB, and re-ran the &#8220;wp-install.php&#8221; script. After that worked, I imported my posts, and voila, they are all back.<\/p>\n<p>This post will be the &#8220;test&#8221; as to whether that solves my problem of posting in general&#8230;<\/p>\n<p>Finally, while WordPress 2.1 seems to have cooler features in it, so far, in Firefox 2.0.0.1, the UI is hosed. The textarea that I am writing in spills into the sidebar on the right hand side (that worked perfectly in 2.07), and the only &#8220;fix&#8221; is to maximize the window to the entire screen (I&#8217;m running 1600&#215;1200), which is annoying, to say the least&#8230;<\/p>\n<p>P.S. No such luck. This post failed too. I have reverted back to 2.0.7. Even with a fresh install of 2.1, and no imports, I can&#8217;t post anything by a blank with a title :-(. This is a fresh install of 2.0.7, with the original posts imported, and this one as the &#8220;new&#8221; one&#8230;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I&#8217;m not a happy camper. I started out with WordPress 2.05. After the first post or two (or three), I upgraded to 2.07. That upgrade went flawlessly. This past weekend, I upgraded to WordPress 2.1. The upgrade &#8220;failed&#8221;. The previous blog posts showed up fine, but I saw a SQL error in the part that [&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":[3,2],"tags":[23,22,21],"class_list":["post-9","post","type-post","status-publish","format-standard","hentry","category-3","category-2","tag-blog-software","tag-upgrade","tag-wordpress"],"_links":{"self":[{"href":"https:\/\/opticality.com\/blog\/wp-json\/wp\/v2\/posts\/9","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=9"}],"version-history":[{"count":0,"href":"https:\/\/opticality.com\/blog\/wp-json\/wp\/v2\/posts\/9\/revisions"}],"wp:attachment":[{"href":"https:\/\/opticality.com\/blog\/wp-json\/wp\/v2\/media?parent=9"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/opticality.com\/blog\/wp-json\/wp\/v2\/categories?post=9"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/opticality.com\/blog\/wp-json\/wp\/v2\/tags?post=9"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}