WordPress.org

1. spc0000
   Member
   Posted 3 years ago #

   I have upgraded my WordPress installation several times before and this is the first time I have run into any problems of great significance that I haven't been able to figure out on my own.

   My site is published at http://joylag.com/

   I've just upgraded from 2.3.3 to 2.5.1 and the problems I'm having are both HUGE and VERY ALARMING. The two most important issues that need to be addressed are as follows.

   WHERE THE HELL ARE MY POSTS?
   They are nowhere to be found... front-end or back-end. The general public cannot see them, and I cannot see them from within the wp-admin Manage Posts screens.
   
   MY SIDEBAR HAS BEEN WIPED!
   I do not recall any previous WP upgrade having any significant effect on my sidebar, but this upgrade has wiped everything clean. My sidebar was made up mostly of custom TEXT and PHP widgets, and now they are nowhere to be found. I had hoped that I would only have to drag them back and rearrange them in the order they were in before, but it seems like this isn't an option.

   I'll be honest with you...I am very nearly in tears over this.
   I would really appreciate any help that you can offer.
   Thanks.

   Shawn

2. spc0000
   Member
   Posted 3 years ago #

   UPDATE
   I think I've found the problem, but now I need help in fixing it.

   Since I was upgrading from 2.3.3 to 2.5.1, I had to make changes to my wp-config file (since the SECRET_KEY variable was added to this file in the 2.5.x release). So I used the wp-config-sample.php file as a template and copied the values over from my existing wp-config.php file. The mistake I made was that I did not delete the following snippet of code:

   // You can have multiple installations in one database if you give each a unique prefix
   $table_prefix  = 'wp_';   // Only numbers, letters, and underscores please!

   So what happened was that new duplicate tables were created in my database with the wp_ prefix. What should I do at this point? I have already run the installation for the 2.5.1 upgrade. Is the solution as simple as deleting this code snippet from my wp-config.php file? I am tempted to try this, but at this point I am going to play it safe and see what others have to say.

Topic Closed

This topic has been closed to new replies.