Background of the issue:
Our site hidden link was on AWS hosting using Apache, and we had activated the WPML option: 'Use directory for default language' to redirect 'hidden link' to 'hidden link'. After moving the site to another hosting (wp.com) which uses NGINX, the site in Spanish is not working as expected.
Symptoms:
If you type hidden link it redirects to a post and not the Home page. Navigating through different site sections displays a 404 page.
Questions:
How can we configure WPML on NGINX to use the directory for the default language?
What steps should we take in the WPML troubleshooting section to resolve this issue?
Thank you for contacting WPML support, I’m happy to help you with this issue.
Do you disable the option "Use directory for default language"? For other pages, I don't see the default language code in the URL. For example hidden link
I also need more information on your site by sharing the debug info. If you don’t know how to share the debug info, please follow this article https://wpml.org/faq/provide-debug-information-faster-support/
Your next reply is enabled to share the debug info.
Hi there! and thanks heaps for your reply, I really appreciate your assistance.
- Do you disable the option "Use directory for default language"? For other pages, I don't see the default language code in the URL. For example hidden link
that is the weird thing, so, the default language on my site is Spanish, if I activate that option, after that, if you type: hidden link it redirects to a random post of the site. 🤷🏻♂️
and if you navigate to "inspiracion" or "ciudades" etc... it displays a 404 page, and I don't know why.
because, the other 3 languages work just fine, just try to navigate:
I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue. It would be better to have a testing site where the issue is replicated. Your next reply is set to private to share the info.
❌ IMPORTANT: Please backup your database and website before proceeding ❌
You can use this plugin to create the backup: https://wordpress.org/plugins/duplicator/
✙ I would need your permission to de-activate and re-activate Plugins and the Theme to change configurations on the site if needed. This is also a reason the backup is critical.
1. Regarding the redirection from hidden link to a post hidden link
it is related to the custom theme on your site. If I switch the theme to a WordPress theme (2024), this issue is gone.
2. Regarding the option "use directory for default language", you might need to contact WordPress.com support and ask them to update the Nginx configuration file to handle the language directories properly. Here is an example:
# Handle default language directory
location ~ ^/([a-z]{2})(/.*)?$ {
set $lang $1;
set $rest $2;
try_files $uri $uri/ /$lang$rest /index.php?$args;
}
I will have a look to the post redirection but I think it's related to the Nginx config cause when we had the site on AWS hosting everything was working just fine.
I've already sent a message to wp.com support. let's see how they say...
thank you so much for your support and I will keep you updated about any progress
Thanks for the update from WPML. However, some plugins and themes may tell you that to function, they need you to make changes to the NGINX configuration. However, this is not possible here at WordPress.com. Please reach back out to the WPML developers to see if they have any alternative solutions.
so, I would like to ask you if there is a different option besides the nginx config. maybe a function or similar to add in functions.php file?
otherwise I think we are not wil be able to solve this issue.
Our 2nd tier support is still investigating the issue, I will let you know when I have more information.
Meanwhile, you can disable the option "Use directory for default language" and still use the URL format language directory for the second languages on your site.
Our 2nd tier support asks for permission to make some changes on your site, specifically the theme and deactivate some plugins. Please let me know if we can do that on your site because it is related to the WordPress.com hosting, not possible to replicate on another hosting or local host.
