Problem: You are facing issues with dynamic image linking in the slider on custom post type pages, and custom fields translated via ACF are not appearing in the translated version. Solution: We found that the 'acf-post-type' was set to 'translatable'. It's important not to modify locked post types. If you're experiencing this issue, we recommend checking the settings for your custom post types and Advanced Custom Fields (ACF). Ensure that the 'acf-post-type' is not set to 'translatable' if it should not be modified. Additionally, verify that all necessary fields are correctly configured in ACF for both the original and translated versions.
This solution might be 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 issue persists, please open a new support ticket at WPML support forum.
Problem: You are trying to implement automatic translation on your WordPress site using the Oxygen builder and are considering using the Deepl API with WPML.
Solution: Currently, the Oxygen page builder is not compatible with WPML, which means you cannot automatically translate your site using this setup. You will need to translate content manually. We recommend contacting the Oxygen builder's author to request a compatibility update. For developers looking to make their themes/plugins compatible with WPML, we provide detailed guidance and support. You can find more information on achieving WPML compatibility for themes and plugins at https://wpml.org/documentation/support/achieving-wpml-compatibility-for-your-themes-and-plugins/. Additionally, theme and plugin authors can join WPML’s Go Global program to ensure their products are multilingual ready. More details are available at https://wpml.org/documentation/support/go-global-program/.
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 you still need assistance, please open a new support ticket at WPML support forum.
Problema: Stai cercando di tradurre il tuo sito web con WPML, utilizzando WooCommerce e il tema Travel WP di PhysCode. Hai riscontrato un problema con lo slug 'tours' che funziona solo in italiano. In inglese, il prefisso della lingua non viene inserito correttamente, risultando in un errore 404. Soluzione: Il problema potrebbe essere legato agli slug. In WPML > Impostazioni, lo slug per i tour dovrebbe essere impostato come 'prodotto'. Se non riesci a modificare questi permalink direttamente, potrebbe essere necessario contattare l'autore del tema per assistenza, poiché modifiche ai permalink possono essere rischiose e l'autore del tema non è stato cooperativo in passato.
Se questa soluzione non risolve il problema o sembra non essere più attuale, ti consigliamo di aprire un nuovo ticket di supporto. Ti raccomandiamo inoltre di consultare la pagina dei problemi noti e di verificare che tu abbia installato le versioni più recenti dei temi e dei plugin. Per ulteriore assistenza, visita il forum di supporto WPML.
Problem: The client translated an Italian page into English using WPML, but the translated page still displays the original Italian text. This issue arises because the WPBakery widgets used on the page are not officially compatible with WPML, preventing some parts from being available for translation. Solution: We added custom XML configuration to WPML > Settings to register the WPBakery widgets for translation. Here is the code we used:
We recommend contacting the theme author to request their participation in our Go Global program for better compatibility. Additionally, follow our guide on using different translation editors for manual adjustments or to add compatibility code for other widgets.
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 for further assistance at WPML support forum.
Problem: You are trying to resolve an issue where the updated PLN prices via BaseLinker's API are visible in the WooCommerce product backend but do not reflect on the frontend without manual updates. This behavior differs from EUR prices, which update immediately. Solution: Firstly, BaseLinker is not officially compatible with WPML, which might be causing the issue. We recommend contacting BaseLinker's authors to consider joining our GoGlobal program to work towards compatibility: https://wpml.org/documentation/support/go-global-program/ If PLN is your second currency and you are updating it, WPML synchronizes changes when the post is saved. You might need to trigger a re-save of the post using hooks like
save_post
or
update_post
. This approach may require additional custom coding. For custom coding, consider hiring a contractor from WPML: https://wpml.org/contractors/
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 for further assistance.
Problem: If you're experiencing issues with translating elements added by the Democracy Poll plugin or the Joli Table Of Contents Pro using WPML, here's what we found and recommend.
Solution: 1) Democracy Poll: This plugin does not support direct translation. We recommend creating separate polls for each language. For example, if you have a poll in English with ID 1, create a Czech version with ID 2. Then, use the translated shortcode in String Translation, replacing the poll ID accordingly. 2) Joli Table Of Contents Pro: Although the "Table of Contents" string can be brought into String Translation, translating it might not impact the frontend due to the plugin's code not following proper internationalization methods. We suggest contacting the plugin support for compatibility issues or referring them to WPML’s Go Global program (https://wpml.org/documentation/support/go-global-program/).
If these solutions do not resolve your issues or if they seem outdated, we highly recommend checking related known issues (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: When navigating through the main menu on a multisite setup using WPML with subdomains, the AJAX request URL incorrectly switches to an English URL (https://en.fme.de/wp-admin/admin-ajax.php), causing the site to fetch English content instead of the intended language. This issue persists despite disabling related plugins and occurs specifically when using the Divi FilterGrid. Solution: 1. Ensure that your WPML plugin and all related add-ons are updated to the latest version. You can check and update from WPML Installation Guide. 2. Verify that the issue isn't due to a compatibility problem between WPML and the Divi FilterGrid. If you're using posts or pages within the grid, change their settings in WPML > Settings > Post type translation to 'Translatable'. 3. Check if the issue also occurs with a regular Divi grid widget or only with the FilterGrid addon. 4. If the problem is due to the plugin not being officially compatible with WPML, consider contacting the plugin author to discuss making the plugin compatible through WPML's GO Global program. More details can be found here: GO Global Program. 5. For AJAX calls, ensure proper language handling by following the guidelines provided here: Handling AJAX with WPML.
If these steps do not resolve your issue or if the solution seems outdated or irrelevant to your specific case, we highly recommend checking related known issues at WPML 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: The client is trying to translate their website using WPML, but only one section of the homepage is being translated, and the footer is not visible in the translated version. The theme used, 'Service Finder,' is not WPML compatible, and there are issues with outdated plugins and new/custom Elementor widgets. Solution:
If these steps do not resolve the issue or if the solution seems outdated or irrelevant, 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: https://wpml.org/forums/forum/english-support/
Problem: You have set up the multi-currency function in WPML with German as the default language and linked the currency CHF to the German language. However, when visiting a product page, the currency switches back to EUR after 2 seconds. Solution: This issue is related to the
BM_Update_Price::update_price()
method, which is hooked to AJAX. To fix this, you need to add it to our AJAX filters using the wcml_multi_currency_ajax_actions filter. Add the following code to the functions.php of your theme:
// WPML Workaround for compsupp-7663<br />add_filter( 'wcml_multi_currency_ajax_actions', 'wpml_compsupp7663_add_actions_to_multi_currency_ajax', 10, 1 );<br /><br />function wpml_compsupp7663_add_actions_to_multi_currency_ajax( $ajax_actions ) {<br /><br /> $ajax_actions[] = 'update_price'; // Add a AJAX action to the array<br /> return $ajax_actions;<br /><br />}
Please test this solution and provide feedback. If it resolves the issue, we recommend sharing this workaround with the plugin developers.
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.
