Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • In my case, I made sure that the following in the WP-config file are filled up correctly. I contacted Yahoo to be sure that the name of the database and the password are working properly. Also in the original download DB_HOST is not ‘mysql’. I changed it to ‘mysql’.

    // ** MySQL settings ** //
    define(‘WP_CACHE’, true); //Added by WP-Cache Manager
    define(‘DB_NAME’, ”); // The name of the database
    define(‘DB_USER’, ”); // Your MySQL username
    define(‘DB_PASSWORD’, ”); // …and password
    define(‘DB_HOST’, ‘mysql’); // 99% chance you won’t need to change this value
    define(‘DB_CHARSET’, ‘utf8’);
    define(‘DB_COLLATE’, ”);

    When I upgraded, everything came out perfectly even though by then my database was already empty. The point is: the tables are set up properly by the old WordPress version, and the new version just picked up from there.

    Hope this helps.

    Scribu is right. My blog is hosted by Yahoo. Yahoo’s WordPress version is still 2.3. I refused to upgrade to 2.5 or to 2.6 because of problems in upgrading. I damaged all my blogs while doing so 3 times and reconstructed them 3 times. After the third reconstruction the problem that you now have started appearing. I could never access my blogs again. Finally, I gave up and upgraded to 2.6. For the 4th time I reconstructed my files. It took me longer than a week to do it. See the final product. And I am happy I upgraded. I believe the problem is one way WordPress is forcing everybody to upgrade. The problem I currently have (it is posted here) is: my feed does not validate because of blank line 1.

    By the way for Yahoo hosted blogs. The installation from scratch and the so called famous 5-minute installations were all the causes of my files destruction. IF YOU CAN, UPGRADE ONLY! IN THAT CASE YOUR FILES FROM THE OLD WORDPRESS VERSION ARE HELD INTACT. BE SURE TO BACKUP YOUR FILES BEFORE ATTEMPTING TO UPGRADE.

Viewing 2 replies - 1 through 2 (of 2 total)