Skip Navigation

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.

Sun Mon Tue Wed Thu Fri Sat
- 8:00 – 15:00 8:00 – 15:00 8:00 – 15:00 8:00 – 15:00 8:00 – 15:00 -
- 16:00 – 17:00 16:00 – 17:00 16:00 – 17:00 16:00 – 17:00 16:00 – 17:00 -

Supporter timezone: Europe/Rome (GMT+01:00)

This topic contains 68 replies, has 3 voices.

Last updated by Alejandro 1 year, 1 month ago.

Assisted by: Alejandro.

Author Posts
September 28, 2023 at 2:26 pm #14482581

Alejandro
Supporter

Languages: English (English ) Spanish (Español ) Italian (Italiano )

Timezone: Europe/Rome (GMT+01:00)

Hello,

This is what i see: hidden link

So whatever's happening has nothing to do with the account, which is a good thing. at this point then could it be that you are using extensions on your browser? if so disable them for the time being.

At the same time try to access your site from an incognito browser and try again because if i can access on your site, on your server, with your same user, then the problem is likley found on your pc (which is quite uncommon, by the way!)

Try it out and let me know how it goes.

September 29, 2023 at 7:04 am #14485845

bjornL-7

Hi,
OK, so I logged in as incognito, and it worked to access the translations.
Then I logged in in the regular browser, non-incognito, and that worked too! Very strange.

However, it seems like the translation memory is completely gone. Take the /valuebetting page as an example. As you can see here, the page is fully translated to Swedish: hidden link

BUT: When I enter the ATE translation for that page, almost NOTHING is translated in ATE. This happened somewhere in the steps I have taken in this 4 page support thread.
How can I get back the translation memory for everything that has already been translated??

Also: When in the STAGING site, hidden link, I get this errors in the attached screenshots when trying to translate /valuebetting

Please how do I get out of this mess? I can't update neither our live nor or staging site.

Screenshot 2023-09-29 090113.png
Screenshot 2023-09-29 090310.png
September 29, 2023 at 1:32 pm #14487895

Alejandro
Supporter

Languages: English (English ) Spanish (Español ) Italian (Italiano )

Timezone: Europe/Rome (GMT+01:00)

Can you please check your sites now and see if the banner is gone and also if the page has recovered its memory?

