Timeline for WordPress Odd migration issue
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 29, 2017 at 18:55 | comment | added | Rick Hellewell | If the 'target' system is fully borked, but your 'source' system is OK (content, etc), you could just blow away the entire 'target' WP folder and install a fresh/new WP. Then install the WP-Clone plugin on source and target, and backup source and restore target. Depends on whether target system is (or was) 'live'. You might check if the hosting place has an older backup to restore entire site + databases. | |
| Aug 29, 2017 at 18:52 | comment | added | Rick Hellewell | If you have phpMyAdmin access, you should be able to update/change the db credentials. Then use those credentials in the wp-config.php file. You might rename the wp-content/plugins folder to something else to temporarily disable all plugins. The point is to get admin access. You might also try manually FTP a fresh WP copy from local computer, changing the wp-config.php file (or not copying that file). Once you get admin access to a basic site, you can copy plugin folders to a new wp-content/plugins folder, then activating. | |
| Aug 29, 2017 at 9:25 | comment | added | Nitescu Lucian | Well unfortunately I can not boot the old server at all (only in safe mode) and there I have the same problem (WordPress on localhost, with all fixes). Therefore I can not run any plugins at all. :/. Actually this is the main reason behind the migration | |
| Aug 29, 2017 at 3:18 | history | answered | Rick Hellewell | CC BY-SA 3.0 |