Background of the issue:
I am trying to translate a page from English (EN) to Spanish (ES) using WPML. The new page (ES) was created without any issue. To review the issue online, it might require creating a new account on the site. The issue can be seen at the following link: hidden link
Symptoms:
I am getting a 'Bad Gateway' (nginx) error code when accessing the new page. The 'Advanced Translation Editor Error Logs' do not show any change or new log.
Questions:
Why am I getting a 'Bad Gateway' error when accessing the translated page?
Why are there no new logs in the 'Advanced Translation Editor Error Logs'?
Welcome to WPML support. Would you please follow the steps below?
- Make sure that you are logged in wpml.org.
- Go to "WordPress Dashboard > Plugins > Add New > Commercial (Tab)".
- Click the unregister link. (no worries the translations are safe)
- Click the "Register WPML" at the right section of the screen.
- Click the "Get a key for this site" link annotated in the screenshot below.
- A new page will open up and the auto-generated key will show in pop-up.
- Copy the key and paste it into the "Site Key" input box annotated in the screenshot below.
- Click the "OK" button.
Thank you for the answer, I'd appreciate it if you could give me the URL/User/Pass of your WordPress dashboard after you make sure that you have a backup of your website.
It is absolutely important that you give us a guarantee that you have a backup so if something happens you will have a point of restore.
Make sure you set the next reply as private.
We might need a copy/staging version of the website for further troubleshooting and we will ask for that. But for now the login info for the current site should do the trick.
I will check:
hidden link
Please give me all the steps or users needed to see the issue on the backend
Thank you for the video. The way that we can test is to replicate the problem on a clean installation and see if the same thing happens there.
To be able to report the compatibility issues we need to replicate the issue on a clean installation.
I created a clean installation of WordPress, WPML, and all necessary WPML add-ons.
You can access the WordPress dashboard using the link below: hidden link
Kindly follow the steps below:
- Install your theme.
- Install the necessary plugins.
- Try to replicate the issue.
This will help us to report the probable issue to the compatibility team and solve the possible problem faster.
And please only keep the WP Residance related plugins.
Regarding the 502 error as it is happening only when the Add property template is used that shows it must be theme and wpml related.
By the way the login information you shared is still the live website. We will need the copy of the website. So we can do tests there while you add the theme on the clean installation above.
Thanks.
I also suggest that you contact your hosting service provider and ask them to give you the log that causes the 502 error. That might give us better understanding.
Thank you for the details. It seems that the issue happens on your server only as it is not possible to replicate the issue on a clean installation.
The 502 error happens on server level so enabling the WordPress debug will not give the error behind the seen.
If you can contact your hosting service provider and ask them to give you th elog when you check the Spanish version that should give us better information.
I own the server and I'm managing the server configuration, here's the info from the logs when accesing the translated page: from /dashboard-add-property/ to /es/dashbord-agregar-propiedad/ at (17/Jun/2025 19:15 +0000)
* stderr.log (no time)
[UID:1000][152253] Reached max children process limit: 10, extra: 0, current: 10, busy: 9, please increase LSAPI_CHILDREN.
* error.log (no entry at 19:15)
2025-06-17 19:11:25.371224 [NOTICE] [95186] [172.80.1.3:41876#flywp] [STDERR] PHP Warning: Undefined array key "price_max" in /var/www/html/public/wp-content/themes/wpresidence/libs/advanced_search/searchfunctions.php on line 1128
* debug.log (no entry at 19:15)
[17-Jun-2025 18:16:44 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the
wpresidence
domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the
init
action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/html/public/wp-includes/functions.php on line 6121
Please reach out to the WPResidence theme developers and check whether they’ve released a fix for this issue. Before doing so, make sure you’re using the latest version of the theme.
As you can see, this change has affected many plugins and themes: Search results on WordPress.org. Can you try to reproduce the error using a default WordPress theme (like Twenty Twenty-Five) on a staging site?
thanks for the update (I'm no longer seeing the option to post the comment "Hide");
The error (notice-function-_load_textdomain_just_in_time-was-called) as mentioned before on the thread doesn't affect the translation process, all others pages and strings were translated without any issue.
With Christopher, we already did try and reproduce the error in the clean install, doesn't happend.
Also, this is the answer from WPResidence (theme) support:
------------------
The errors that you get from the theme are not related to the 502 error:
* debug.log (no entry at 19:15)
[17-Jun-2025 18:16:44 UTC] PHP Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the
---> This is caused by the WordPress update and it will be reviewed for the next theme version, but this does not affect the site functionality.
The other errors are not related to the theme and we cannot debug on server level to be able to advise further.
Since this happens only for the translated page, WPML might have seen this before and can help.
The theme manages the main language. All translations are managed by WPML.
WPML is a 3rd party plugin and we offer support only within the limits of our knowledge.
I am not familiar with the above behavior. Please contact the WPML support.
If you are not happy with WPML support, we have a contact with the team leader of the support team and we can escalate the ticket for you, to ensure good support from the WPML team.
---------------
Can you please, try and review the issue on my webpage again?
Languages: English (English )Spanish (Español )German (Deutsch )
Timezone: Europe/Madrid (GMT+02:00)
Hi Pavel,
To properly investigate this, we need to be able to reproduce the issue. So far, the only error we’ve seen is related to the wpresidence theme, and there are no other relevant logs available. I enabled WP_DEBUG_DISPLAY, but nothing was output.
The only log currently available is the server’s error.log, which shows a fatal error related to the Envato Market plugin—caused by a call to an undefined function since the plugin is deactivated (Not related)
Without additional error information or a way to replicate the issue on a clean installation, our debugging options are quite limited. However, we could clone the site and deploy it locally on a local server environment to see if the issue is reproducible there. Please let me know if this is OK for you.
thanks for the update (I'm no longer seeing the option to post the comment "Private");
I think that I mentioned before, I don't think there's a theme(WPResidence), or plugin(WPML) issue or missconfig between the pair;
I think could be an issue between some kind of cache (tried on different enviroments), or the link store on the WPML servers, maybe because I changed from the first time using a char ñ from the Spanish translation from Add-new-property to Añadir-nueva-propiedad, later when I updated the Title to Agregar-nueva-propiedad (Add->Añadir or Agregar are the same) is when the 502 Bad Gateway appear.
I just added a French version and it worked fine.
YES, please, clone it or wherever is needed on my website (I have multiple copies and backups) to search or replicate the error, but I strongly believe it's something related to some cache issue in some place.
