Problem: The client is receiving a 'Your WPML account has expired' notification in WordPress after moving their site to a new domain and updating the URL in the WPML system. The client is not a developer and cannot access the 'Add plugin' option in WordPress due to the site being GIT based. Solution: We recommend trying to register the domain using a slightly modified URL. Specifically, instead of registering 'https://konopljazdravi.si', try registering 'https://konopljazdravi.si/wp'. This might resolve the issue with the WPML account expiration notification.
If this solution does not apply to your situation, 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 the problem persists, please open a new support ticket.
Problem: The client is trying to translate the WP Cookie Consent plugin using WPML but is unsure how to proceed. Solution: We recommend using the WPML String Translation to translate all strings of the WP Cookie Consent plugin. If some strings are missing, you should register them to appear in the translation table. You can do this by following the steps outlined in Finding Strings That Don’t Appear on the String Translation Page. It is advisable to use the "Admin Strings" option. Once activated, open the Frontend, and WPML will attempt to automatically register all visible strings.
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 issues persist, please open a new support ticket.
Problem: The client reported that Rankmath is not displaying some translated
/hr/
pages in the sitemap, despite having created a caching exception in W3C.
Solution: First, we checked if there was a
noindex
directive or a
robots.txt
file blocking the pages, which there wasn't. We also verified that hreflang tags were correctly implemented using TechnicalSEO's hreflang tool.
Next, we suggested manually submitting the URLs to search engines using Rankmath's IndexNow feature, as detailed in their documentation: How to use IndexNow.
If these steps did not resolve the issue, we offered to debug the website further, for which we would need a Duplicator package of the site as per the instructions here: Providing supporters with a copy of your site.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your specific case. If the issue persists, 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 necessary, do not hesitate to open a new support ticket with us.
Problem: The client needed to know the procedure for retranslating a post that was originally translated with the Classic WPML editor but then modified in the WordPress Editor. Solution: 1. If the client wants to start from scratch, they should: - Go to Pages. - Switch the language at the top to the language of the translation. - Find the page with the translation and delete it. - Also, delete it from the "Trash" area.
2. If the client just wants to edit the text in the current translated version: - They can directly edit the translation in the WordPress Editor.
We recommend not switching between the classic editor and the WordPress editor as it may cause issues. It is better to consistently use one editor.
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.
Problem: The client needed clarification on what a specific option in the WPML interface means, particularly regarding the translation of media attachments. Solution: We explained that the option in question allows the client to select media attachments for translation within a post. When selected, the translator can translate any associated text with the media through the translation editor. Additionally, we advised that if the client wishes to use different media files for each language, it is necessary to translate the media in WPML -> Media Translation. We provided a step-by-step guide on how to do this with a link to our documentation:
If this solution does not seem relevant, we encourage the client to open a new support ticket for further assistance. For additional support, please visit our WPML support forum.
Problem: The client experienced issues with translations after manually editing articles in Gutenberg and using the WPML editor. Some content was overridden with the original language content, and some paragraphs were not translated when viewed on the front end.
Solution: 1. If you're experiencing similar issues, it's important to note that you cannot mix translation methods. You need to choose either manual translation or the WPML editor. 2. To resolve the issue, you can disable the WPML editor for the affected page. After disabling, re-save the translated page manually in the WordPress editor. 3. Alternatively, you can re-translate the content using the WPML editor and continue using this method for future translations. 4. If you're planning to change your WordPress theme, be aware that it shouldn't impact existing content and translations. However, new design elements introduced by the theme may require additional translations.
If this solution doesn't seem relevant to your situation, please open a new support ticket with us, and we'll be happy to assist you further.
