1. Not as far as I can remember. It's been over a year since we started building the site so it is possible, but as far back as I remember, Swedish has been the default language.
2. WPML was one of the first plugins installed so it should have already been there when most pages were built.
Up until the 1.8.1 (perhaps even 1.8.0) update to ACFML I have not experienced anything like this problem.
According to our findings so far, this issue is not related to ACF and ACF Multilingual. I'll now explain this assumption.
Even if the site is in a minimum environment (The theme is switched to 2021 WP default theme, and all the plugins except WPML, String Translation, and Translation Management are deactivated, the following occurs.
A. If you try to translate an old page that its translation is complete, the Advanced Translation Editor does not show. The page gets refreshed, and nothing happens.
B. In the debug.log, the error message shows.
Undefined property: stdClass::$status_id in /wp-content/plugins/wpml-translation-management/classes/ATE/class-wpml-tm-ate.php on line 57
When I deactivate WPML on your site, I can see that English is the default language. Please see the attached screenshot. This probably means that English was set as the default language while setting up WordPress. And Swedish was set to be the default language by WPML. This is why I asked if the default language has ever been changed.
I'm now escalating this issue to our second-tier supporters, and they will continue to investigate. We'll keep you updated here.
Our second-tier supporters might want also to check things on the staging site.
However, if you need to use it, then go ahead and use it. We also have a copy of your site.
Our developers recognized the issue that I mentioned in my reply on the 3rd of March as a bug. That issue will fix in a future version of WPML and the Advanced Translation Editor.
If you have any translation jobs that you need to be fixed, please share their ID with us, and our developer would manually fix those until the fix is deployed to production.
When the version with the fix is released, I'll update you here.
I'm sorry, but this issue is still not fixed on the ATE server. As I mentioned in my previous reply, you can give me the job IDs of the translation jobs that you lost their translations, and our developers will manually fix those specific jobs for you.
