Home›Support›English Support›[Resolved] wpml not working on live website but working correctly on staging
[Resolved] wpml not working on live website but working correctly on staging
This thread is resolved. Here is a description of the problem and solution.
Problem:
The client is experiencing issues with WPML not displaying translated content correctly on the live website, despite working on the staging site. The problem affects multiple Vehica elements, such as testimonials and titles, which are not visible in the WPML translation editor or found in the String Translation section.
Solution:
We identified that the issue was related to the Elementor plugin, and it occurred because the client had deleted the WPML packages. Here are the steps we recommend to resolve the issue:
1) Navigate to the */wp-content/plugins/vehica-core/app/Managers* folder. 2) Open the *PageManager.php* file for editing. 3) Change the code at line 31
4) Open the Homepage for editing in the original language. 5) Make a minor edit to the contents and save changes to refresh the translation settings. 6) Update the translations from WPML Advanced Translation Editor.
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.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Background of the issue:
I am trying to ensure that WPML works correctly on both my live and staging websites. The settings are the same in both environments. The issue can be seen on the live website at hidden link, and I expected it to work like it does on the staging site at hidden link.
Symptoms:
WPML is not working on the live website, but it is working correctly on the staging site.
Questions:
Why is WPML not working on the live website despite having the same settings as the staging site?
What steps can I take to resolve the issue on the live site?
Thank you for the updates. I am enabling the private option for the next reply. Please share the new staging site credentials so we can continue with our checks.
- i have only cloned the site public_html folder
- copied the database
- added ssl certificate using zero ssl
- replaced siteurl and home in wp_options table
- installed "better search plugin" (not executed the replace of staging2 with
staging...afraid to break elementor serialization)
We are still working on this. The translations have been completed in the WPML Advanced Translation Editor server and delivered back to the site as expected.
So we have a request. Please create a copy of the site using the Duplicator plugin and install the Duplicator copy in the space of hidden link. Then, please check if the issue still exists.
This will help us track the problem more effectively, as it might be related to the manual migration steps previously followed.
- i have only cloned the site public_html folder
- copied the database
- added ssl certificate using zero ssl
- replaced siteurl and home in wp_options table
Please try it and let us know your feedback. Thank you for your kind understanding.
I’ve now copied the staging site using the Duplicator plugin. After several attempts, I successfully completed the process and deployed the copy to the staging environment.
During this process, I discovered a key issue that explains why the live site wasn’t behaving correctly: there was an extra .htaccess file located in public_html/wp-content. This conflict was preventing translations from displaying properly on the live site, while the staging copy (staging2) was working as expected.
Please leave the chat open for now, as I’d like to monitor things a bit further and return here in case anything else comes up.
After reviewing the website, the issue with the WPML translation editor not displaying translated content still persists on more pages. For example:
hidden link
hidden link
Although the content has been translated, it does not appear on the frontend.
The problem seems to affect multiple Vehica elements—for example, the testimonials (reviews) on the homepage and most Vehica titles are neither visible in the WPML translation editor nor found in the String Translation section.
The good news is that Automobile Facilities (the list of features on single product pages) are now displaying correctly and can be translated via Taxonomy Translation in WPML. Additionally, I’ve implemented a JavaScript function on the live site to force missing translations to appear where possible.
Here’s what I’ve done so far:
Rechecked the WPML settings, ensuring the relevant custom fields are set for translation.
Downloaded the Vehica files through WPML > Theme and Plugin Localization to register all translatable strings.
Searched for missing strings in the String Translation interface.
Despite these efforts, key Vehica page elements still aren’t available for translation.
Could you please assist in identifying a solution?
Thank you for the updates. The WPML >> Support >> Advanced Translation Editor >> Error Logs are showing the following errors.
AMS Server Communication
Api error missing resource: No sitekey found for this website
Therefore, please try the following steps after taking a full site backup and see if there is any difference in the result:
1) Visit your account page at https://wpml.org/account/sites/
2) Delete the existing key for your site. (hidden link)
3) Navigate to Plugins >> Add New >> Commercial tab of hidden link.
4) Click on "Unregister WPML from this site".
5) Refresh the page.
6) Click on "Get a key for this site".
7) Copy the newly generated code.
8) Return to Plugins >> Add New >> Commercial tab.
9) Register the site with the new key.
10) Open this post for editing - hidden link
11) Make a small change (like adding a space or punctuation) and update the post. This will help refresh the translation settings.
12) Then update the translation and check if you are now getting the expected results.
I’ve added the new site key by following above steps and in commercial tab the green checkmark and the message “WPML is registered on this site” is visible. However, the translated content is still not visible on the frontend — it only appears inside the ATE.
Also, I have scanned vehica theme and now I have multiple unwanted strings in ATE. I have removed them from string translation, but are still visible in ATE. How to remove them?
New threads created by Bigul and linked to this one are listed below:
More than this - I have switched from <Translatable only show translated items> to <use translation if available or fallback to default language> and back; now even the few elements that had visible translation are not working anymore
New threads created by Bigul and linked to this one are listed below:
Thank you for the updates. We will check this further and get back to you soon.
Also, please note that I have created a new ticket for the issues related to multiple unwanted strings in ATE and translations not working for some elements. This will make it easier to follow up and ensure we handle each issue more efficiently.
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.