To do that please go to WPML > Translation Management and then resend the page you used as a reference on your last reply, so it can be translated again (otherwise you'll keep seeing the old session of the translation which was empty).

If the banner still remains in the staging site, allow me access to the staging site and i'll have it fixed and tell you the steps to prevent this in the future, ok?

October 2, 2023 at 6:38 am #14494615

bjornL-7

Still having issues. The translated content in ATE is gone. Please can you just login to both live and staging and fix the problems for me? Same credentials (my user) on the staging site as for the live site.

October 2, 2023 at 8:33 am #14495791

Alejandro
Supporter

Languages: English (English ) Spanish (Español ) Italian (Italiano )

Timezone: Europe/Rome (GMT+01:00)

On the production site: hidden link

I can see the content correctly showing translated or with the past translation memory.

there are some with new content like the "FAQ" which needed to be translated, for example, or with updated segments but it is working normally and it's not empty.

What you had missed is that you had sent the job to the translation basket but then left it there and you kept seeing the LAST translation job (or session) which was empty, before the changes on my end.

---------

About the staging site. i have fixed the migration banner but please do the following in order to prevent it from happening again: hidden link

Regards.

October 3, 2023 at 7:00 am #14501545

bjornL-7

So I need to:

1. On the LIVE site: Manually go through all pages/layouts/elements that are translated and update the translations again to 100%.
2. Push live to staging.
3. Select this is a COPY (on the staging site), when/if wpml asks me.

Then, when I have made changes on the staging site that I wish to push to live:
1. Push staging to live
2. Select this is a COPY (on the live site).

Is the above correct?

Additional questions:
1. Previously, I needed to change the WPML license key every time I pushed to staging or live. Is this not necessary going forward, or should I keep doing this?
2. I should NEVER select that I have MOVED the site. Correct?

October 3, 2023 at 12:51 pm #14504847

Alejandro
Supporter

Languages: English (English ) Spanish (Español ) Italian (Italiano )

Timezone: Europe/Rome (GMT+01:00)

the above is all correct.

1. Previously, I needed to change the WPML license key every time I pushed to staging or live. Is this not necessary going forward, or should I keep doing this?

ANSWER: the license has nothing to do with the migration banner. i'd suggest that you leave the license on the live site and ignore it on the staging site since it will not really affect anything on your site at this point (it could affect updates mainly so you can only license it when you want to update the plugins).

2. I should NEVER select that I have MOVED the site. Correct?
ANSWER: in your case, it's not needed to use the "moved" option, that's correct. we are already thinking of a better workflow so you never have any blocking situation like this again, no matter what option you've selected but just in case, for now select the "copy" option eveerytime and you'll be good to go 🙂

Regards.

October 3, 2023 at 1:09 pm #14505069

bjornL-7

OK. Good that we are getting closer to a solution here. But are you having issues with ATE at the moment?

I have marked all required required pages and elements to translate as 'Required', resulting in a list of 28 pages and elements. These need to refresh the translation, so the translation memory get up to sync.

However, when trying to update a translation (in an incognito browser), it takes between 1-3 MINUTES for the ATE page to load.

Let's say the average load time is 2 minutes.

Having 28 pages and elements to be translated into 7 different languages, I am looking at a load time of 6.5 HOURS just to load the ATE translation page.

I tried to create a gif screencast of this, but the file ended up to be over 30Mb, so I can't attach it in this case.

Are you having issues with ATE at the moment?

October 3, 2023 at 1:14 pm #14505079

bjornL-7

3 minutes and counting on this one

Screenshot 2023-10-03 151349.png
October 3, 2023 at 4:04 pm #14507289

Alejandro
Supporter

Languages: English (English ) Spanish (Español ) Italian (Italiano )

Timezone: Europe/Rome (GMT+01:00)

Can you please send me the URL and the language pair you had issues with? because no, we're not having issues with ATE at the moment.

You mention it takes 2 minutes in average, but they end up opening or they get hanging in there without opening at all?

Please send the URL my way so i can investigate because i suspect the problem is that those pages are quite long and there's an "automatic translation by default" enabled which might take longer than usual to translate everything.

This feature can be disabled once any ATE page opens but i'd like to confirm if this is indeed the case.

October 4, 2023 at 6:21 am #14509797

bjornL-7

Take the homepage as an example: hidden link When trying to edit the Swedish translation: hidden link
The ATE page just loads and loads. Sometimes it ends up opening, but most often not. Just loads and nothing happens.

October 4, 2023 at 9:18 am #14511175

Alejandro
Supporter

Languages: English (English ) Spanish (Español ) Italian (Italiano )

Timezone: Europe/Rome (GMT+01:00)

I checked this out with our developers and the reason why it loads slowly in some pages is just because the Automatic translation is working and it seems that deepl sometimes takes a bit to load the translation.

I asked them however if they could speed things up or check why is this happening. if you don't want to use the automatic translation by default, you can deactivate it by accessing any page on the translation editor.

However, just so you know, our developers are looking into this to see if the problem was indeed with the automatic translation editor or if it was because of something else.

In the meantime, try to load another page when that happens, it will load but it's indeed taking way too long and it seems to happen randomly (i tested it on a few pages and only 1 was super slow, the rest were quite fast to load).

I'll keep you updated and don't worry we will reward you for this issue 😀

October 4, 2023 at 11:19 am #14512251

bjornL-7

OK, looking forward to the update on the load time.

Just to double check. I should ALWAYS use the send to translation basket and use that method of translating a page, and NEVER use the alternative method of translating directly from the page itself, to avoid using an old translation-session and seeing an old version of the page?

October 4, 2023 at 1:21 pm #14513399

bjornL-7

OK, I have disabled all three translation engines (see screenshot).

I have added an element to the basket, and assigned myself as a translator.
In the translation queue, I click "Translate" for that element ("aa CTA Sure betting trial").
You can see this element by filtering the title (see above), or status "In progress" (first one in the list).

When clicking the Translate button, the ATE page is just loading infinitely. It never ends up opening (see screenshot): hidden link

Screenshot 2023-10-04 152044.png
Screenshot 2023-10-04 151548.png
October 4, 2023 at 3:32 pm #14514637

Alejandro
Supporter

Languages: English (English ) Spanish (Español ) Italian (Italiano )

Timezone: Europe/Rome (GMT+01:00)

Hm, your'e right. it's still happening.

I'm currently waiting on our developers for more information about this because it's indeed a weird behaviour but doesn't seem to be affecting everyone. i'll update you as soon as i have more info on the matter.

The topic ‘[Closed] This site has moved to a new location’ is closed to new replies.