Compatibility

Problem:
The client is experiencing issues with the menu and footers not displaying correctly in translation on a Betheme template, despite updating the code in the theme's

functions.php

file.
Solution:
We recommend verifying and increasing the WordPress Memory Limit as it is currently set below the recommended minimum, which can affect the display of translated strings. Here are the steps to follow:
1. Go to WPML → Support and check the current memory limit.
2. If it's below 128MB, increase it to at least 128MB (256MB is preferable for optimal performance).
3. After adjusting the memory limit, re-process the strings to see if the issue with the menu and footers is resolved.

If this solution does not resolve the 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 at WPML support forum for further assistance.

Problem:
You are trying to display product options such as Tile color, Decoration color, and Corner decorations in German on your website using the WPML plugin. However, the YITH WooCommerce Product Add-Ons & Extra Options are not showing in the translated version of the website.
Solution:
We have identified that the product was originally created in English, but the filter (block) was configured in English with a German product assigned to it. To resolve this, go to YITH → Product Add-Ons → Blocks (https://delfterfliesen.de/wp-admin/admin.php?page=yith_wapo_panel&tab=blocks), open each block, and assign the English version of the product (the original language), then save.

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. If issues persist, please open a new support ticket at WPML support forum for further assistance.

Problem:
The client was unable to remove a specific translation from their website. Despite deleting the string translation, it still appeared on the site. Additionally, WPML seemed to be injecting or overriding text in the FunnelKit plugin, specifically the text 'Besteed nog X voor kabel organizer tas (t.w.v. 14.99)', which did not match the configured text in FunnelKit.
Solution:
We suggested updating WPML to the latest version and deleting some strings that might be causing the issue, but this did not resolve the problem. We then set up a fresh WordPress installation for the client to replicate the issue. The client was instructed to install the FunnelKit plugin on this clean setup and check if the problem persisted. If the issue was reproducible, we planned to escalate it to our compatibility team. Eventually, the client discovered that the issue was within the FunnelKit plugin itself, specifically in a language tab that might only appear when WPML is active. The problem was resolved after identifying this.

Please note that this solution might be outdated or not applicable to your case. If you're experiencing similar issues, we 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:
The client is unable to locate the Divi Flash FAQ module in WPML's String Translation. Additionally, extra identifiers are appearing on the French page after switching to Classic Translation mode, and the English translation in WPML differs from the original content.
Solution:
For the Divi Flash FAQ module not being recognized by WPML, we recommend updating your custom XML configuration. Please ensure to have a backup and follow these steps:
1. Navigate to WPML > Settings > Custom XML Configuration.
2. Update with the following code:

<wpml-config><br />    <shortcodes><br />        <shortcode><br />            <tag label="FAQ Item">difl_faqitem</tag><br />            <attributes><br />                <attribute label="FAQ Question" encoding="allow_html_tags">question</attribute><br />                <attribute label="FAQ Answer" encoding="allow_html_tags">content</attribute><br />                <attribute label="Question Image Alt Text">close_que_img_alt_txt</attribute><br />                <attribute label="Open Question Image Alt Text">open_que_img_alt_txt</attribute><br />                <attribute label="Answer Image Alt Text">answer_image_alt_text</attribute><br />                <attribute label="Button Text">button_text</attribute><br />                <attribute label="Button URL" type="link">button_url</attribute><br />                <attribute label="Question Image" type="media-url">close_question_image</attribute><br />                <attribute label="Open Question Image" type="media-url">open_question_image</attribute><br />                <attribute label="Answer Image" type="media-url">answer_image</attribute><br />                <attribute label="Admin Label">admin_label</attribute><br />            </attributes><br />        </shortcode><br />    </shortcodes><br /></wpml-config>

3. After saving this configuration, edit the FAQ Item on the original page, save the page, and open the translation editor. You should now see the strings of the module inside the translation editor.

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. If the problem persists, please open a new support ticket.

Problem:
Der Kunde hat Probleme mit der korrekten Anzeige von übersetzten Elementor-Templates in einem Slider, der mit dem ElementsKit Widget Advanced Slider erstellt wurde. Die Templates werden nicht sprachspezifisch geladen, und es scheint, dass WPML dieselbe Slider-Struktur für beide Sprachen (DE und EN) verwendet.
Solution:
Das ElementsKit Widget Advanced Slider speichert Inhalte in einer speziellen Weise, die nicht den Standard-Elementor JSON-Daten entspricht. Daher kann der WPML-Übersetzungseditor diese nicht automatisch erkennen. Um dieses Problem zu beheben, sollten Sie den Beitragstyp

ElementsKit items (elementskit_content)

in WPML > Einstellungen > Beitragstypen als "Übersetzbar" markieren. Anschließend können Sie die entsprechenden Beiträge unter WPML > Übersetzungs-Dashboard übersetzen, indem Sie Übersetzungs-Jobs erstellen und diese entweder automatisch übersetzen lassen oder einem Übersetzer zuweisen. Die fertigen Übersetzungen können dann unter WPML > Übersetzungen abgerufen werden.

Falls diese Lösung veraltet erscheint oder nicht auf Ihr Problem zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Überprüfen Sie auch die bekannten Probleme und stellen Sie sicher, dass Sie die neuesten Versionen Ihrer Themes und Plugins installiert haben.