[Waiting for user confirmation] wrong translated URL on website
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.
WordPress 6.7 has introduced a new issue that impact translations, please update WooCommerce and WPML to the latest versions before you report issues. More about this here - https://wpml.org/errata/php-error-wp-6-7-notice-function-_load_textdomain_just_in_time-was-called/
Background of the issue:
I am trying to get the correct URL for a news article on the translated version of the website, controlled by the plugin 'The Events Calendar'. The issue can be seen on this page: hidden link. I need to get this URL: hidden link. On the staging website, the issue was resolved by changing the WPML Language setup from 'A different domain per language' to 'Different languages in file folders'.
Symptoms:
I expected to see the article page when clicking on the Calendar page, but instead I got a 404 error page. The URL is wrong and adds the Dutch home URL in the URL. Instead, I get this URL: hidden link.
Questions:
What goes wrong with the URL translation on the live site?
How can I fix the URL issue on the live site as it was fixed on the staging site?
I would like to offer to have a closer look at the problem and request temporary access (wp-admin and FTP) to the website to investigate this issue further.
You can find the required fields below the comment section when you log in to leave the next reply. The information you provide is private, which means only you and I can see and access it.
IMPORTANT
Please be sure to make a backup copy of the website and database before allowing us access.
If you can't see the wp-admin / FTP fields, your post and website credentials are set as PUBLIC. DO NOT publish the data unless you see the required wp-admin / FTP fields.
I may have to install a plugin called "All In One WP Migration" to make a copy of the website where I can investigate the issue further.
However, I would also be very grateful if you could provide a staging site or copy of the website from your server yourself for this purpose. This step would only be required if the issue is replicable on such a staging site.
If you have any questions about creating such a staging site, you can consult your hosting provider. Just take note that WPML should be registered on this site again.
If you are unable to provide such a copy of the site for testing, please let me know on this ticket.
The private response form looks like this: hidden link
Next time you reply, click "I still need assistance."
Video: hidden link
Please note that we are obliged to request this information individually on each ticket. We may not access any access information not specifically submitted on this ticket in the private response form.
Take note, that the workaround from our errata needs to stay integrated into the file, until the author has fixed this issue. The workaround was not present when I checked your site. I gave it a quick test and it did not solve the issue.
I create a local copy of your site and registered a subdomain in my hosts file.
The issue does not occur on this local install. See screenshot.
I suggest you check the .htaccess file on your server for unexpected redirects or uncommon entries. Also I would like to encourage you to consult the hosting support about this issue, as it only seems to occur on your server.
Ok, thank you for your find. My staging website is also on the same server/hosting. Probably that's way I did not think of this. I will check the .htaccess file and consult the hosting support.
Did you change something on the website the last time you've checked?
I've checked the website an hour ago and the problem seems solved. But I did nothing after you're last reply (nov 8).
Wanted to work on the website (started an hour age) to check the setup(s) you were referring to. The site was offline (strange) and showed a blanc page. Re-installed a full backup of last night. The problem seems solved. So was wondering if you put the workaround in place or did something else to fix this error.
No, the last time I accessed the site was on the 8th of November when I tried to apply the workaround again. It did not solve the issue, so I took a copy for testing.
Please let us know in case the issue occurs again.
