After creating a translation from english to spanish on wordpress page with traveliscious theme the ...

This thread is resolved. Here is a description of the problem and solution.

Problem:
If you're experiencing a 404 error after translating a page from English to Spanish using the WPML plugin on the Traveliscious theme, it might be due to an issue with your .htaccess file or a conflict with existing directory structures.
Solution:
We recommend checking if there is an /es/ folder in the root directory of your WordPress installation, as this could be causing the conflict.

If this solution does not apply to your case, or if it seems outdated, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If issues persist, please open a new support ticket for further assistance at WPML support forum.

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.

Tagged: Exception

This topic contains 5 replies, has 1 voice.

Last updated by Shekhar Bhandari 4 months ago.

Assisted by: Shekhar Bhandari.

Author	Posts
February 25, 2025 at 2:34 pm #16746270
maciejK-33	Background of the issue: I'm trying to implement translation for the home page in the Traveliscious theme using WPML on my site hidden link. Symptoms: After creating a translation from English to Spanish on a WordPress page with the Traveliscious theme, the Spanish version of the page appeared in the menu, but I get a 404 error. Questions: Why does the Spanish version of the page return a 404 error after translation? How can I correctly implement translations in the Traveliscious theme using WPML?
February 25, 2025 at 8:03 pm #16747832
Andrey WPML Supporter since 06/2013 Languages: English (English ) Russian (Русский ) Timezone: Europe/Kyiv (GMT+03:00)	While one of my teammates addresses your ticket, I will provide you with some initial debugging steps. Ensure that you have completed the translation for 100% of your homepage. Then, try re-saving the permalinks by going to Settings → Permalinks. If the issue persists, create a new test page to see if the same problem occurs. Does the issue still exist if you temporarily activate any default theme? Remember to back up your database before making any changes.
February 26, 2025 at 8:30 am #16749628
maciejK-33	I created a new test page and the problem still exists. Also i changed for a default theme. Problem could be that i work on clone site of main site and even when i changed default theme on clone when when i get 404 error it's again with a theme traveliscious from the main site. What elements of homepage i need to have translated exactly? Maybe i miss something here.
February 26, 2025 at 9:03 am #16749812
maciejK-33	I checked one more thing. And the problem disappeared when i use creating links with language name added as a parameter. Could be a problem with different languages in directories because of this clone site?
February 26, 2025 at 9:55 am #16750055
maciejK-33	And one more question. Is WPMl compatible with traveliscious. I cannot find that information.
February 27, 2025 at 4:13 am #16753857
Shekhar Bhandari WPML Supporter since 03/2015 Languages: English (English ) Timezone: Asia/Kathmandu (GMT+05:45)	Hello there, I will be helping you further on the issue. Since it works with language as a parameter, it must be some .htaccess issue, can you also make sure if you don't have /es/ folder on the root WordPress files. Also, I couldn't find traveliscious theme being tested yet. To debug this issue further, I would need to check your site settings once, for this I would need temporary access (wp-admin and ftp) to your site. So could you please provide me with those details, you will find the needed fields for this below the comment area when you log in to leave your next reply. hidden link This info is private and available to you and WPML supporters only. Read more about this: https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/ Note: Backup your sites before providing the credentials or if possible provide credentials for the test site Look forward to your reply. Thanks