{"id":258,"date":"2011-07-27T21:19:16","date_gmt":"2011-07-27T21:19:16","guid":{"rendered":"http:\/\/shivdev.com\/blog\/?p=258"},"modified":"2011-07-27T21:19:16","modified_gmt":"2011-07-27T21:19:16","slug":"wordpress-update-requires-upgrading-to-php-5-x-and-mysql-5-x","status":"publish","type":"post","link":"http:\/\/shivdev.com\/blog\/2011\/07\/27\/wordpress-update-requires-upgrading-to-php-5-x-and-mysql-5-x\/","title":{"rendered":"WordPress Update requires upgrading to PHP 5.x and MySQL 5.x"},"content":{"rendered":"

After upgrading to WordPress to 3.2 all hell broke lose! I wasn’t able to even see the blog …<\/p>\n

Your server is running PHP version 4.4.9 but WordPress 3.2 requires at least 5.2.4.<\/p><\/blockquote>\n

So I went ahead called my hosting provider and upgraded PHP and was able to see the blog but couldn’t add\/update new posts…<\/p>\n

You cannot update because WordPress 3.2 requires MySQL version 5.0 or higher.<\/p><\/blockquote>\n

Don’t Panic<\/strong> (These 5 steps worked for me and will probably get you past your little hurdle).<\/p>\n

    \n
  1. Backup your database<\/strong> (This is probably a MySQL 4.x database)<\/li>\n
      \n
    1. If you don’t know which database then<\/li>\n
    2. Open up Path_To_WP_Blog\/wp-config.php<\/li>\n
        \n
      1. define(‘DB_NAME’, ‘jb007’); \/\/ The name of the database<\/li>\n
      2. define(‘DB_USER’, ‘jb007’); \/\/ Your MySQL username<\/li>\n<\/ol>\n<\/ol>\n
      3. Create a new MySQL 5.0 database<\/strong><\/li>\n
          \n
        1. Note down credentials (Your hosting provider should have a way to get this for you)<\/li>\n
            \n
          1. $hostname<\/li>\n
          2. $dbname<\/li>\n
          3. $username<\/li>\n
          4. $password<\/li>\n<\/ol>\n<\/ol>\n
          5. Restore the Backed up 4.x database on the new 5.x database<\/strong><\/li>\n
              \n
            1. Your hosting provider should have a way to get this for you<\/li>\n<\/ol>\n
            2. Update the wp-config.php<\/strong><\/li>\n
                \n
              1. From the credentials you noted down in Step 2<\/li>\n<\/ol>\n
              2. When you login to your admin, WordPress may require a further update<\/strong> which is a painless click of a button and then you should be good to go!<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

                After upgrading to WordPress to 3.2 all hell broke lose! I wasn’t able to even see the blog … Your server is running PHP version 4.4.9 but WordPress 3.2 requires at least 5.2.4. So I went ahead called my hosting provider and upgraded PHP and was able to see the blog but couldn’t add\/update new […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[4,9],"tags":[],"_links":{"self":[{"href":"http:\/\/shivdev.com\/blog\/wp-json\/wp\/v2\/posts\/258"}],"collection":[{"href":"http:\/\/shivdev.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/shivdev.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/shivdev.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/shivdev.com\/blog\/wp-json\/wp\/v2\/comments?post=258"}],"version-history":[{"count":12,"href":"http:\/\/shivdev.com\/blog\/wp-json\/wp\/v2\/posts\/258\/revisions"}],"predecessor-version":[{"id":270,"href":"http:\/\/shivdev.com\/blog\/wp-json\/wp\/v2\/posts\/258\/revisions\/270"}],"wp:attachment":[{"href":"http:\/\/shivdev.com\/blog\/wp-json\/wp\/v2\/media?parent=258"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/shivdev.com\/blog\/wp-json\/wp\/v2\/categories?post=258"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/shivdev.com\/blog\/wp-json\/wp\/v2\/tags?post=258"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}