Timeline for WordPress Odd migration issue
Current License: CC BY-SA 3.0
21 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Sep 14, 2017 at 2:10 | history | bounty ended | CommunityBot | ||
| S Sep 14, 2017 at 2:10 | history | notice removed | CommunityBot | ||
| Sep 8, 2017 at 16:59 | answer | added | Jeff Mattson | timeline score: 0 | |
| Sep 6, 2017 at 16:14 | comment | added | Luis Sanz |
Have you checked if liwys is assigned to the $table_prefix variable in your wp-config.php?
|
|
| Sep 6, 2017 at 15:30 | answer | added | The Filipino Freelancer | timeline score: 0 | |
| Sep 6, 2017 at 4:55 | history | edited | Johansson |
edited tags
|
|
| Sep 6, 2017 at 4:55 | answer | added | Johansson | timeline score: 1 | |
| Sep 6, 2017 at 2:42 | comment | added | giolliano sulit | It looks like you installed a new Wordpress install over your old database. You probably didn't copy of the wp-config.php from your old server which is why you got this settings page.. | |
| S Sep 6, 2017 at 0:47 | history | bounty started | Nitescu Lucian | ||
| S Sep 6, 2017 at 0:47 | history | notice added | Nitescu Lucian | Draw attention | |
| Aug 29, 2017 at 12:06 | comment | added | Tom J Nowell♦ | you don't want to downgrade, it was a guess that you'd moved to an older version that didn't support the collation you needed to use, have you verified the SQL is correctly formatted and not mangled? You will need to remove the existing tables before running it again or it'll skip over them | |
| Aug 29, 2017 at 9:26 | comment | added | Nitescu Lucian | @TomJNowell No I did not downgraded mysql to an older version on the new serve. Any Idea how to do it? | |
| Aug 29, 2017 at 3:18 | answer | added | Rick Hellewell | timeline score: 0 | |
| Aug 29, 2017 at 2:05 | comment | added | Tom J Nowell♦ | Have you downgraded mysql to an older version on the new server? Note that you can't just open the sql file in a text editor and change the URL via search replace, it'll mangle any serialised PHP present generating problems. You have to use a dedicated search replace tool such as WP CLI to do the change | |
| Aug 29, 2017 at 0:16 | history | edited | Nitescu Lucian | CC BY-SA 3.0 |
added 276 characters in body
|
| Aug 28, 2017 at 23:50 | history | edited | Nitescu Lucian | CC BY-SA 3.0 |
Running generic WordPress database fix.
|
| Aug 28, 2017 at 23:42 | comment | added | Nitescu Lucian | WordPress database error: [Table 'liwys_users' already exists]. The only two errors. @TomJNowell | |
| Aug 28, 2017 at 23:39 | comment | added | Nitescu Lucian | Yes, yes, yes its written: WordPress database error: [Unknown collation '#224' in table 'liwys_options' definition] | |
| Aug 28, 2017 at 23:33 | comment | added | Tom J Nowell♦ |
did you do a search replace on the SQL file to change URLs? And did you change the wp-config.php to use the new database credentials? Also, can you show us the database errors in that screenshot? All the useful parts are cropped out
|
|
| Aug 28, 2017 at 22:32 | review | First posts | |||
| Aug 29, 2017 at 3:18 | |||||
| Aug 28, 2017 at 22:30 | history | asked | Nitescu Lucian | CC BY-SA 3.0 |