Using Helix Ultimate With Multilanguage, The Page is Not Found, Redirected To The 404 Template Page. - Question | JoomShaper
SP Page Builder 6 is Here! Learn More →

Using Helix Ultimate With Multilanguage, The Page is Not Found, Redirected To The 404 Template Page.

YL

Yves Lacroix

Helix Framework 2 months ago

Using Helix Ultimate with multilanguage, the page is not found for language urls like site.com/en If I use the language filter option to remove the URL code, then the default language works fine. (i.e. the default URL becomes: site.com) but other languages still have the same problem since switching language to the non-default page addes the language URL (ex: site.com/ja). I confirmed the same thing on 2 helix sites (using the wimble template)

0
5 Answers
Ofi Khan
Ofi Khan
Accepted Answer
Support Agent 2 months ago #200593

Hello Yves Lacroix,

Thank you for reaching out to our technical support forum. I’m sorry to hear about the trouble you’re experiencing.

Please follow this article and set up the multilingual site:

How to Create a Multilingual Site with Helix Ultimate

Best regards

0
YL
Yves Lacroix
Accepted Answer
2 months ago #200595

I am not a beginner, and I followed your instructions to the letter before coming here. Please read my question. There are no issues with multi-language settings. Thank you.

0
Ofi Khan
Ofi Khan
Accepted Answer
Support Agent 2 months ago #200596

Apology for the inconvenience. I need to check the site. Please share your administrator access here to check the issue. Use the Hidden Content box to share the credentials. Make sure that you have a full site backup before sharing.

0
YL
Yves Lacroix
Accepted Answer
2 months ago #200611

The issue is not there when the site is published to a URL without a path. If this is how it is supposed to be, then please add this requirement to the documentation.

problem case: http://XXX.XXX.XXX.XXX/wepages/site1/en

no problem in normal case where site1 is routed by a dns record.

0
Ofi Khan
Ofi Khan
Accepted Answer
Support Agent 2 months ago #200685

Thanks for bringing this to our attention, and for providing a test account for verification.

From your explanation, it appears that the issue only occurs when accessing your Joomla multilingual site using the server’s IP address and folder path, but not when using the actual domain URL.

This behavior is expected and is not specific to our framework—it also affects Joomla's default multilingual setup. Joomla uses SEF (Search Engine Friendly) URLs and language filters that rely heavily on proper domain routing and base paths to function correctly. When accessed via a direct folder path on a server IP, Joomla may not correctly detect the active language or route URLs as intended, which can lead to unexpected behavior.

0