Problem: The client reported that all British English pages, which are duplicates of the default English pages, were missing from the WordPress page list, although the page count indicated they existed. The client had already tried clearing the WPML cache without success. Solution: 1. We first suggested updating outdated plugins, specifically Advanced Custom Fields Multilingual and Gravity Forms Multilingual, which did not resolve the issue. 2. We then advised refreshing the permalinks by navigating to Settings → Permalinks and clicking the Save Changes button, which also did not bring back the missing pages. 3. We checked the WPML settings under WPML → Languages to ensure that British English was not set to be hidden. It was confirmed that British English was not hidden. 4. After further investigation, we discovered that the issue was caused by the 'HappyFiles Pro' plugin. Once we deactivated this plugin, the British English content appeared correctly.
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. If the problem persists, please open a new support ticket.
Problem: You are trying to activate the WPML plugin on your subdomain but encountering errors such as 'Your account allows you to build only 3 "production" sites with WPML,' and 'Unable to register: Site key not matching' when using the parent website key. Solution: If you are using a Multisite Setup, you should first register your main site so that the same site key will apply to all subsites. For detailed instructions on how to register WPML on a Multisite Setup, please visit https://wpml.org/documentation/support/multisite-support/#install-wpml-multisite. If your subdomains are separate WordPress installations and not part of a Multisite setup, you will need to register each one individually and create a separate site key for each URL.
Please note that this solution might be irrelevant if it's 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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client is experiencing two main issues: 1. Language mismatch in redirection and auto-responder, which remains unresolved and was mistakenly closed in a previous ticket. 2. Layout and hover effects issues on the translated blog page using WPML with Bricks Builder, which is currently unassigned.
Solution: For the first issue regarding language mismatch: - We recommend revisiting the previous tickets and ensuring all related templates are fully translated. If the problem persists, consider setting up a new staging site that mirrors the current production site exactly, or connect your staging site with your production site to share the same translation memory. You can find more information here: Automatic Translation Subscription for Multiple Sites.
For the second issue related to PHP memory limit: - We suggest contacting your hosting provider to increase the PHP memory limit to at least 256M to ensure smoother operation of your site.
If these solutions do not resolve your issues or if they seem 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 problems persist, please do not hesitate to open a new support ticket with us for further assistance at WPML Support Forum.
Problem: The client is experiencing an issue where wpseo_titles are being overwritten in the secondary language when using WPML with the Yoast SEO plugin. This occurs after changes are made in the Yoast settings and the frontend is visited in a secondary language. Solution: 1. Verify if the wpseo_titles custom field is set to be translatable by following the steps in this guide: Translating Custom Fields. 2. If the field is translatable, check for any triggers in the default language that might be overwriting the translation. 3. You can also try translating the wpseo_title value via String Translation. This might require locating it first within the admin texts section as described here: Finding Strings that Don't Appear on the String Translation Page. 4. If translating the value does not resolve the issue, it is likely a compatibility issue between WPML and Yoast SEO, not directly caused by WPML.
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 problem persists, please open a new support ticket.
Problem: The client is experiencing issues with manually linking pre-translated Elementor pages using the WordPress editor. Instead of allowing manual linking, clicking the '+' icon redirects to WPML's Advanced Translation Editor. Additionally, there are problems with language mapping for manually added languages and visibility of translated content in the backend. Solution: To manually translate and link Elementor pages using the WordPress editor, follow these steps: 1. Ensure that the option to use the WordPress Editor or Elementor for translations is correctly set up. You can find detailed instructions on setting this up here: Using Different Translation Editors for Different Pages. 2. When clicking the '+' sign to add a translation, if the page appears blank, copy the content from the original page and proceed with the translation. 3. If issues persist, such as the '+' icon still redirecting to the Advanced Translation Editor or problems with language mapping and visibility, it may be necessary to escalate the issue to our technical team.
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 problem persists, please open a new support ticket at WPML support forum.
Problem: The client was unable to translate a button labeled 'Rezervuoti' and change its link for the English version. Additionally, the client needed assistance with translating the footer into English. Solution: For the button issue, we duplicated the header element and named it 'Header Main'. We then manually translated it using the manual translation method provided by WPML. You can find detailed instructions on manual translation here: https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/. This resolved the issue with the button text and link in the English version.
For the footer, we duplicated it using the 'Overwrite with Lithuanian content' option to create an English version. We then set it to 'Translate independently' allowing both versions to be edited separately. This setup is a one-time process and has been completed. Changes to the footer must be done manually in Elementor for each language, as the theme does not support the Advanced Translation Editor for header/footer templates.
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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is experiencing inconsistent page loading, sometimes resulting in a 500 error or a redirect loop on their multilingual site using WPML. This issue occurs after updating the Learndash plugin, but persists even after deactivating other plugins like Memberium, suggesting a problem with WPML’s language routing or translation handling. Solution: We recommend reviewing the WPML configuration for the affected page, particularly its translation status, language assignment, and URL structure. Additionally, try the following workaround: https://wpml.org/faq/why-is-htaccess-getting-overwritten-with-the-language-folder-on-my-wpml-website/
If this solution does not resolve the 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 the problem persists, please open a new support ticket with us for further assistance.
Problem: Se stai riscontrando problemi con la rigenerazione automatica del file .htaccess che modifica le regole standard di WordPress, causando malfunzionamenti del sito quando WPML è attivo e utilizza la modalità 'Lingue diverse nelle directory', potresti notare che il file .htaccess viene modificato inserendo '/en/' come RewriteBase. Solution: Ti consigliamo di consultare la nostra FAQ specifica per questo problema, che potrebbe aiutarti a risolvere la situazione. Puoi trovare la guida dettagliata qui: https://wpml.org/faq/why-is-htaccess-getting-overwritten-with-the-language-folder-on-my-wpml-website/. Inoltre, se il problema persiste, ti suggeriamo di salvare nuovamente i permalink nelle Impostazioni > Permalink, poiché questo può rigenerare correttamente il file .htaccess e ripristinare il funzionamento del sito.
Se la soluzione proposta non dovesse essere più rilevante o non risolvere il tuo caso specifico, ti invitiamo a consultare la pagina dei problemi noti https://wpml.org/known-issues/, verificare la versione della correzione permanente e confermare che hai installato le ultime versioni di temi e plugin. Se necessario, apri un nuovo ticket di supporto per assistenza ulteriore qui.
Problem: The client is unable to edit exhibition dates in the Arabic version of their website, despite being able to do so in the English version. The date fields are not visible or accessible in the Arabic version. Solution: We recommend checking the translation settings for the custom fields related to the exhibition dates. Here are the steps to follow: 1. Navigate to WPML → Settings in your WordPress dashboard. 2. Scroll to the Custom Fields Translation section. 3. Locate the fields 'exhibits_start_date' and 'exhibits_end_date'. 4. Set the translation preference for these fields to Translate. 5. Click Save to apply the changes. After making these changes, please check if the date editing fields are now visible and editable in the Arabic version of the exhibition post.
If this solution does not resolve the 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 the problem persists, please do not hesitate to open a new support ticket for personalized assistance at WPML support forum.
Problem: Die Seiten existieren, aber WPML erkennt sie als englischsprachig, obwohl sie dupliziert wurden, um auf Deutsch angezeigt zu werden. Eine Übersetzung von Deutsch nach Englisch ist nicht möglich, da eine Fehlermeldung angezeigt wird: "Some of the selected content has already been translated from English to German and cannot be re-translated from German to English." Solution: Wir empfehlen, die Ausgangssprache der Inhalte im WordPress-Editor anzupassen. Dies kann in der rechten Seitenleiste des Editors erfolgen. Anleitung: https://wpml.org/faq/how-to-link-already-translated-pages/
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 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.
