{"id":3916,"date":"2010-04-18T15:28:50","date_gmt":"2010-04-18T20:28:50","guid":{"rendered":"http:\/\/danigirl.ca\/blog\/?p=3916"},"modified":"2010-04-18T15:31:19","modified_gmt":"2010-04-18T20:31:19","slug":"well-that-was-a-trip-through-bloggy-hell","status":"publish","type":"post","link":"http:\/\/danigirl.ca\/blog\/2010\/04\/18\/well-that-was-a-trip-through-bloggy-hell\/","title":{"rendered":"Well, that was a trip through bloggy hell"},"content":{"rendered":"<p>I had nothing but the best of intentions when I set out to upgrade both my WordPress installation and my Thesis theme last night.  With infinite idealism, I told Beloved I&#8217;d need &#8220;30, maybe 45 minutes, tops.&#8221;<\/p>\n<p>That was 16 hours ago.  I didn&#8217;t spend *all* of that 16 hours trying to recover everything that got farked up, but it was more than six hours.  Maybe close to eight.  And you know, I don&#8217;t usually plan for eight hours of blog maintenance in the average weekend.<\/p>\n<p>But victory is MINE!  I&#8217;ve recovered almost all the customization settings I lost.  Phew!  And even better, I found a solution for a problem that&#8217;s been vexing me for the best part of six months now.<\/p>\n<p>Just in case it&#8217;s been vexing you, too, and because I am deeply proud of myself for figuring out a solution when I was swimming in waters way over my geeky little head, here&#8217;s the problem and the solution.<\/p>\n<p>I&#8217;d been losing WordPress dashboard functionality for a while.  I&#8217;d lost the widgets that show incoming blog links and recent comments, for example.  And, the reason I did the upgrade is because I&#8217;d intermittently lose the ability to edit a page.  And then I started getting 500 Internal Server Errors.  What a mess!  I&#8217;d figured out that it was related to plug-ins, so set up to update all of those, too.<\/p>\n<p>Long story short, the WordPress upgrade went okay, but the Thesis theme upgrade completely wiped out some of my custom settings.  It took me *hours* just to recover those, but they were not related to the core functionality of the blog.  The larger problem was the previously intermittent problems with functionality became suddenly severe.  I&#8217;d get random 500 Server Errors when trying to post a new article or page, or the plug-in page would disappear.  Eventually, I disabled every single plug-in and was *still* having trouble.<\/p>\n<p>I googled &#8220;plug ins and internal server errors&#8221; and found a whole bunch of articles about people using my host (1and1.com) having this problem.  One post suggested editing the .htaccess file and adding a couple of lines of code.  I was afraid, very afraid.  The .htaccess file is a bit of a mystery to me, but I know it&#8217;s at the core of my server-blog relationship &#8212; severing this might just sever the bloodflow to the blog entirely!  After consulting with my in-house tech support (thanks, Beloved!) I went ahead and added the following lines of code to the .htaccess file:  AddType x-mapp-php5 .php  AddHandler x-mapp-php5 .php  And damn if it didn&#8217;t fix everything!  (Well, the functionality issues.  It still took me hours to repair the lost customizations.)  Apparently, my host needed special instructions to tell the blog to read php 5 instead of php 4.  Or something like that.<\/p>\n<p>Anyway, I am deeply pleased with myself.  Performing this bit of codery was not unlike performing open-heart surgery on the blog, and things were dicey for a while there, but it looks like the patient will make a full recovery.  How people can do this for a living is beyond me!<\/p>\n<p>I&#8217;m happy to report that all is well now, except for the hours of lost time.  Oh well, it&#8217;s not like the floors won&#8217;t still be dirty tomorrow, and the unfolded laundry has waited patiently for my return.<\/p>\n<p>\/geekout<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I had nothing but the best of intentions when I set out to upgrade both my WordPress installation and my Thesis theme last night. With infinite idealism, I told Beloved I&#8217;d need &#8220;30, maybe 45 minutes, tops.&#8221; That was 16 hours ago. I didn&#8217;t spend *all* of that 16 hours trying to recover everything that &hellip; <a href=\"http:\/\/danigirl.ca\/blog\/2010\/04\/18\/well-that-was-a-trip-through-bloggy-hell\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Well, that was a trip through bloggy hell&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[22],"tags":[],"class_list":["post-3916","post","type-post","status-publish","format-standard","hentry","category-editorial-asides"],"_links":{"self":[{"href":"http:\/\/danigirl.ca\/blog\/wp-json\/wp\/v2\/posts\/3916","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/danigirl.ca\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/danigirl.ca\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/danigirl.ca\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/danigirl.ca\/blog\/wp-json\/wp\/v2\/comments?post=3916"}],"version-history":[{"count":2,"href":"http:\/\/danigirl.ca\/blog\/wp-json\/wp\/v2\/posts\/3916\/revisions"}],"predecessor-version":[{"id":3918,"href":"http:\/\/danigirl.ca\/blog\/wp-json\/wp\/v2\/posts\/3916\/revisions\/3918"}],"wp:attachment":[{"href":"http:\/\/danigirl.ca\/blog\/wp-json\/wp\/v2\/media?parent=3916"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/danigirl.ca\/blog\/wp-json\/wp\/v2\/categories?post=3916"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/danigirl.ca\/blog\/wp-json\/wp\/v2\/tags?post=3916"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}