Not much - just the header/footer/and individual pages [not all], couple products [exactly, so no biggie]. One post from Taprooms [culture pub] and... I left untranslated all default post type posts and products on purpose. And header's menu. So really not much by comparison. If it goes - it goes.
Can you provide us with access to the dev site? Please also confirm if made any changes to it, since migrating.
The required fields to share access can be found below the comments section. The information you enter is private, i.e. only you and I can see it and have access to it.
Right, witnessed that old table with my own eyes via phpMyAdmin.
10web support is being such a shitshow - they cannot reply to me how to correctly reinstall WP on their system and instead pointing me, that I have the latest WP version installed and I don't need to d anything. This is frustrating AF
Just as an update: we understood what's going on, but still haven't identified the cause yet. The devs are still analyzing. Please note that at the moment, your production website is stable, and you haven't lost any data.
WPML is apparently duplicating posts and not finishing the translation process properly (that's why we saw the duplicated posts in EN). That's what we're checking to fix, but overall your website's safe. It's getting tricky to find the specific cause, but I'm sure we'll find it.
Until them, we'll need you to have some patience, thanks for that! It's in our hands now.
Could it take a week, month? On staging2.sektahouse everything works fine, while migrated to 10web it fails. Database tables you mentioned - maybe we should get rid of them manyally and try to re-migrate the site once again?
Just wipe all database files on 10web and try to migrate the site again? Are those large actionscheduler entries at fault?
It's best not to change the production website, as we are still investigating it. Yes, a DB cleanup in this case could help, but first we are trying to understand what's causing this issue.
It will take at least a few more days, as we had to get a third developer involved in your case. Please leave the production website as is for the moment. I appreciate your patience.
The development team wants to do a clean up on your database, to remove the duplicate entries. We tested that on a local copy of your website, and had no issues, but it's mandatory that you have a complete backup of the current production website before we proceed. Can you please do that and get back to me?
