Recent content by carlsson

I have double- and triple checked that there actually is a new database created for the cloned site, and that new database (wp_zckvu) is the one that the clonedsite.com is using. I have checked privileges as well. I assume they use the same table names, haven't checked. It shouldn't be a...

…and furthermore; I made some changes in the wp-config file, and now when I go to clonedsite.com I end up on originalsite.com. This tells me there are more locations that store the original site url, and probably the reason for all this mess. Gaaah....!

A more comprehensive answer; In wp-config I have: …and all tables in the database start with that.

One more thing that I just realized – I get different results if I go to www.clonedsite.com and just clonedsite.com! With www it actually tries to log in, but fails when it tries to reach the wp panel without www…? (btw; I'm only using private browsing to avoid any caching issues)

Yes they do.

Followup: I found this article, and have updated originalsite.com to clonedsite.com in 12 tables, and I still get the same error… :confused:

(This may or may not be related to Plesk. However, there's a lot of brilliant people here that may be able to help me.) I have a multisite that have given me some headache. I haven't built the solution, but provide hosting and maintenance. Recently I updated WP to 6.5.2 from 6.4.4. After that...

Followup from Plesk support since this can help future people in the same situation: "When prefix database mismatch was generated, WP-Toolkit detected the WordPress instance as broken, because of that, the restore probably didn't work. Plesk backup would have worked, with the option "Restore...

Plesk support have helped me with this now, and it seems to work! I wonder though, why the WPT Restore didn't work from start? @nmdpa3 : I will definitely take a look at backup extensions, I don't want this to happen again… o_O Thank you guys for your help, highly appreciated!

Thank you for your help Kaspar! I have contacted Plesk and are awaiting their feedback. My feeling is that the solution is very easy for someone that knows everything about Plesk, WP, Linux and mySQL... I am obviously not that person. :rolleyes:o_O

After restoration I got this: And also this in WPT:

Thanks, it might come to that.

The dump is 411 MB . I created an SQL database with same name, user and pw as before and imported the dump. Now I have restarted Plesk (just in case) and I'm currently doing a restore again.

Dump created before I did a Remove Database, then WPT> Restore, after 10 minutes I got this error: …and then this: "WordPress installation www.mysite.com (#26) is not available for current operation because it is broken" Something tells me the restore couldn't restore the database...?