Links Still Showing /pt-pt/ After Setting Portuguese as Primary Language with Elementor Active

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.

This topic contains 3 replies, has 0 voices.

Last updated by Alejandro 5 months, 1 week ago.

Assisted by: Alejandro.

Author	Posts
February 10, 2025 at 8:33 pm #16689475
petrC-8	Background of the issue: I have a website built with Elementor and translated using WPML. The default language is Spanish, and Portuguese is set as the secondary language. I want to change the primary language to Portuguese. Symptoms: When I change the primary language to Portuguese, all the links in Elementor still include /pt-pt/, causing them to break. If I deactivate Elementor, links are correctly without this /pt-pt/ identifier. Questions: How can I fix the issue of links still showing /pt-pt/ after setting Portuguese as the primary language with Elementor active?
February 11, 2025 at 9:51 am #16690677
Alejandro WPML Supporter since 02/2018 Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00)	Hello, You mention ...When I change the primary language to Portuguese, all the links in Elementor still include /pt-pt/ Do you mean the links to open the elementor editor or the links that are seen in the front-end (so links in content, like text, buttons, etc). I suspect you mean the language in the wp-admin page. does it work when you switch it to another language by using the topbar language switcher? Try it out and let me know.
February 11, 2025 at 12:59 pm #16691683
petrC-8	Hi, the issue was in Elementor. Thank you Alejandro.
February 11, 2025 at 2:57 pm #16692453
Alejandro WPML Supporter since 02/2018 Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00)	Oh I see, but from the text it seems you have solved the problem, is that the case? If not, then please Enable the debug.log and try to recreate the problem so WordPress can log the error. send me the file it creates (found in the wp-content directory) and I can try to figure out the next step from it. Regards.