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
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: America/Los_Angeles (GMT-07:00)

Tagged: 

This topic contains 10 replies, has 2 voices.

Last updated by Bobby 1 year, 2 months ago.

Assisted by: Bobby.

Author Posts
March 5, 2024 at 7:04 pm

enzaD

My previous chat got disconnected, and when reconnected had a message that someone would get back to me, but that didn't happen. I'm not sure if there is another ticket in your system we should use as a starting point, or just make a new one?

After updating WMPL recently, we have 502 errors in the Admin when updating some pages on the site. All of the PHP memory settings and WP memory use settings are very high, as per WMPL instructions, and we have disabled all plug-ins except WPML and the issue persists. When WPML is disabled, the issue does not happen.

March 5, 2024 at 8:09 pm
March 6, 2024 at 2:39 pm #15380092

enzaD

Since this ticket was not available yesterday, we started a new one, and that one ended with me being told that long chat would become a ticket here for us to reference and continue with. However I only see this chat which was cut off, not the full chat we had.

March 6, 2024 at 2:48 pm #15380247

enzaD

My dev environment has the following message: This site has moved to a new location
You or someone else moved this site to hidden link. Please keep in mind that:
Translations that you do at hidden link will not appear on this site.
You cannot edit translations on this site.
The site at hidden link is using the same credits for automatic translation as this site.

If you didn't intend to move this site to hidden link, you can indicate that this site should be at hidden link.

This is because we pushed production to dev to sync them up.
I don't see where in the settings we can indicate that this is a dev site - that is how we had it set up previously. How do we register this as a development site?

March 6, 2024 at 6:10 pm #15381207

Bobby
WPML Supporter since 04/2015

Languages: English (English )

Timezone: America/Los_Angeles (GMT-07:00)

Hi,

per our conversation the chat was moved to a ticket for us to further work on it.

You mentioned that

"I can use a backup to return to an older version of the site, and do this both on dev and staging. I think that would verify that the databases are unique. Then I would update all plug-ins except WPML and see if this issue arises."

were you able to do this, and if yes what were your results.

Remember that when I was investigating this issue duplicating the page with the plugin yoast duplicator allowed me to work on the duplicated page but something triggered the ACF fields to be removed.

In summary the issue seems to be related to either a database entry related to this page or an acf field that is causing this behavior, which is why when the ACF fields were removed it updated OK, which is why this needs more investigation.

Regarding the notice, I am attempting to view it but my account details are no longer working, please update them and let me know when ready to check 🙂

March 6, 2024 at 7:16 pm #15381307

enzaD

This image shows the message we are getting on cafdndev
For our staging site, I sometimes get a message asking if it's a dev site, and when I reply that it is a dev site, not production, WPML works fine and doesn't throw any messages. I'm not sure why we have this message on Dev, but there is no easy way to solve it - and I don't want to make it the 'live' site as production of course, is the live site.

Screenshot 2024-03-06 at 2.14.36 PM.jpg
March 6, 2024 at 9:08 pm #15381642

Bobby
WPML Supporter since 04/2015

Languages: English (English )

Timezone: America/Los_Angeles (GMT-07:00)

Please review the following Errata documentation and let me know your results

https://wpml.org/errata/persistent-warning-this-site-has-moved-to-a-new-location/

March 6, 2024 at 9:52 pm #15381712

enzaD

Just like the person in that thread - I am not declaring the site URL in the config file, nor anywhere else. Is there some other solution to connect this site properly at my account end?

March 6, 2024 at 10:26 pm #15381744

Bobby
WPML Supporter since 04/2015

Languages: English (English )

Timezone: America/Los_Angeles (GMT-07:00)

please share with me the updated access details to review

March 7, 2024 at 2:20 pm
March 7, 2024 at 8:39 pm #15386776

Bobby
WPML Supporter since 04/2015

Languages: English (English )

Timezone: America/Los_Angeles (GMT-07:00)

This persistent warning has been resolved in the latest version of WPML, to fix on your site I did the following:

1. Go to Plugins->Add new->Commercial tab->unregister WPML and re register (for now I used my own account, but I will be removing this, please follow these steps and register a new key for this site through your account)

2. Update WPML to latest versions (already done for you)

3. Once step #2 is done a new part shows up in the notification --> "If you prefer not to move this site, you can mark it as a copy and enable automatic translation for it." you click on this and then select "no" and continue and it will remove the warning. (done for you)

The notice should be removed now.

You just need to do step #1 and re register the site with a new key

March 7, 2024 at 8:51 pm #15386834

enzaD

So just to confirm. If the license is for 3 sites, this does, or does not include the dev site? We have production, staging, development and a local version of the site, but only 3 licenses. Isn't there a way to flag this site as development and not need to use one of those keys? Or can we add the production key, and then indicate that this is a dev site?

March 7, 2024 at 9:56 pm #15386932

Bobby
WPML Supporter since 04/2015

Languages: English (English )

Timezone: America/Los_Angeles (GMT-07:00)

Each site requires it's own licesnsce.

So for example let's say you have

1. site.com 2. dev.site.com 3. site.staging.com

each one of them will require it's own key.

When creating a key for your staging site make sure to mark it as "development" as that gives you the ability to register more than one.

So if you migrate site.com into staging the key will copy each time and you will need to update it which is what I believe happened here.

Documentations:
https://wpml.org/faq/install-wpml/#register

https://wpml.org/faq/install-wpml/#register-development-sites

The topic ‘[Closed] 502 Errors’ is closed to new replies.