Skip to main content

How To Downgrade Your Wordpress Installation

I recently updated one of my Wordpress installations to 3.5 from 3.4.2 and found out that 3.5 really isn't ready for release as it appears to have a slew of problems.

So, what to do?  Downgrade back to 3.4.2, obviously.  A quick Google search brought up this great article with some good steps to follow: http://etuts.org/manually-downgrade-wordpress/

Here are the steps, with my notes:

  • Log into the administrative backend of your Wordpress installation and deactivate all your plugins (important)
  • Create a backup of your site including the database for safety's sake ( or at least download all the files including those in the root directory, especially wp-config.php)
  • Delete the \wp-admin and \wp-includes folders of your site either with your FTP client or through the backend cPanel of your hosting company.  File Manager in cPanel is a lot quicker than through FTP.
  • Find the Wordpress 3.4.2 (or whatever version you are going to downgrade to) files:  http://wordpress.org/download/release-archive/ and unzip locally.
  • Upload the following to your site
    • root folder files
      • May not be necessary, but without doing it, I ran into errors
      • Remember to re-upload your old wp-config.php file, though, because it has your database settings in it.
    • /wp-admin
    • /wp-includes
  • Log into the administrative backend of your site and it should ask you to Update Your Database. Go for it.
That's it. Most important things to remember are to make a backup of your site, overwrite the files in the root directory (which is what made it work for me) and then re-upload your wp-config.php file from your previous installation.





Comments

  1. I followed these instructions step by step, but for some reason, i know only see a blank webpage when loading the site! Can you help?

    ReplyDelete
    Replies
    1. No error at all? Did you go to http://yoursitename.com/wp-admin ?

      Usually, errors would be some PHP error or something to at least point you in the right direction (ie...db setup incorrect or something).

      Delete

Post a Comment

Popular posts from this blog

How To Run Chrome From Within Notepad++

If you have recently tried to Run  Chrome from within Notepad++ recently, you've probably encountered the same issue I did.  Chrome didn't run. The fix is actually really simple.  Open up the Run box in Notepad++ and browse to your installation of Chrome. ie.  C:\Program Files\Google\Chrome\Application\Chrome.exe Select the file when you find it.  Now, the trick is: Put quotation marks around the path you see in the Run  box.  Now, put 1 space after the closing quotation mark. Type this: $(FULL_CURRENT_PATH) It'll look something like this: Click Run .  If Chrome opens, click Save and set your hotkey.

Developer Note: Virtuemart - Editing the Add to Cart MooTool Popup

To edit the “Add To Cart” popup that appears when you add an item to a cart in Virtuemart, there are few files that you need to know about. These are the files to know \components\com_virtuemart\themes\default\theme.js \components\com_virtuemart\js\mootools\   - contains the files for editing the appearance of the popup. To edit the appearance of the box, edit \components\com_virtuemart\js\mootools\mooPrompt.css to change the styles as well as editing the 2 images in the directory to edit how they appear as well (close box and header-background)

Proper Viewport Scaling on iPad and iPhone

So, this is a little silly and I'm a little embarrassed to say that I've spent far too much of my time on this issue. I had a multi-page site that wasn't displaying correctly on my iPad.  One page would look great, but the next would have the top menu cut off on the right and everything would be slightly zoomed in. I realized that it was a scaling issue, but for all the experimenting I did with the meta viewport tag , I couldn't get it to work. Then I thought of something...some pages didn't have as much content as the others.  The longer pages were displaying great, it was the pages short on content that weren't.  So, I went ahead and set a min-height for each page of 1050px (I figured it had to be a little larger than the 1024px portrait height of an iOS device) and voila, it worked. All the pages showed correctly.  Now, I fully admit that this is most likely a hack that isn't considered the "proper way", but I am absolutely open to sugge...