We've migrated a copy of our production site manurefetish.com to a secondary domain as a development site (scatstream.com).
However it seems after setting everything up and the migration was complete that WPML is a bit broken right now. Products can't be opened on the frontend as we receive a critical error then. Also we've switched our theme and now use elementor as our new page builder, here it's unclear how to translate the elementor templates as in translation managment they are not showing.
Thank you for contacting WPML support, I’m happy to help you with this issue.
Please enable WP debug log and visit the frontend again to see the critical error, then share the log file with me. I can download it and take a look at it, and determine where to go from there.
If you don't know how to enable WP debug log, please follow the documentation https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/
I also suggest you enable a minimal environment to see if it helps:
- Deactivate all plugins except WPML plugins and WooCommerce.
- Switch to a standard theme of WordPress.
❌ IMPORTANT: Please backup your database and website before proceeding ❌
Hi Long,
thank you for replying, I will enable the debug log when I'm back at work on Monday, then I will share the log file with you.
However one error/bug I could fix. It seemes that for products because I was using a template I've created, I had to also translate and save the template to get it working.
Also for the tanslation I found out that under Templates > Saved Templates, I can open them like I would open a page/post normaly and from there I can select If I want to translate it with WPML advanced translator or the classic, which is exactly what I've wanted.
We've ACF Field Groups for example for our Products. The Field group name should stay the same however only the field should be translateable for the second language.
However so far the field show up in the second language, but some ACF fields are locked from editing and in others, where some of the translated/custom content could be put in, it's not saving.
Under WPML Settings, Post Type Translation there's the field Field Groups (acf-field-group) With translateable is set to no. I've tried the other two settings out, however then WPML wants to translate the names of the whole field groups and field type names.
This is not exactly what we want, the Field Groupes and Types should stay the same only the content should be translateable.
New threads created by Long Nguyen and linked to this one are listed below:
So I understand the issue with the "Products can't be opened on the frontend as we receive a critical error then" is resolved. We can handle one issue per ticket only so I will split your new issue with ACF fields translation to a new ticket for better handling.
Yes it seems to be resolved right now, didn't have a single error after I've also translated the templates used on the main language in the second language.
