Problem: The client was experiencing an issue where some translated content was not displaying on the front end of a WooCommerce product page. The content was managed via the Gutenberg editor and involved a shortcode. Despite the content being visible in the Advanced Translation Editor, it was not rendered on the front end for certain tabs. Solution: We discovered that the issue was due to the [GK-TABS-BREAK] being mistakenly treated as a real shortcode during translation, which led to its duplication and subsequently broke the tab layout. To resolve this, we modified the code in the theme's shortcode file. Here are the steps we took:
Made a minor edit in the default language product to trigger a retranslation.
Completed the translation in the WPML Advanced Translation Editor.
This solution resolved the issue, and the translated content now displays correctly on the front end. However, please be aware that this fix might become irrelevant due to future updates to the theme or WPML. If you encounter similar issues or if this solution does not work for you, we 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.
. You expected to see three indices: one English, one Spanish, and one Chinese. However, you encountered an error indicating that you have reached the limit of indices your plan supports. After deleting empty indices and attempting to sync a single language, you received the same error. Solution: We have confirmed that the WPML Elasticpress plugin creates an index per language, and the indices are always created regardless of the posts populated. This behavior is expected under the current system. We are considering this issue as a potential feature request for future updates, but we cannot guarantee when or if this will be implemented.
If this solution does not resolve your issue or 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 visit our support forum at WPML Support Forum.
Problem: The client needs to translate page slugs in multiple languages except for Chinese, where they want to keep the original slug untranslated. They were unable to find an option to exclude only one language from slug translations and had issues reverting already translated slugs. Solution: We advised the client to navigate to WPML > Settings > Translated documents options. Under Page URL, they should select the Translate option and save the changes. This setting allows the slug to appear in the translation editor, where the client can choose to either copy the original slug manually or translate it for each language. For existing pages, after applying this setting, the client should update the page or post in the default language and then access the translation editor to see the option to translate the slug.
If this solution does not apply to your case, or if it seems outdated, 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 issues persist, please open a new support ticket.
