Problem:
The client needed assistance with translating the Cartflows Store Checkout page as there were no visible translation options. Solution:
Step 1: We navigated to WPML > Settings > Custom Fields Translation and enabled the option
Show Multilingual Content Setup meta box on the post edit screen
. This action allows the custom fields for each content to be visible at the bottom of the WordPress Editor. For further guidance, we provided a link to the documentation: Translating Custom Fields.
Step 2: On the Checkout Page Editor, we configured the fields for options and layout to
copy
and text fields to
translate
, thus opening up the translation.
Step 3: If there are still missing strings for translation, we advised the client to identify which fields control the text and set them to
translate
.
Additionally, we noted that the client switched the translation method to
Classic Translation Editor
at WPML > Settings > Translation Editor. We reminded the client that translations made in the Classic Translation Editor are not available in the Advanced Translation Editor (ATE). If issues arise with ATE, we recommended clearing the browser's cache and trying again. If problems persist, we advised the client to inform us.
Please note that this solution might be irrelevant due to being outdated or not applicable to your case. If so, 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 you still need assistance, please open a new support ticket.
Problem: The client is experiencing a critical error on their website after installing the WPML String Translation plugin. Solution: We recommend enabling the WordPress debug log to identify the specific PHP error causing the issue. To do this, edit the
wp-config.php
file in the WordPress directory and insert the following lines:
After adding these lines, try to reproduce the issue. The debug log will be located in
/wp-content/debug.log
. The client should then paste the content of the debug log on a site like pastebin.com and share the link with us for further assistance. Relevant Documentation: https://codex.wordpress.org/Debugging_in_WordPress
If the provided solution does not resolve the issue or seems irrelevant due to being outdated or not applicable to your case, we encourage you to open 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 in the WPML support forum.
