WordPress.org

1. Dgold
   Member
   Posted 5 years ago #

   WP 2.2 broke so many things on my blog (frontend theme, and backend admin). 2.2 is an unmitigated disaster, for me. I've spent many hours trying to fix problems, and I've even paid WP-Pros to help. I still have critical errors such as a broken RSS feed, and Admin pages that go blank after posting.

   What should I do?

   (1) Wait for WP 2.2.1 and hope it fixes the problems?

   (2) Try to rollback to WP 2.0.x? If so -- how?

   (3) Quit using WordPress and give up? (Kidding... sort of.)

   I'm seriously thinking about Option #2, but I am worried about what will happen and how to do it. Will WP 2.0.x be able to read my database that has been altered by WP 2.2?

   Or do you advise that I delete my 2.2 database, delete my whole site, and reinstall from a 2-weeks old database that was from 2.0.x, and then reinstall WP 2.0.x?

   p.s. To anyone still helping me in the other threads (about my broken RSS and blank admin screens), please continue assisting because I might leave a test blog in 2.2 for trying to fix those problems.

2. whooami
   Member
   Posted 5 years ago #

   Will WP 2.0.x be able to read my database that has been altered by WP 2.2?

   No, a lot was changed in the db schema

   if all you have is a 2 week old backup and you want to roll back -- thats more or less what you are left dealing with.

   You can also dig posts out of google's cache is you have a decent idea of what to look for, and you dont restrict google from caching your site.

   -------

   General response to all your other posts:

   While 2.2 might seem to be 'broken" when reading the forums- we need to remember that this is a support forum, not a "im happy as a pig in crap" forum :P so the majority of what's seen is going to be related to problems.

   I've been admittedly lucky in all of my wordpress upgrades and installs, in that Ive never experienced the problems that other have (except for a minor permalink problem with UTW that I solved in a matter of minutes)

   My 2.2 bigbox install was fresh, and all my stuff works. I have to guess that it might not have gone so well had I actually upgraded my live site -- I don't know, and I'm not willing to test it :P

   My point is, I suppose, that, my uneducated eye tells me its upgrades that are issues, and not necessarily fresh installs. You just might want to do a fresh install of 2.2 and see how it works, without the problems you've had since upgrading. You might even find yourself migrating all your content over to that fresh 2.2 by "hand" (one post at a time)

   For what its worth, I'm hosted on asmallorange :)

3. drmike
   Member
   Posted 5 years ago #

   But I am happy as a pig in crap. It was even my wp.com avatar today:

   http://a.wordpress.com/avatar/drmike-128.jpg

   :)

4. whooami
   Member
   Posted 5 years ago #

   are those 2 pigs?

5. Dgold
   Member
   Posted 5 years ago #

   Thanks again whooami.

   I agree about the nature of a Support Forum. I understand & I want to be clear that I am not Anti-WP, or Anti-2.2. Although I am frustrated by it.

   I've had WP since before 1.5, and I've probably Upgraded at least 5 times (not to mention, 3 different installs of WP, all of which upgraded as many times). I've had minor upgrade problems that I always fixed (such as needing to upgrade a plugin). I have Never had this much problems, or these kinds of problems, or problems that were hidden to me at first but popped up later (like discovering that my RSS isn't working, a week later). So I really regret that I upgraded to 2.2. I should have considered it more carefully at first, instead of assuming it would be as easy as all previous upgrades. Also I really think WP should have put better descriptions of the changes and possible effects, in the announcement -- especially the changes in Template Tags that affects All the 1000's of people who had Kubrick since WP 1.5. I've fixed that, but it was the beginning of me getting frustrated by spending so many hours fixing things.

   -----

   I saw you mentioned your host. Do you think my host is part of my problems? For example is it the host's mod_security settings, and that isn't coming from WP? I moved servers within the same host, purely so I could meet the requirements of 2.2. At the time, I thought it was worth it, and thought the newer server was an upgrade (higher version of PHP and mysql, and cpanel instead of Ensim control panel).

   ----

   I'll probably follow your rollback steps, deleting everything, reinstalling everything, and re-writing my posts from the last 2 weeks.

   I think I will copy-paste all my recent posts into a Text File first, rather than the Google cache method. (I can see my posts fine right now, that isn't the problem on my site, so it's not a recovery effort).

