Problem: You are trying to translate ACF select field values using WPML but are seeing the original language values instead of the translated ones. Solution: We recommend checking the ACF Field Group settings for your 'dough' field. Change the return format from "Value" to "Label". This adjustment is necessary because the 'get_field' call currently retrieves the value, which is not translatable. By switching to "Label", you enable the translation of these labels in choice fields like Select fields.
If this solution does not resolve your issue or seems outdated, please visit our known issues page to check for related problems. Ensure you have the latest versions of themes and plugins installed. If needed, do not hesitate to open a new support ticket on our support forum for further assistance.
Problem: The client was unable to save translations in the WPML Advanced Translation Editor due to issues with HTML formatting markers not being correctly applied or accepted. Additionally, the client could not save the edited window or finish the translation. Solution: We advised the client to ensure that the HTML formatting in the translation matches the default language. Specifically, if the default text includes a
<span>
tag enclosed within an
<a>
tag, the translation must replicate this structure. The client should select the text in the translation box, apply the Span tag, and then apply the Anchor tag to align with the default language's structure. Furthermore, if issues persist, we recommended switching back to the previous version of the Advanced Translation Editor by: 1. Clicking the gear icon in the top right corner of the editor. 2. Enabling the option 'Use the previous version of the Advanced Translation Editor.' 3. Applying the marker and saving the translation. Ultimately, the issue was resolved by unregistering and re-registering WPML on the client's WordPress site, which required generating a new site key due to a URL change.
If this solution does not resolve your issue, or if it 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. If further assistance is needed, please open a new support ticket at WPML support forum.
The client needs to translate the string 'Pay by Card' but is experiencing issues.
Solution:
We recommend ensuring that the string 'Pay by Card' has been translated via WPML>>String Translation Dashboard. If the problem persists, please follow these steps:
1. Perform a site backup. 2. Navigate to WPML>>String Translation and enable the 'Look for strings while pages are rendered' option in the 'Auto register strings for translation' section at the bottom of the screen. 3. Visit the frontend pages, specifically the Checkout page, to see if the issue still exists. This setting will automatically disable after a few hours but is crucial for identifying the problem in similar cases.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 needed, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: The client is building a bilingual website using WPML, The Events Calendar Pro, and Event Tickets. They encountered an issue where the RSVP form does not appear on the event page, and the RSVP block is not saved when WPML is activated. Disabling WPML resolves the issue. Solution: We created a sandbox environment for the client to replicate the issue. It was suggested that the client should try creating a basic RSVP block in the sandbox to see if the problem persists. This step is crucial to determine if the issue is specific to the client's current setup or a general problem with the plugins and theme used. Additionally, we noted that there are known issues with The Events Calendar, but this particular problem with RSVP forms is not currently recognized as one.
If this solution does not resolve your issue or 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. If the problem persists, please open a new support ticket.
Problem: The client is unable to see the option to translate Practice pages created by the CEA plugin on their website. Solution: If you're experiencing this issue, it's likely that the post type used by the CEA plugin is set to 'Not Translatable' in the WPML settings. To resolve this, you should change the translation preference for this post type to 'Translatable'. You can follow the steps outlined in our guide on translating custom post types: Translating Custom Posts.
This adjustment should make the translation options visible for these posts. If the solution provided here is outdated or does not apply to your case, 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 issues persist, please open a new support ticket.
Problem: The client wanted to remove the automatic translation feature in WPML to avoid using credits unintentionally and requested a refund for credits used due to accidental automatic translations. Solution: 1. We explained that the 'Translate Automatically' button cannot be removed from the Advanced Translation Editor (ATE) as it is loaded from an external server and is the same for all users. 2. We clarified that once credits are used, they are non-refundable as the payment goes to the selected translation engine. For more details, please refer to this link. 3. We suggested switching to the Classic Translation Editor via WPML->Settings, which does not use automatic translation. More information can be found here: this link. 4. As a one-time courtesy, we attempted to refund the 1000 credits mistakenly used. After locating the correct account, we refunded 1050 credits.
If this solution does not resolve your issue or seems outdated, please 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. We highly recommend opening a new support ticket if needed.
