Problem: The client needed to change not only the text on the front end but also the URL.
Solution: First, we recommended that the client update their WPML plugin to the latest version, which at the time was 4.6.9, along with any add-ons, to ensure they have all the latest bug fixes and improvements. We provided a link to the update instructions: http://wpml.org/faq/install-wpml/ and reminded them to back up their database before proceeding.
If this solution does not apply to your case, or if it seems outdated, we highly recommend checking the 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 do not hesitate to open a new support ticket: https://wpml.org/forums/forum/english-support/.
Problem: The client was unable to update WPML and restored the site to a previous version. They also inquired about running WPML on a staging site. Solution: We recommended the client to register the site with a new WPML site key after taking a full site backup. The steps include: - Deleting the old key from the account page - Unregistering WPML from the site through the Plugins>Add New>Commercial tab - Generating a new key and registering the site with it - Upgrading to the latest version of WPML For detailed instructions, we provided documentation links:
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 you need further assistance, please open a new support ticket.
Problem: The client needed to update the header with custom mobile numbers for each language.
Solution: We provided a step-by-step guide to find and translate the strings for the header: 1. Navigate to WPML-> Theme and plugins localization, select the theme/plugin, and scan. 2. Go to WPML-> String Translation. 3. Click on the "Translate texts in admin screens »" link. 4. Search for the needed strings. 5. Select the strings. 6. Click on the "Add to String Translation" button. 7. Click on the "« Return to String Translation" link. 8. Translate the strings, clear the cache, and check the front end.
Problem: The client received an automated email from WordPress indicating a fatal error caused by the WPML Multilingual CMS plugin. The error message specified an issue with the file
1
class-wpml-tm-icl-translations.php
and mentioned 'No translation entry found for query'. Solution: If you're experiencing a similar issue, we recommend searching for existing tickets that address this error. You can use this custom search URL to find relevant solutions: Google Search for WPML Support Forum. Additionally, you may find a solution in this specific ticket: WPML Support Forum Ticket. Following these steps should help you resolve the issue more quickly. If this solution doesn't seem relevant to your situation, please open a new support ticket in our support forum.
We use cookies to optimize our website and services. Your consent allows us to process data such as browsing behavior. Not consenting may affect some features.
Functional
Always active
Required for our website to operate and communicate correctly.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
We use these to analyze the statistics of our site. Collected information is completely anonymous.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
These cookies track your browsing to provide ads relevant to you.
