Multilangual site: always en-GB as language with the version 2

Hi Amar,

Thank you for the detailed report and for sharing the examples. I’m sorry for the trouble you experienced.

The first issue you described is related to a core Joomla bug that, in some cases, prevents the database schema of the extension from being updated correctly.

I just checked the links you provided, and they appear to be working as expected on your test site running version 2. The page loads with the correct language.

Could you confirm if the issue is still occurring on your side? Also, have you perhaps switched the test site back to version 1 as well?

If the problem persists, please open a private support ticket and share administrator access to your test website. This will allow me to check your setup directly and identify the cause.

Best regards,
Lefteris

Hi Amar,

I’ve identified the cause of the issue — it’s coming from the “Route 66 – HikaShop” plugin.

In that plugin, we load a helper directly from HikaShop to generate links where needed. It seems our code needs to be updated, as loading that helper is triggering the problem with the language attribute.

Since you’re not using custom URLs for HikaShop, I’ve disabled the plugin for now, and the language tag now appears correct. Please verify on your side.

Regarding the crawler issue, it’s caused by Cloudflare’s bot protection (“verify that you are human”), which interferes with the request. I’ll update Route 66 so it doesn’t flag any issues when the Cloudflare protection page appears. If you plan to keep using the crawler (which I recommend, as it provides a global place to set metadata), you may want to see if there’s a way to whitelist it in Cloudflare. In the meantime, I’ll also explore workarounds for such cases.

Lastly, since your production site is currently downgraded to v1, you may encounter problems when upgrading again. If that happens, please update the private ticket and share administrator and database access for the production site so I can handle the upgrade for you.

Best regards,
Lefteris

Hi Amar,

We will release an update today or tomorrow that resolves the HikaShop issue, so you’ll be able to use all the features again, including AI Tools and Sitemaps.

Regarding Cloudflare, instead of creating a Route 66–specific rule, I recommend whitelisting your origin IP if possible. Crawling requests come directly from your web server, so this approach should be more reliable.

I also noticed that even when I visited your site using a regular browser, I still encountered the “Verify you are human” challenge. You may want to adjust your Cloudflare rules to be a bit less strict to improve accessibility.

Best regards,
Lefteris

Hi Amar,

After some research, it appears you can create an IP-based exception in Cloudflare’s Security Rules to bypass the JS challenge. This way, requests from the specified IP will be allowed without triggering the challenge.

To set this up:

1. Log in to your Cloudflare dashboard.
2. Select the domain in question.
3. Go to Security → Security Rules.
4. Create a new custom rule with the condition: IP Source Address equals your origin IP.
5. Set the action to Skip (JS Challenge).
6. Save and deploy the rule.
    

This should allow requests from your IP to pass without being challenged.

Please note, I haven’t tested this myself — it’s based on information I found online.

Best Regards,
Lefteris

Hi Amar,

Glad to hear it’s working!

Since your site is behind the Cloudflare proxy, your server’s IP should remain the same. If it ever does change, your site would stop working until the DNS in Cloudflare is updated to point to the new IP — so it’s unlikely to change without you being notified or making changes with your hosting provider.

Thanks for letting me know!

Best Regards,
Lefteris

Hi Amar,

Glad to hear everything is working well now and that Route 66 can read the meta data correctly.

Regarding “too many elements,” I assume you’re referring to the excessive DOM size warning. It’s based on Google’s recommendations and is something to keep in mind when redesigning your site or changing templates. If your site performs well in browsers, you can safely ignore it for now.

I’ll go ahead and close this ticket, but if you need any further assistance, feel free to open a new one.

All the best,
Lefteris