6. slodaddy
   Member
   Posted 5 years ago #

   Would this be an acceptable alternative? Create a new install of WP in a new subdirectory, then use the import function to import posts from the troubled install, then copy the index.php and htaccess to root so the new install is visible at domain root.

7. whooami
   Member
   Posted 5 years ago #

   I mention my host not necessarily because of mod_rewrite -- I have it available, and use it. Religiously :)

   I know you aren't anti-WP :) I was hoping to direct that to others that might be here for the first time, actually, and see all the 2.2 problem posts ..

   I "discovered" one minor issue with the codex insructions re. upgrading this morning, and it goes to your remarks about your theme problems.

   The detailed instructions suggest that you don't delete wp-content/

   I really don't agree w/ that suggestion.

   Obviously, a good deal of the themes that were used in 2.0 and prior are going to see immediate errors.

   If i were me, and I were doing an upgrade - I would delete wp-content/ also and upload the new wp-content/ w/ the 2 provided themes.. (just to make sure that I circumvented all the theme-related issues.

   Then, I would work on putting back the pieces of my old theme. It's more time consuming, sure, but it's probably less stressful. :P

   Your issues, the feed not working, etc.. I really think, like I said, that its the upgrade, not necessarily the WP core causing the problems.

8. moshu
   Member
   Posted 5 years ago #

   Re: not deleting the wp-content

   Another consequence of that instructons is that people don't upgrade Akismet on their blog: I have seen blogs where the owners diligently upgraded their WP but the antispam plugin was five versions behind...

9. Dgold
   Member
   Posted 5 years ago #

   FIXED!!!! Mud on my face!! The error was mine --- a "space" at the end of a plugin file.

   2 big errors I had are not the fault of WP 2.2 after-all. It happened when I reconfigured a plugin right after upgrading. It was a space in a plugin file. I don't know how that space got there. I could have narrowed it down earlier, if I had followed diagnostic techniques properly and consistently (Deactivate All Plugins and Re-activate one-by-one, testing for the error). When I realized 1 plugin caused both errors, I looked in the plugin file and there was a space at the very end. I deleted the space and the blog snapped back to normal like magic. This fixed 2 of my major problems simultaneously: (1) the RSS feed validator error, and (2) the blank-pages in the admin after pressing "Publish" or "Save" or "Edit Comment".

   LESSONS LEARNED*
   (and by "learned" I mean, I already knew it before, but it slapped me upside the head)

   (1) STARTING POINT for error-diagnosis: De-activate ALL plugins. Yes 100%, don't skip any. If that breaks your theme, then switch to the Default or Classic Theme temporarily. Your blog is still alive there? Are the errors present? Re-activate plugins One by One, with another browser window open to reload the site and test for the error.

   (2) A plugin or any php file cannot have a SPACE at the beginning or the end. CHECK the start & end of those plugin files for spaces!

   I spent a lot of time looking into how Upgrading broke my site, and not enough time trying the Basic Starting Point diagnosis tests.

   Thank You to everyone who reads the Support forums to give advice and share techniques. Several people specifically spent time on my questions today. The support here is invaluable. At least 4 people mentioned specifically that I needed to check for a space in a plugin file, or that I needed to deactivate all plugins and reactivate one-by-one. I know the Codex advises it too. Forum volunteers -- don't forget to recommend that n00bs like me, really-actually definitely do the basic things like deactivate all the plugins. Thanks again.

10. whooami
    Member
    Posted 5 years ago #

    look at all those resolved threads :)

Topic Closed

This topic has been closed to new replies.