Problem: The client is working on a site under development and wants to change the custom post type (CPT) label to the Korean language. Solution: If you're trying to change the custom post type label to Korean, we recommend using the WPML String Translation module. First, ensure that you have scanned all related plugins for translatable strings in WPML > Theme and Plugin Localization. After scanning, go to WPML > String Translation and search for the CPT name. You can then add the translation directly there. For more detailed guidance, please check our documentation for developers at https://wpml.org/documentation/support/.
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 this does not resolve your issue, please open a new support ticket at our support forum.
Problem: The client is unable to display the Polish translation of the footer on their website, despite having renamed the Polish footer and being able to locate it via WPML translation management. The footer is integrated using the shortcode '[fl_builder_insert_layout slug="footer"]' in the Customizer.
Solution: We recommend the following steps to resolve the issue: 1. Ensure you have a full backup of your website. 2. Delete the Polish footer by navigating to Beaver Builder > Vorlagen, switching the language to Polish at the top-bar, and sending it to the trash. 3. Permanently remove the item from the trash. 4. Return to the German version of Vorlagen and click on the '+' sign to add a translation to Polish. 5. Name it 'Footer' and set the type to Footer. 6. Select 'copy content from German'. 7. Create the translation.
After following these steps, the footer should display correctly in Polish.
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 the problem persists, please open a new support ticket at WPML support forum.
Problem: You are working on a site under development and trying to translate strings using WPML, but some strings are not translated. Solution: We have checked your website and noticed that the strings you mentioned are now properly showing translated in English. Please confirm if your issue has been resolved.
If this solution is outdated or does not apply to your case, 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: You are experiencing an issue where you cannot save or edit translations due to an error message: 'Updating failed. The response is not a valid JSON response.' This problem is likely related to the reverse proxy settings on your live website. Solution: First, ensure you have a full backup of your site as the settings involved are sensitive. Then, follow these steps: 1. Add the following code to your theme's functions.php file:
If these steps do not resolve the issue or if the solution seems 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 problem persists, please open a new support ticket.
Problem: Sie arbeiten an WooCommerce-Produktseiten und haben ein Problem mit der Anzeige eines Custom Fields und einer Taxonomy in verschiedenen Sprachversionen (EN, FR), die trotz vorhandener Daten nicht im Frontend erscheinen. Sie verwenden Beaver Themer und steuern die Ausgabe über Shortcodes. Solution: Um das Custom Field für die Übersetzung verfügbar zu machen, folgen Sie diesen Schritten: 1. Öffnen Sie den Übersetzungseditor. 2. Klicken Sie in der Liste der benutzerdefinierten Felder auf „Neu eingeben“. 3. Fügen Sie „per_product_item_cost“ im Feld „Name“ ein. 4. Geben Sie den entsprechenden Wert ein und speichern Sie Ihre Änderungen. Für die Taxonomy 'lieferzeit', da diese Inhalte unabhängig vom Original sind und nicht über die WordPress- und WPML-Oberfläche im Bulk hinzugefügt werden können, müssen diese manuell und einzeln hinzugefügt werden. Eine Alternative wäre, das Feld direkt über die Datenbank oder mithilfe einer Import-Tabelle hinzuzufügen, was jedoch außerhalb des WPML-Supports liegt.
Falls diese Lösung veraltet ist oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Wir empfehlen auch, die Seite mit bekannten Problemen zu überprüfen, die Version der dauerhaften Lösung zu verifizieren und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben. Für weitere Unterstützung besuchen Sie bitte unser Support-Forum.
Problem: You have an ACF Taxonomy field on a WooCommerce attribute set to Copy, expecting the settings in the original language to automatically apply to the secondary language. However, the fields are editable in the secondary language but are not updating or taking the value of the primary language, leaving all secondary language taxonomy radio lists empty. Solution: We have identified that the taxonomy field requires you to click the update button twice for the changes to reflect correctly in the secondary language. We have documented this issue in our errata. For a temporary workaround, please follow this step: 1. After making changes in the primary language, save and then click the update button again. For more details, refer to our errata here: https://wpml.org/errata/taxonomy-custom-field-metadata-set-to-copy-requires-double-save-for-updates-to-reflect/
If this solution does not resolve your issue or seems irrelevant due to being 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. Additionally, please feel free to open a new support ticket for further assistance at our support forum.
**Problem:**
The user (cristianS-23) reported that WPML displayed a notification indicating "90 translations waiting for review," but no translations were found in the queue under Posts, Pages, Products, or Knowledge Base sections. The user wanted to resolve this issue and ensure it does not recur.
**Solution:**
1. **Investigation:**
- Confirmed no translations were marked as "waiting for review" in the interface.
- Identified that the issue likely stemmed from incorrect entries in the `icl_translation_status` database table.
2. **Fix:**
- Suggested editing the database to update the `review_status` column in the `icl_translation_status` table to `'ACCEPTED'`.
- Clarified that this might fix the immediate issue but noted the root cause could be related to plugin or theme conflicts.
3. **Implementation:**
- User manually applied the suggested database change, which resolved the issue.
4. **Preventive Action:**
- Advised disabling the review feature if not required to prevent similar issues.
- Provided steps to disable the feature:
- Navigate to **WPML > Settings**.
- Under **Automatic translation**, select **"Publish right away without reviewing"** and save the settings.
**Outcome:**
The issue was resolved, and the user chose to mark translations as accepted before disabling the review feature. Additional support was offered but not required.
