Cornerstone and WPML critical error

[salilou]

Hi,
I use Pro, Cornerstone and WPML in the latest version.
After one or two of the latest updates a critical error occurs when opening the cornerstone pagebuilder.
If I deactivate WMPL, it works.
Have you heard of any complications?
Hope you can help.
Best regards,
Hannes

[tristup]

Hi Hannes,

Unfortunately, no issue has been reported until now. I would suggest you troubleshoot the following common issue to help us to recognize the reason.

1. Theme Related Issue
2. Plugin Conflict
3. Theme Update related issue
4. Child Theme Related issue ** if you have activated it.
5. CSS/JS Customization
6. Disabling Cache
7. Disabling CDN

If you discover that an issue is coming from a custom code or 3rd party plugin, kindly consult with a developer or contact the plugin author. Please note that we do not provide support for custom codes and 3rd party plugins.
If that does not help, please provide login credentials for your site in a secure note to examine it further, including:

– WordPress Site URL & Login URL
– WordPress Admin username/password
– FTP/CPanel credentials to access the file.

To create a secure note, click the key icon underneath any of your posts.

Thanks

[salilou]

Thank you. Everything is up to date.
Conflict found only in WPML.
Here are the credentials in a secure note.
Thank you very much!

[achtideen]

I have the same problem.

[tristup]

Hi Hannes,

I have checked the said plugin version 4.2.6 with the Pro latest version in my local environment, and it worked perfectly fine. It might be a problem with version 4.6.3 with the latest version of Pro. I will check it with our development team and will add it to the Issue Tracker for further investigation.

Thanks

[charlie]

Can you turn on WP_DEBUG for this site or let me know what the Critical Error is? I’m getting weird results in my document list in the latest version, but not a critical error.

[salilou]

OK, it is done!

[charlie]

I think you have a translation that no longer has post content in it. I believe in the WPML troubleshooting page there are actions to remove translations that have deleted posts. They do recommend doing anything on that page in a staging environment first.

On our end I can ensure we don’t have a fatal error in another release. I do have an out for you though for now. Add this to your child theme and it won’t try to to move the layout that doesn’t exist. It goes by translation data to move the post types in Pro6 and this filter just stops the migration from happening which is where your fatal error is. Let me know if you have questions.

add_filter("cs_wpml_use_untyped_migration", "__return_false");