This thread is resolved. Here is a description of the problem and solution.
Problem: If you're experiencing issues with the design of your page breaking when translating a Toolset template from Dutch to German, it might be due to errors in the original language version of the Content Template. This could involve Single Field blocks with dynamic sources referencing fields from a field group that no longer exists. Solution: We recommend checking if the field group referenced by the dynamic sources in your template is unassigned or missing. If a relevant field group was accidentally deleted, consider restoring a backup from when the template was functioning correctly. Alternatively, you should edit the original language template to remove all references to the non-existent field groups. Ensure the template can be edited and used without errors before proceeding with the translation.
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Also, check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum at WPML support forum.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Background of the issue:
I'm trying to translate a Toolset template from Dutch to German on my site hidden link. I've tried using both the advanced and classic editor.
Symptoms:
The translation breaks the design of the page.
Questions:
Why does translating the Toolset template break the design of the page?
How can I translate the Toolset template without breaking the design?
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: America/Lima (GMT-05:00)
Hello,
I would like to offer to have a closer look at the problem and request temporary access (wp-admin and FTP) to the website to investigate this issue further.
You can find the required fields below the comment section when you log in to leave the next reply. The information you provide is private, which means only you and I can see and access it.
IMPORTANT
Please be sure to make a backup copy of the website and database before allowing us access.
If you can't see the wp-admin / FTP fields, your post and website credentials are set as PUBLIC. DO NOT publish the data unless you see the required wp-admin / FTP fields.
I may have to install a plugin called "All In One WP Migration" to make a copy of the website where I can investigate the issue further.
However, I would also be very grateful if you could provide a staging site or copy of the website from your server yourself for this purpose. This step would only be required if the issue is replicable on such a staging site.
If you have any questions about creating such a staging site, you can consult your hosting provider. Just take note that WPML should be registered on this site again.
If you are unable to provide such a copy of the site for testing, please let me know on this ticket.
The private response form looks like this: hidden link
Next time you reply, click "I still need assistance."
Video: hidden link
Please note that we are obliged to request this information individually on each ticket. We may not access any access information not specifically submitted on this ticket in the private response form.
Our second-tier supporter found that the template in Dutch is faulty. Please see the attached screenshot, which may explain the problem with the translation.
Please allow us to take a copy of your site to investigate this issue. I must install a plugin like Duplicator or All In One Migration. Please let us know if you agree.
I can see that the Duplicator plugin has already been installed on your site. So, I used it to create a copy of your site and sent it to our second-tier supporters. When I have news from our second-tier supporters, I'll update you here.
Our second-tier supporter has investigated the issue further and found the following:
Upon reviewing a local copy of your site, it appears that the original language version of the Content Template, which contains errors, includes Single Field blocks with dynamic sources that seem to reference fields from a field group that might no longer exist.
The field group, as seen in the screenshot, is unassigned, and there’s no option to select a field group for the source. Additionally, under Toolset > Custom Fields, only one field group is assigned to the "Camping" post type, but this field group doesn’t contain any fields.
If this worked in the past, it’s possible that a relevant field group was accidentally deleted. In that case, you may want to consider restoring a backup from when the template was functioning properly.
Alternatively, you will need to edit the original language template to remove all references to the non-existent field groups. Once that’s done, ensure the template can be edited and used without any errors before proceeding with the translation.
I have checked the concerning field group, but on my end the correct field group is selected and not empty. See attached screenshot. Might something have gone wrong with the export?
In any case, i will try to fix the errors in the template.
