Problem: The client is using a custom function to add menu items to a WordPress menu based on user login status. However, when adding the WPML language switcher, the custom menu items appear after the language switcher instead of before it. Solution: We recommend modifying the function to ensure that the custom menu items appear before the WPML language switcher. You can use the following code:
add_filter('wp_nav_menu_items', 'add_custom_menu_items_before_wpml', 10, 2);<br />function add_custom_menu_items_before_wpml($items, $args) {<br /> // Your new menu item(s)<br /> if (is_user_logged_in()) {<br /> $custom_items = '<li><a href="' . esc_html_x('/conta/', 'Botão no menu de navegação URL', 'lwp') . '">' . esc_html_x('Conta ', 'Botão no menu de navegação', 'lwp') . '</a> </li>';<br /> $custom_items .= '<li><a href="' . wp_logout_url() . '">' . esc_html_x('Sair ', 'Botão no menu de navegação', 'lwp') . '</a> </li>';<br /> } else {<br /> $custom_items = '<li><a href="' . wp_registration_url() . '">' . esc_html_x('Registar ', 'Botão no menu de navegação', 'lwp') . '</a> </li>';<br /> $custom_items .= '<li><a href="' . esc_html_x('/conta/', 'Botão no menu de navegação URL', 'lwp') . '">' . esc_html_x('Entrar ', 'Botão no menu de navegação', 'lwp') . '</a> </li>';<br /> }<br /> // Find the WPML language switcher and insert before it<br /> $pattern = '/(<li[^>]*class="[^"]*menu-item-wpml-ls[^"]*"[^>]*>)/i';<br /> if (preg_match($pattern, $items, $matches)) {<br /> $items = preg_replace($pattern, $custom_items + $matches[1], $items, 1);<br /> } else {<br /> // Fallback if language switcher not found — append instead<br /> $items += $custom_items;<br /> }<br /> return $items;<br />}
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 WPML support forum.
Problem: You are trying to translate a modal box on a global CTA bar using WPML. The Gravity Form is translated, but the title of the modal box and the close button are not appearing in the translation strings. The title uses the dynamic title of Avada, which is similar to the container text and is translatable. Solution: To make the title of the modal box translatable, we added a custom XML configuration. Please add the following code to your WPML settings:
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 further assistance is needed, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
Problem: The client attempted to use a code snippet from a WPML forum post to exclude the product title from automatic translation for testing purposes, but it did not work. The client actually wants to exclude only the main product description from automatic translation while keeping the title and short description translatable. Solution: We explained that the provided code was a basic example and needs adaptation to meet specific requirements. Since the client wants to modify WPML’s default behavior, which is complex, we recommended consulting with a certified WPML contractor for tailored assistance. A list of certified freelancers can be found at https://wpml.org/contractors/.
If this solution does not apply to your case, or if it seems outdated, please check the 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 further assistance is needed. You can do so at WPML support forum.
Problem: The client wants to configure WPML to use different domains for different languages and add a custom NGINX rule so that when users visit specific URLs (like fishingbooker.de/blog), they are redirected to the corresponding language version on the main site (fishingbooker.com/blog). Solution: We recommend using an NGINX reverse proxy to route traffic from each language-specific domain to the appropriate language directory on the main WordPress installation. Here is an example of how you can set up the NGINX reverse proxy:
Please ensure SSL, cookies, and caching are properly managed, as these are crucial for WordPress and WPML functionality. Note that this solution is not a WPML-native feature and falls outside our standard support. If you need further assistance with server configuration, consider contacting a certified WPML developer from our list of contractors.
This solution might be outdated or not applicable to your specific case. If it doesn't resolve your issue, 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 our support forum.
Problem: You are trying to synchronize products from an ERP system to your WordPress website and want to add English translations simultaneously to avoid manual translation later. Solution: We recommend using the WordPress REST API in conjunction with WooCommerce Multilingual to automate the process of creating both the original product and its translation. You can find more details on how to implement this here. Please note, this type of custom integration is outside our standard support scope. If you need further assistance, consider reaching out to a WPML-certified developer here.
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. Should you need further assistance, please do not hesitate to open a new support ticket here.
Problem: Der Klient hat Inhalte ursprünglich auf Deutsch erstellt und später WPML verwendet, um die Website auf Englisch zu übersetzen. Nach der Umstellung der Originalsprache auf Englisch wurden die bereits erstellten deutschen Inhalte fälschlicherweise als Originalinhalte betrachtet. Der Klient möchte wissen, wie er die Zuordnung von Bildern, Tags und anderen Elementen zur richtigen Sprache korrigieren kann, sodass alle Elemente als Originalsprache Englisch sind. Solution: Wir haben erklärt, dass die Standardsprache von WPML keinen Einfluss auf die Sprache hat, in der die originalen Inhalte erstellt wurden. Um die Zuordnung manuell zu korrigieren, sollte der Klient eine Übersetzung im WordPress Editor öffnen und in der rechten Seitenleiste den Eintrag "This is a translation of:" auf "None" setzen und die Seite speichern. Dadurch wird die Übersetzung nicht mehr mit dem originalen Inhalt verbunden. Anschließend kann der Klient die Option "Connect with translations" verwenden, um den Inhalt mit einem anderen Inhalt in einer anderen Sprache zu verbinden. Ein Dialog wird erscheinen, in welchem festgelegt werden kann, welcher Inhalt nun der neue originale Inhalt sein soll. Mehr Informationen finden Sie unter: https://wpml.org/faq/how-to-link-already-translated-pages/
Falls diese Lösung veraltet ist oder nicht auf Ihren Fall zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu eröffnen. Wir empfehlen auch, die Seite mit bekannten Problemen (https://wpml.org/known-issues/) 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.
