Problem: Sie versuchen, Ihre Webseite mit WPML zu übersetzen, verwenden jedoch das LAY Theme, das mit Projekten und nicht mit Seiten arbeitet. Sie haben festgestellt, dass nur der Titel übersetzt wird, während der Rest der Webseite leer bleibt und neu angelegt werden müsste. Lösung: Das von Ihnen verwendete LAY Theme ist derzeit nicht in WPMLs Verzeichnis der kompatiblen Themes gelistet. Sie können dies überprüfen unter: https://wpml.org/theme/. Es könnte sich um ein Kompatibilitätsproblem handeln. Das Theme verwendet einen anderen Editor mit eigenen Elementen, und es ist unklar, ob diese Elemente im Backend als Shortcodes oder anders dargestellt werden. Wir empfehlen, die Theme-Support-Team zu kontaktieren und um Unterstützung bei der Übersetzung der Inhalte zu bitten. Außerdem könnten Sie das Theme-Entwicklerteam bitten, am Go-global-Programm von WPML teilzunehmen, um die Kompatibilität zu verbessern. Weitere Informationen zum Go-global-Programm finden Sie hier: https://wpml.org/documentation/support/go-global-program/. Falls diese Lösung nicht relevant ist, weil sie veraltet ist oder nicht auf Ihren Fall zutrifft, empfehlen wir Ihnen, ein neues Support-Ticket zu öffnen. Wir empfehlen auch, die Seite mit bekannten Problemen zu überprüfen (https://wpml.org/known-issues/), die Version der dauerhaften Lösung zu überprüfen und zu bestätigen, dass Sie die neuesten Versionen von Themes und Plugins installiert haben.
Problem: The client is experiencing issues with the 'WooCommerce Quantity Discounts, Rules & Swatches' plugin on their multilanguage site using WPML. While the discount rules work correctly on the default English version of the site, they do not apply correctly on the translated versions of the product pages. Additionally, the second price option is not selected by default in the foreign languages as it is in English. Solution: We resolved the issue by ensuring that the discount rule values are copied to other languages: 1. Navigate to WPML > Settings > Custom Fields Translation and click on "Show system fields". 2. Search for the field "_wqm_tiers" and set the preference to "Copy", then save the changes. 3. Edit the product in the English language and click on Update to apply these changes to the translations. For the issue of the default quantity option not being selected, follow these steps: 1. Set the custom field "_wqm_settings" preference to "Translate". 2. Update the product in the original language and its translation to ensure the default quantity option is copied to the translated product pages. Refer to the documentation on translating custom fields for more details. Note: The 'WooCommerce Quantity Discounts, Rules & Swatches' plugin is not listed in our compatible plugins directory. We recommend contacting the plugin author to join our Go Global program to ensure full compatibility with WPML. Learn more about the program here: Go Global program.
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. If the problem persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: If you're experiencing issues with MyListing theme where images are not appearing under the correct language, this might be due to a compatibility issue between the theme and WPML. Solution: We recommend contacting the theme author and inviting them to join our GoGlobal program. Our compatibility team will be glad to assist in making their product WPML compatible. This collaboration can help resolve the issue.
If this solution does not apply to your case, or if it 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. If the problem persists, we highly recommend opening a new support ticket for further assistance.
Problem: The client reported that while duplicating booking objects (Custom Post Type) on their multilingual website, the tours page displayed correctly in French and English, but no content was shown in Italian and German. Solution: We discovered that the issue was related to the settings of the BABE plugin not being consistent across different languages. To resolve this, we advised the client to: 1. Navigate to BA Settings > General tab. 2. Switch to the Italian language. 3. Set the option
Return search results without checking availability if no dates are specified
from 'No' to 'Yes'. 4. Save the changes. This adjustment ensures that the plugin's behavior aligns across all languages, as it supports saving options per language.
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. Additionally, please feel free to open a new support ticket for further assistance at WPML support forum.
Problem: The client is unable to translate a contact form created with the Metform plugin and Elementor widgets on their multilingual site. Solution: A. Translate the form content: 1. Navigate to WPML > Settings > Post Types Translation and set the post type "metform-form" to Translatable. 2. Go to WPML > Settings > Custom XML Configuration and add the following code to translate the form fields:
3. Visit Metform > Forms and translate the form titled "New Form # 1693676945". B. Translate the widget form on the contact page: 1. Follow step 2 above to add a custom XML code to translate the form ID:
2. Switch to the English language in Metform to retrieve the form ID from the URL, which is 2710. 3. Add the following PHP code to the file functions.php in the theme folder to make the number translatable in the Advanced Translation Editor:
4. Update the contact page and its translation. 5. In the Advanced Translation Editor, search for the form ID and translate it. Now, the form should appear translated on the frontend. Refer to the documentation for further details:
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, 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. For further assistance, please visit our support forum at WPML support forum.
Problem:
Unable to review translation of custom post type posts.
Solution:
We enabled error reporting and the theme was generating fatal error on reviewing Gallery post type posts. The client don't want to translate the Gallery post type posts, so he set them to not translatable.
Problem: The client needed assistance with two issues: translating the filter labels 'All', 'Room', and 'Rooms' on the homepage and archive pages, and changing the Cyrillic translations to Latin for the Serbian language on the Cart and Checkout pages in WooCommerce.
Solution: 1) To translate 'All', 'Room', and 'Rooms': - Go to WPML > String Translation. - For 'All', type 'All' in the search box, select "Exact match", and click the "Search" button. Translate the string found under the "augustine-core" domain by clicking the "+" icon under the language flags. - For 'Room' and 'Rooms', type '%s Room' in the search box and press the "Search" button. Translate the strings under the 'augustine-core' text domain using the same method.
2) To translate WooCommerce strings on the Cart and Checkout pages to Latin for the Serbian language: - Go to WPML > Theme and Plugins Localization. - Select the "WooCommerce" plugin and scan it for strings. - Once the scan is complete, navigate to WPML > String Translation. - Input the text you wish to translate in the search box, using English as the source language. For example, type "Product" instead of "Производ". - If the string is under the 'woocommerce' text domain, add a translation for the Serbian language by clicking on the "+" icon below the Serbian flag.
Please note that the solution provided might be outdated or not applicable to your case. If the steps above do not resolve your issue, we highly 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 you still need assistance, please open a new support ticket.
Problem: The client has translated ACF fields for a custom post type 'accommodaties' but the translations are not showing on the English version of the site.
Solution: We recommend the following steps to resolve the issue: 1. Open the
, around line 142, replace the code snippet with the provided workaround that includes WPML filters for registering and translating strings. 3. Open the
, around line 339, replace the code snippet with the provided workaround similar to step 2. 5. Visit the page with the facets in the original language to register the strings. 6. Go to WPML > String Translation and translate the strings.
Before making these changes, ensure to back up your database. Additionally, if the default language on the website is Dutch and the strings are registered in English, the language of the string may need to be changed to Dutch before translating. For guidance on changing the source language of strings, refer to the documentation.
Please note that this solution might be outdated or not applicable to your case. If the issue persists, 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, do not hesitate to open a new support ticket for further assistance.
Problem: If you're experiencing an issue where the overlay menu for the second language is not visible on the mobile version of your site, while it works correctly for the primary language, the problem may be related to the theme you are using.
Solution: First, ensure that your theme is compatible with WPML. You can check the theme's certification status on the WPML's list of compatible themes.
If the theme is not certified, you might encounter issues with multilingual functionality. In the theme file
, the theme author uses a custom function to display the navigation menu. We recommend replacing this custom function with the standard WordPress function
wp_nav_menu()
to ensure compatibility with WPML. Here is an example of how you can adjust the code:
Please note that custom code assistance is beyond the scope of WPML support. If you need help with custom code, consider contacting one of our certified partners.
Keep in mind that the theme's last update was in 2017, which is quite outdated. We recommend using a theme from the list of compatible themes to ensure proper content translation on your site.
If the solution provided here is not relevant to your case, either because it's outdated or not applicable, we highly recommend checking related known issues on the WPML Known Issues page, 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.
Problem: The client reported that URLs set in any anchor tag were being manipulated by WPML, as evidenced by different values in a hidden input field and an anchor tag. Solution: We recommended the client to set the pages to "Translatable - only show translated items" in WPML > Settings > Post Type translation to see if this resolves the issue.
Please note that this solution might be outdated or not applicable to your case. If the issue persists, we encourage you to open a new support ticket. We also highly 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 further assistance is needed, please contact us through the WPML support forum.
Problem: The client was experiencing an issue where the subscribe form worked in Bulgarian but not in English. In the English version, the successful subscription message did not appear, and a 500 error was present in the console on the feedback file. Solution: We recommended the client to first create a backup of their site and database. Then, we suggested deactivating the "Bravis Addons" plugin and switching to a different WordPress theme to see if the problem persists. If the subscribe form worked after these steps, we advised reactivating the plugin and switching back to the original theme to check if the form continued to work. If the issue remained, we suggested deactivating the plugin again, switching to a standard WordPress theme, adding the subscribe form shortcode to a new page, and translating that page.
Please note that this solution might not be relevant to your case, as it could be outdated or not applicable to your specific situation. If you're experiencing a similar issue and the provided solution does not help, we highly recommend checking 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 with us.
