Problem: If you're experiencing issues with WPML where automatic translations are stuck in the queue, it might be due to plugin conflicts or incorrect settings. Solution: First, ensure that your 'Views' post type is set to 'Not Translatable' in 'WPML > Settings > Post Type Translation'. This setting is crucial as having 'Views' translatable can cause issues with automatic translations. Next, check for any plugin conflicts. Specifically, the 'WP External Links' plugin has been known to interfere with the translation process. Try deactivating this plugin to see if it resolves the issue. If the problem persists, you might need to clear the translation queue and reset the translation settings:
Navigate to 'WPML > Support > Troubleshooting'
Click on 'Cancel in-progress automatic jobs'
Clear the cache in WPML
Fix element_type collation
Synchronize local job ids with ATE jobs
Synchronize translators and translation managers with ATE
Assign translation status to duplicated content
Set language information
Fix post-type assignment for translations
After these steps, switch the translation mode back to 'Translate Everything Automatically' under 'WPML > Settings'. If these steps do not resolve the issue, it may be necessary to provide temporary access to your site for further diagnosis. Remember to back up your site before making any changes.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the problem persists, please open a new support ticket at WPML support forum.
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.
