Problem: The client has created an ACF Options page with a field group intended for use across all language versions without translation. However, the
get_field()
function returns null for all languages except the default one, even after setting the field to 'Don't translate' and disabling the ACFML plugin. Solution: We have acknowledged this issue and escalated it to our second-tier team for further investigation and resolution. The feature request concerning non-translatable ACF Options pages is under review, and the client's ticket has been linked for tracking purposes. We will update the client as soon as there is any progress.
If this solution becomes outdated or does not apply 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: The client reported that the WPML plugin is loading JavaScript and CSS files externally, which they believed to be against WordPress plugin guidelines and raised concerns regarding privacy policy compliance and potential security risks. Solution: We explained that the WordPress Plugin Guidelines cited do not apply to WPML as it is not hosted on the official WordPress.org directory. The external scripts are served from our own domain and are part of WPML's service infrastructure, ensuring they comply with our privacy policy and do not conflict with data protection laws like GDPR. Regarding security, while acknowledging the theoretical risk if our servers were compromised, we maintain that the assets are securely served via HTTPS from our controlled infrastructure, balancing flexibility and security effectively. We decided not to bundle JS/CSS with the plugin at this time.
If this solution does not resolve your issue or seems outdated, we 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 feel free to open a new support ticket at our support forum.
Problem: When using Gutenberg to create a page and translating it with the Advanced Translation Editor (ATE), if you later edit the heading in the original language, the corresponding translated field in ATE becomes empty. Solution: Currently, this behavior is expected and there is no direct way to retain the old translations in ATE after changes are made in the original language. However, we have already submitted a feature request to our development team. Your ticket has been added as an additional vote for this request, which will be considered in future updates.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also advise checking the related known issues and confirming that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum.
Problem: Sie möchten WPML löschen und die Datenbank von allen Übersetzungen sowie Einträgen bereinigen. Die Standardanleitung entfernt nur Sprachen und String-Übersetzungen, aber Seitenübersetzungen und Produktdaten bleiben in der Datenbank. Solution: 1. Löschen der aufgeführten Tabellen/Metafelder Das Löschen der spezifizierten Tabellen und Metafelder entfernt alle WPML/WCML-Übersetzungsdaten zu Produkten und Medien. Felder, die auf Währungscodes wie '_TRY' enden, hängen von den im Shop aktivierten Währungen ab. 2. Abbruch beim Sprachlöschen Ein bekanntes Problem führte zum vorzeitigen Abbruch des Löschvorgangs unter *WPML → Sprachen → Sprache löschen*. Dieses Problem wurde in WPML 4.7.2 behoben. Weitere Informationen 3. Medienbehandlung WPML Media Translation erstellt keine physischen Bildduplikate, sondern arbeitet mit Metadaten. Die aktuelle Logik wurde verbessert, um Medien je nach Einstellung intelligent zu handhaben. 4. WPML-Reset Ein WPML-Reset wird empfohlen, um alle WPML-Daten einschließlich Einstellungen in 'wp_options' und eventuell verbleibender Tabellen mit Präfix 'icl_' vollständig zu entfernen.
Falls diese Lösung veraltet erscheint oder nicht auf Ihr Problem zutrifft, empfehlen wir, einen neuen Support-Ticket zu öffnen und die aktuellen bekannten Probleme unter https://wpml.org/known-issues/ zu überprüfen. Stellen Sie sicher, dass Sie die neuesten Versionen Ihrer Themes und Plugins installiert haben.
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 for further assistance.
Problem: The client needed to know how to find the word count for their site using WPML and also inquired about editing translations globally after using AI translation, specifically for handling incorrectly translated terms. Solution: We advised the client that when they are on the Translation Dashboard and select a page, they can see at the bottom the number of words that need to be translated, how many credits are used, and the exact price. Unfortunately, an estimate for the entire website is not currently available, but the client can check the estimated cost for each selected page or post.
For editing translations globally, we recommended that from WPML > Settings, the client can choose to review the translation or set specific terms and their translations in the Glossary, which will then be used in automatic translations. More details on managing glossary entries can be found here: How to Create and Manage Glossary Entries.
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: You are experiencing inefficiencies in uploading images with localized filenames for SEO purposes using WPML Media Translation. You've noticed there is no automatic process for translating filenames, which makes the process time-consuming. Solution: We have considered the possibility of implementing automatic filename translation. However, after internal discussions, we decided not to pursue this feature at the moment. The main reasons are the lack of sufficient demand from our users and the potential increase in database usage due to file duplication. WPML is designed to focus on translating user-generated content like alt texts and captions while using the same media file across different translations.
If this solution does not resolve your issue or seems outdated, we recommend checking the related known issues and verifying that you have the latest versions of themes and plugins installed. If the problem persists, please open a new support ticket.
Problem: The client needed to customize the default translation batch name in WPML Translation Management, which is hardcoded as 'WPML|{lang}|{number}'. They requested a filter to change the prefix 'WPML' to a custom string like 'Help Center'. Solution: We reviewed the request and decided not to add a new filter for customizing the default translation batch name. This decision was based on the specificity of the request and the fact that it's the first of its kind in over 10 years of WPML development. Additionally, since the batch name can be manually edited before sending for translation and it does not impact the translation workflow, we concluded that the demand for this feature does not justify a new implementation at this time. However, you are welcome to implement a custom solution if necessary.
If this solution does not apply to your case, or if it seems outdated, 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. Should you need further assistance, please open a new support ticket.
