Tell us what you are trying to do? Restore a back-up of the website. The restore process would not complete and was timing out. I contacted iThemes/BackupBuddy (the developer of the plugin we use to make/restore back-ups. They suggested to exclude that wp_icl_languages database from the restore. We did that and the restore worked. However, I want to confirm with WPML if wp_icl_languages is needed or if it was fine to exclude it.
Is there any documentation that you are following? A support ticket with iThemes/BackupBuddy.
Is there a similar example that we can see? No.
What is the link to your site? hidden link However, the DNS info has not been updated to point the domain to the new host. So to see the copy of the website that was restored, you will need to add this to your hosts file:
You can exclude it though in the event that the table with all the latest entries is already there (on the destination), these entries being your custom languages. Other than that, this table would not be filled with any information such as translations or similar.
It is strange though that this table in particular would cause timeouts because it only consists of 65 rows or simple data, if that (it depends upon the number of your custom languages + preconfigured WPML languages).
Thanks for confirming that Bruno. We are looking into things with the back-up/restore plugin and the host. I have tried the restore again with nothing excluded. The database restore does get further, but stops at one of the other wp_icl tables.
Languages: English (English )German (Deutsch )French (Français )
Timezone: Europe/Zagreb (GMT+02:00)
You can perhaps try with https://wordpress.org/plugins/duplicator/ or https://wordpress.org/plugins/all-in-one-wp-migration/ to see if possible to move the website using any of these, this may tell you whether the problem is indeed in corrupt database tables or a timeout. Perhaps it happens only with icl_ tables because of the order in which these are being migrated/restored, so if the process stops after a certain amount of time, it would always stop on icl_ tables which would being restored at that point.
