Skip Navigation

This thread is resolved. Here is a description of the problem and solution.

Problem:
The client is experiencing issues with visitors being directed to sub-directory URLs instead of the correct domain URLs after changing the WPML-Language setting for different domains. Additionally, there are problems with a distorted home page and missing background images when switching to French.
Solution:
After migrating from staging to production please run the WPML troubleshooting options available at WPML > Support > Troubleshooting (Cleanup) > Clear the cache in WPML. This action can help resolve issues inside the Advanced Translation Editor.

If this solution does not resolve issues or seems irrelevant due to being 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. Should you need further assistance, please do not hesitate to open a new support ticket at our support forum.

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.

This topic contains 0 replies, has 3 voices.

Last updated by Alejandro 1 month, 1 week ago.

Assisted by: Alejandro.

Author Posts
October 29, 2024 at 3:11 am #16340060

ronaldT-5

I'm also noticing that once I reset a page in live production site, that not only do I lose a lots translations, but that multiple sentences are being automatically translated at once instead of one sentence at a time.

Otherwise, it fixes the issue with using a separate domain for the translated pages.

I am starting to realize that I made a huge mistake by migrating from Polylang to WPML. I bet I wouldn't have any of these problems with Polylang.

October 29, 2024 at 5:17 am #16340125

ronaldT-5

BTW, 95% of my customers speak French. Would it be possible to change the main domain for alarme-maison.ca and use that one with subdirectories, such as /en/ for English and /fr/ for French content? Wouldn't that solve my issues? Instead of using different domains.

October 29, 2024 at 1:30 pm #16342540

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

My apologize, I did not mean to ignore a topic, but please take note that we can only handle one issue per ticket, to be able to assist you effectively.

Once you change the site URL format for the website you need to go to the WordPress Permalink settings and click "Save".

This usually should adjust the permalinks for all your contents. In cases where you hard-coded links into the content, then you might need to adjust them manually.

THis means, you update the original content, then complete the translation with the WPML Translation Editor.

So far, I can not follow how it came to a huge credit loss. I am not aware about any MEMCACHED issues at the moment, but I would like to ask you to set up a test site on your server on which we can run tests to see if we can recreate this problem.

We further provide the following documentation for this topic:
https://wpml.org/documentation/support/using-wpml-with-memcached-caching/

October 29, 2024 at 2:11 pm #16342743

ronaldT-5

Not sure what you mean by hard-coded, but none of my links on the site are switching to separate domains. The only way I have found is to reset all 39 English pages and to retranslate everything as I lost most of my manual translations.

I could manually copy the ATE translations from staging to live (even though it would be a lot of work, but it is better than having to start from scratch). But, my biggest hurdle is that the live site ATE often shows up with multiple sentences (a whole paragraph) on a single row. Why is that? Or, HOW TO PREVENT THIS???

And yes, I did save the permalinks as instructed following the language URL setting.

The credit loss is mainly due to the memcached issue. I kept having to retranslate on the staging until I finally discovered in the end that disabling it prevented that.

You could use staging22 as a test bed. Same credentials. But, currently memcached is disabled on the server. Once I'm done with the current nightmare and able to get the French links to work again, then I will re-enable the memcached on the server.

October 29, 2024 at 2:22 pm #16342826

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

The following websites should use the same translation memory:

hidden link
hidden link
hidden link

Total count in memory: 12517

This means, no identicals segments that you have translated already will get charged credits for translation. Surely, you would need to complete the translations first again, if a new site has not translations yet, but at this moment ATE will pull the info from translation memory and you will not get charged for this.

In case you suspect that the translaiton memory does not work as expected due to MEMCACHED, then please provide me access and details to a content on the site on which I can see the issue.

October 29, 2024 at 2:49 pm #16343076

ronaldT-5

Okay, I have a live site that the French links do not work (has not been working for weeks). How about you help me with that first. I keep avoiding my dire questions. The new site is FULLY SEOed, and having the French side not working is going to kill my reputation on Google. You do not seem to care about it, do you?

October 29, 2024 at 5:17 pm #16343741

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

It seems the confusion here is that we are talking about different issues.

Please take note that we can handle only one issue per ticket. Here was reported that old translations are not available on the WPML Translation Editor, which for we asured that the translation memory is now shared between sites.

When it comes to internal links, then this is a new request that should be handled on a new ticket.

I actually replied this already. If you have written links inside your content, then you need to edit those links. This can not happen automatically.

If you wish I can offer to take a look into this to confirm if the issue is expected or not, but I am not longer able to log in to the live site.

The private reply form is enabled again, so that you can provide access.

November 5, 2024 at 6:07 pm #16368708

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

On your site the migration banner was still not completed. I finished this task now for you.

The site is currently set to " Different languages in directories" - I have set it to " A different domain per language" and saved the WordPress Permalink settings.

The problem here seems to be, that the domain fr.home-alarm.ca is not valid.

You might need to consider contacting your hosting support and ask them to assist you with setting up this domain, so that it will point to the main site domain.

November 5, 2024 at 6:10 pm #16368712

ronaldT-5

Hmmm, I do not need to ask away. That domain is the wrong domain, it does not exist. The French domain is hidden link

The links are still being referenced with /fr/.

You mentioned I need to edit the link URL to use hidden link (different domain) instead. But, you have NOT told me how to do so since you know we cannot edit translated pages directly and that the URLs do not appear in the ATE.

November 5, 2024 at 6:41 pm #16368817

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

If I open the translation for the homepage, it is only completed to 3% inside the WPML Translation Editor.

It looks like those translations were made on the WordPress-Editor.

How are you going to translate the content? WPML Translation Editor or WordPress Editor?

November 5, 2024 at 6:43 pm #16368819

ronaldT-5

I hate to burst your bubble, but the entire site has been translated in ATE on staging before deploying it.

See below.

Screenshot 2024-11-05 at 1.42.38 PM.jpg
November 5, 2024 at 7:02 pm #16368849

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

This is odd indeed. I will need to escalate the issue towards the second tier support, as the translation memory seems not to work as expected.

November 5, 2024 at 7:22 pm #16368918

ronaldT-5

Actually, I think I know why this has happened. Even though it was at 100% translated on staging the double arrow icon was showing up. I have since rectified it.

I would like to re-deploy staging, but I need to know what you did to fix the license or migration issue.

As for the links not converted for separate domains, I have found a solution already.

November 5, 2024 at 10:09 pm #16369297

ronaldT-5

Okay, I just re-deployed the staging site onto live production. That page should have all the translations in there now.

But, I'm still plagued with the following even though I have already copied the Migration Code over to live site:

Screenshot 2024-11-05 at 5.08.29 PM.jpg
November 6, 2024 at 1:18 am #16369559

Andreas W.
Supporter

Languages: English (English ) Spanish (Español ) German (Deutsch )

Timezone: America/Lima (GMT-05:00)

Please select that it is a copy and proceed.