Upgrade failed, go back or go on?

  • Resolved wordshine

    (@wordshine)


    15 years, 2 months ago

    The manual upgrade to 2.9.1 failed, wanting MySQL 4.1.2 but not advising me until the end. How can I go back? I don’t have access to the dashboard, plugins are turned off as advised so spam is getting through. I took a backup immediately before the upgrade.

    Is this the right forum? I posted in the “How to” forum without response, but traffic there is amazingly high.

    I can’t reinstall 2.8.6 because it was an automatic upgrade which is no longer available. I have located 2.5.1, but I don’t know if it is compatible.

    I have been offered access to a newer server running PHP 3.2.4 and MySQL 5.0.87. If I migrate the MySQL database to the new server, will the upgrade complete when it recognises a MySQL version it wants? Or would I still have to fix the incomplete upgrade on the new server? If I go to the new server, how do I stop/restart the MySQL service just with cpanel, without a shell session, in order to copy the files? I can’t find it anywhere in the documentation.

    It seems to me the surest way through all this is to roll back the upgrade. That might mean restoring from backup, but I’m not sure.

    I would appreciate some advice. I really need it. It’s been 19 hours since I started the upgrade.

    Thanks.

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

  • You can download the 2.8.6 version here and reupload 2.8.6 via FTP.

    Also, WP requires PHP is 4+ so do not downgrade to PHP 3.2.4 at all.

    Re: nobody helping – it might just be a matter of time zone or availability of this almost all-volunteer forum.

    Good luck.

    Thread Starter wordshine

    (@wordshine)

    mercime,

    Now why didn’t I find that earlier? Thanks. I’m on my way.

    It happens ??

    Thread Starter wordshine

    (@wordshine)

    Phew! Thanks again.

    I’m back up with 2.8.6 and now I’ll migrate to the new server so I can complete the upgrade. Here’s hoping…

    Thread Starter wordshine

    (@wordshine)

    Cripes! I’ve just re-read your first response. I hope I can persuade my provider to install PHP 4.

    Better yet, persuade your provider to upgrade to PHP5 for performance at the very least and so you won’t miss out on plugins requiring PHP5, among many other reasons for PHP5

    Thread Starter wordshine

    (@wordshine)

    My provider migrated my site to a newer server running PHP5 and MySQL5. But many of the WordPress files were corrupted in the process.

    The corruption is similar to that which occurs moving a document from a Mac to a PC: extended ASCII characters get replaced by a small string of incorrect characters.

    Could it be PHP5 that is doing this? Is there a fix? I can, if I want to, repeat the migration, as the original site still exists.

    I don’t want to go through perhaps 200 files correcting the corrupted symbols.

    One thought: the WordPress editor does a good job translating, for example, a dash surrounded by spaces into an em rule, or straight quotes into typographical quotes. However I enter many of these characters directly with the keyboard codes. Does this, perhaps, upset PHP5?

    Thanks.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Upgrade failed, go back or go on?’ is closed to new replies.