Problem: You are working on a site under development and encountered a problem with duplicate ACF fields from different language fields. After setting all field groups to 'Same fields across languages' and removing duplicates, the data in the fields was saved for all languages in the admin. However, on the site, two out of three languages display correctly, but the third shows an error: 'Uncaught Error: Illegal offset type in isset or empty'. Solution: We recommend checking a similar support ticket that might help resolve the issue you are facing: https://wpml.org/forums/topic/fatal-error-uncaught-typeerror-illegal-offset-type-in-isset-or-empty-in-var-w/ Before making any changes, please back up your database first. Additionally, verify if the ACF options were translated in other languages using the format "%options_(language_code)_resources%", where (language_code) is replaced with the actual language code.
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 the issue persists, please open a new support ticket at WPML support forum.
Problem: You are developing a multilingual site using custom posts with custom taxonomy (CPT UI) and specific fields for taxonomy archive pages (ACF). The issue occurs on the taxonomy term 'Engines -> Hybrid', where data is not displayed on the archive page. Despite recreating it and clearing the WPML cache, the problem persists. The 'Hybrid' term does not show the contents of the custom fields on the archive page, except in German where only the background image is displayed. Disabling WPML, the 'Hybrid' terms are displayed correctly. Solution: The issue is with the UpSolution Core plugin from Impreza. We will contact the author since it is a compatible theme. The definitive solution must come from them because it is a problem with their code logic. A temporary solution is to comment out line 264 of the file
. We have done this on the staging site, and as you can see, it now works. If there are updates to UpSolution Core before this issue is fixed, you will need to repeat the modification.
Please note that 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: When the client selects Spanish on their website, and then navigates to another page, they need to select Spanish again because the language does not persist across different pages. Solution: We recommend ensuring that the language switcher is properly configured to maintain the language selection across different pages. This might involve checking the settings for language persistence in WPML. Additionally, if the issue is specifically related to the menu not being translated, we suggest following our guide on translating WordPress menus with WPML. You can find the guide here: Translating WordPress Menus with WPML.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, please do not hesitate to open 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, you can contact us directly through our support forum.
Problem: The client is trying to translate the text of the Divi Image Hover plugin using WPML but is concerned about entering code in the Custom XML Configuration and potentially breaking their site. They are using a basic child theme and cannot use the Multilingual Tools plugin. The main issue is that the Spanish professions displayed on the images are not translatable into English. Solution: We recommend following the steps provided by our colleague in a previous support ticket, which involves adding specific XML code to the WPML → Settings → Custom XML Configuration. You can find the necessary instructions and XML code here: https://wpml.org/forums/topic/the-divi-image-hover-text-is-not-acknowledged-by-your-plugin/#post-13394257. Before implementing this on your live site, please try it on a staging site and ensure you have a backup. Additionally, make a minor edit to the page where the Image Hover element is used and update it to trigger the translation process in WPML's Translation Editor. Another critical step is to ensure that the WordPress REST API is enabled on your site, as it is necessary for loading strings. You can verify this in WPML → Support. If it's disabled, please contact your hosting provider or developer to enable it. More information on this can be found here: https://wpml.org/documentation/support/rest-api-dependencies/.
If this solution does not resolve your 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: Sie arbeiten an einer Website in Entwicklung und versuchen, ein WS Form Formular, das in einem Bricks Template eingefügt wurde, zu übersetzen. Die Übersetzung funktioniert nicht, einschließlich Placeholder Text, Checkbox Text und Button. Solution: Wir haben festgestellt, dass alle Strings des Formulars korrekt übersetzt wurden, einschließlich der richtigen Textdomains. Das Problem besteht weiterhin, auch nachdem das WP_MEMORY_LIMIT auf 256 MB erhöht wurde. Wir empfehlen, die Unterstützung der WS Forms-Autoren zu suchen und sie einzuladen, sich für eine WPML-Zertifizierung zu bewerben: https://wpml.org/documentation/support/go-global-program/. Alternativ können Sie ein zweites Formular anlegen und es direkt in Bricks einer bestimmten Sprache zuweisen. Eine weitere Möglichkeit ist die Nutzung einer der bereits für WPML zertifizierten Formularlösungen. Eine Übersicht dazu finden Sie hier: WPML-Plugin-Funktionalität – Formulare.
Falls diese Lösung veraltet ist oder nicht auf Ihr Problem 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.
If you're experiencing an issue where the Elementor loop is missing on your multilingual site, particularly when comparing different language versions, we have identified a solution.
Solution:
1) Ensure that the translation for the 'Bestseller Loop Home new' template is published in all secondary languages. It might currently be in 'pending for review' mode. 2) Add the following code to the
3) Save the changes. 4) Update the page and its translations.
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 the issue persists, please open a new support ticket.
Problem: The client is attempting to translate the text 'Submit Listing' and 'Sign in' on their website header using WPML. Despite following the relevant documentation, the 'Submit Listing' button text does not change when switching the website language from English to Albanian. Solution: 1. Verify that the Template used in the Header is set as translatable in WPML. This can be done by navigating to WPML > Settings > Post Type Translation. 2. Once the Template is set as translatable, use the WPML Translation Editor to apply the translations. 3. Additionally, translate any relevant Listing Conditions through WPML > Taxonomy Translation.
If this solution does not resolve your issue, or if it seems outdated or not applicable 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: Sie möchten die Fahnen in der Top Bar dauerhaft ausblenden. Nach dem Hinzufügen von Fahnen in der Menüliste sind diese in der Top Bar wieder aufgetaucht und lassen sich nicht mehr entfernen. Solution: Die bisherigen Lösungen, einschließlich manueller Anpassungen per PHP oder CSS, die im Chrome Inspector funktionieren, werden auf Ihrer Installation nicht übernommen. Dies könnte an einem aktiven Caching liegen. Wenn diese Ansätze nicht funktionieren, empfehlen wir, sich direkt an den Enfold-Support zu wenden.
Falls diese Lösung aufgrund von Aktualisierungen oder spezifischen Umständen Ihrer Installation irrelevant sein sollte, empfehlen wir, ein neues Support-Ticket zu erö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.
