Problem: If you're using the Uncode Theme and experiencing issues where your translated pages include buttons with internal links not pointing to the correct target language, this might be due to corrupted string packages. This problem was noted especially after editing and saving the original homepage. Solution: First, ensure that all your themes and plugins, including Uncode and WooCommerce, are updated to their latest versions. Then, follow these steps: 1. Navigate to WPML > Packages and delete the existing package for the homepage, which might be corrupted. 2. Edit and save the original homepage to allow WPML to create a new, hopefully uncorrupted, string package. 3. Reapply the translations for the homepage. 4. Repeat the process for any other affected products. If you continue to face issues, it might be helpful to switch the translation method to "WPML Translation Editor" from the WordPress Editor and reapply the translations manually.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your 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. Should problems persist, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing issues with the Uncode theme where the content of translated products does not display correctly, showing only the title and omitting other elements like custom fields, price, and description, this might be due to the theme itself rather than the Advanced Product Fields for WooCommerce plugin. Solution: We recommend checking the template used for products in the 'Theme options > Products'. If products are using a content block named 'product kopie', you should update the translations for this template. Navigate to WPML > Dashboard, resend this Content block to translation, ensure the translation is completed to 100%, and then save the changes.
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking the related 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.
Problem: You are experiencing a 404 error when trying to access archive pages, specifically the product category pages on your website. Solution: We recommend trying the workaround provided in our errata. Please visit the following link to resolve the issue with product category links not using translated slugs: https://wpml.org/errata/product-category-links-do-not-use-translated-slugs/
If this solution does not apply to your case, or if it seems outdated, 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are experiencing issues with HTML tags like
<br>
appearing in the frontend of your translated pages and need custom fields from the Advanced Product Fields Addons plugin to be translated when auto-translating products. Solution: We have resolved the issue with HTML tags appearing in translations. To apply the fix, make a small change to the original page and click the update button to trigger an update to the translation. Then, update the translation. For translating custom fields from the Advanced Product Fields Addons plugin, ensure that the plugin is compatible with WPML and follow the specific integration steps provided by the plugin.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also 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. For further assistance, please contact us through the WPML support forum.
Problem: The client set a homepage which displayed correctly in English, but the German translation at https://www.galaxymarketing.global/de/ had layout issues. Solution: We set the homepage to English under Settings → Reading to ensure it displays correctly at https://www.galaxymarketing.global/. For the layout issues on the German translation, it appears that some structural elements might have been incorrectly translated, possibly due to using the WordPress editor for translation. If you're experiencing similar issues, we recommend checking the translation for accuracy and ensuring that no structural elements were altered during the translation process.
Please note that this solution might be outdated or not applicable to your 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 issue persists, please open a new support ticket at WPML support forum.
Problem: You are experiencing an issue with the String Translation table after performing a WPML reset. This problem is not currently affecting your site's operation but could become critical in the future. Solution: If you have not yet completed any translations, we recommend resetting WPML again and reconfiguring it. Please follow these steps: 1. Navigate to WPML → Support and click on the Troubleshooting link. 2. In the Reset section of the Troubleshooting page, check the "I am about to reset all translation and language data" box. Then, click the "Reset and deactivate WPML" button. For detailed instructions, visit WPML Reset Documentation. Before making any changes, ensure that you back up your database.
This solution might be irrelevant if it's outdated or not applicable to your 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 issue persists, please open a new support ticket at WPML Support Forum.
Problem: The client's homepage in English was showing only the latest posts instead of the translated content, even though it was translated and working fine in the past. Solution: 1. We asked the client to check if the posts were translated. 2. We requested a screenshot of the permalinks settings for the English language. 3. We advised the client to provide WPML debug information. 4. We suggested navigating to Settings → Reading to check the homepage configuration for English. 5. We recommended increasing the WP_MEMORY_LIMIT value to at least 256M. 6. We instructed the client to switch the homepage settings to 'Latest Posts', save it, then change it back to a static page and save again. 7. Upon further investigation, we found that the issue was not related to WPML. The header on the English homepage was set to display posts. We provided a screenshot for reference and corrected the header to point to the correct template, which resolved the issue.
If this solution does not apply to your case, or if it seems outdated, we encourage you to open a new support ticket. We also highly recommend checking related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you need further assistance, please contact our support forum.
Problem: The client wants to import Italian product translations into their site, which already contains products in the main language, German. They have a CSV file with the Italian translations, including columns for SKU, name, short description, and description.
Solution: Here are the steps to follow:
Export your default language content using WP All Export.
Edit the exported CSV to add a column for the unique identifier.
Delete the original content from the site.
Import the default language CSV file with the unique identifier column as New items.
After importing the default language content, proceed with importing your secondary language file.
If you need to connect translations programmatically, you can use the
wpml_set_element_language_details
hook. However, we do not provide custom coding services. For examples and explanations, check out our documentation on wpml_set_element_language_details and related support forum discussions. If you require further assistance with custom coding, consider hiring a professional from our list of WPML contractors.
Please note that this solution might be outdated or not applicable to your case. If the provided solution does not resolve your issue, 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 you still need help, please open a new support ticket in our support forum.
