We have noticed one bug in Osclass core code.
when "Language code in URL" is enabled in general settings. and permalink rule for Page URL: is changed to "{PAGE_SLUG}" only then home page of site for other language return 404 error page.
Also some other pages also return 404 error page on site.

This happens only when two conditions are true:
1) when "Language code in URL" is enabled in general settings
2) and permalink rule for Page URL: is changed to "{PAGE_SLUG}" only.

After changing these two setting when you change language on front end you get the 404 error page on homepage and on some other pages.

Please let us know how we can fix this.

I see, it's most probably because home page URL match to static page rewrite

Is there any solution for this?
we have so many static page urls and we want keep them as it is for SEO reasons (without page id in URL).
Please let me know if there is any quick fix for this.

Also when we enable "Language code in URL" is it possible to load default language without language code in url? we have English as default language, can we load English version without 'en' in URL. and for rest of Languages we want Language code in URL.

@Hugo
Most probably yes, will need to review regex that can take some time

May I know how long this will take and if there is a way on how to speed up the process.
Or can you provide us a solution that we can implement ourself on site. also what we have to take into account if we do it ourselves?

Hey, any updates on this?

no and there will be no update soon.

@Hugo
If you do not use page ID, Osclass is still able to identify static page based on slug.
However it's not possible to use just page slug without anything else. It's not possible to differentiate if you are talking about static page, category page or home page.

Solution is to use prefix for your static content.

Example static URL that will work:
help/{PAGE_SLUG}
In this case make sure you does not have category with slug "help"