Resolved
Resolved in: 4.3.2
Overview of the issue
In WPML 4.3 we have introduced a new way of handling translations coming from plugins.
For that way to work, we need to scan them first.
However if you have the constant “ICL_DONT_LOAD_LANGUAGES_JS” defined, then the scan would not complete at this time as it stops loading some required scripts.
Workaround
Our developers are working on releasing a fix soon.
For now, it is recommended, at least for the initial scanning to not set “ICL_DONT_LOAD_LANGUAGES_JS” constant
Hi,
I just updated to 4.3.1 and it asked to me create .mo files afterward. I don’t know what it means and I accepted it.
Now all my translated content shows 404 error on the site. Please help me out solve this?
This sounds like a known issue which we are fixing and is coming from Yoast and WPML’s latest updates. If you have Yoast activated on your site please deactivate or change to a former version. If not please report this in our support forum.
I also have this issue, but I have set the constant.
This issue came after I updated to the latest version of WPML
This is expected I am afraid, the actual final fix will be released with WPML 4.3.2 which is coming in the next few days until then you need to keep that constant set.
It would be helpful if you mentioned what versions are effect for Yoast and WPML? So we can not update or roll back?
Sorry sure – If you are not using Yoast redirects (a premium feature) you can downgrade to version 1.0.1 to resolve it. (https://wpml.org/errata/yoast-seo-multilingual-causes-404-on-secondary-languages/)
I hope that the updated release 4.3.2 will be available soon. In my opinion, this is a major flaw in the current version of WPML.
We are working hard to have it ready ASAP.
I am on 4.3.2 and I still have the issue. BTW: There was no update notification for 4.3.2 , I deactivated 4.
4.3.1 , deleted it & then installed 4.3.2 to see if the .mo file issue would be resolved but unfortunately it is not.
You did not have notification, since starting from 4.2.8, we use staged rollout: https://wpml.org/2019/09/wpml-4-2-8-launched-through-staged-rollout/. At any time you can check for updates manually, as described in the article.
Concerning the issue, I tried to reproduce it, but no luck. Could you open the ticket on Support Forum, describe details, and share link to duplicator copy of your website in private message?
Thank you.
Seems not to be working in all cases. Still receiving this error.
Hello Dirk!
Did you already update to 4.3.3?
If you are still facing the issue, do you mind posting in our forum, so we can better help you?
Thanks,
Andrea