Displaying same language when switching to another language

Do you know if the qtranslate-xt plugin uses cookies depending on the selected language? Cookies would be mandatory so that you can use this plugin together with the cache plugin.

Hi! Thank you for your prompt answer. I’m not sure if qtranslate-XT uses a specific cookie for every language. If so, do you mean that, by excluding that cookie, things would work out well?

Also, you might find relevant that, if I disable object cache, things work acceptably well. Again, it’s not the perfect scenario, since object cache enabled is a key setting to increase speed. Is there any setting I can play around with?

Sorry if I make too silly questions, I’m not an expert, and my site takes 12 secs to load, far beyond the promised “blazing fast” when I switched to LiteSpeed. What am I doing wrong? Thank you again.

You don’t ask stupid questions. There are only stupid answers. ??

Hi! Thank you for your prompt answer. I’m not sure if qtranslate-XT uses a specific cookie for every language. If so, do you mean that, by excluding that cookie, things would work out well?

The purpose of the cookies is not to disable the cache depending on them. Cookies are about so-called cache varies. This means that each language can have its own cached copy, which makes it easy to solve your problem. Either you ask the plugin manufacturer whether they use language-dependent cookie values or you post the link to your site.

Hi! I want to keep as much as private about my project, because I might not be running it in the future. However, in this link, you’ll find a text file with the url, as well as the cookie policy url, where you can find information about qtranslate-XT cookies (BTW, it seems qtranslate-XT does use a specific cookie). Sorry if it’s not the most elegant way. :”(

I’ve enabled the object cache again, so that you can experience the issue for yourself. Also, any other recommendation to make my website faster (either in the plugin settings or the quic.cloud settings) is welcome! :”D

Thank you for your disposal to help with this, and for your kind answer before.

please provide the report number

you can get it in toolbox -> report -> click “send to LiteSpeed”

Sorry if it’s not the most elegant way.

That’s no problem at all. ??

But the good news first, your language plugin uses cookies depending on the selected language. Thus, the most important requirements would be met. However, there are at least 1 if not 2 additional handicaps that cause me some concern. But before I overwhelm you, let’s try to solve the matter step by step, where there is more than 1 solution, but not every solution is automatically a solution. So it may be that we have to make several attempts.

1. You seem to have installed a security plugin that is preventing guest mode from working. Therefore, search your plugins and either disable this or, if possible, define an exception. Either to the plugin directory of the LiteSpeed plugin or for the guest.vary.php in the LiteSpeed plugin directory.

please provide the report number

@qtwrk Done. TGYEBLRL

You seem to have installed a security plugin that is preventing guest mode from working.

@serpentdriver This is the initial list of suspects:

-Complianz
-Age Gate
-Members by Memberpress
-Redirection
-Disable Cart Fragments
-Siteground Security

I’ve just disabled SG Security and Disable Cart Fragments, which are two disposable plugins (I’m using the earlier just to create a secure login page, but there are many out there that can do the job, too).

However, the error persists, and switching to a different language (specially in the home page) displays the previous language texts.

if possible, define an exception. Either to the plugin directory of the LiteSpeed plugin or for the guest.vary.php in the LiteSpeed plugin directory.

How can I do that?

But before I overwhelm you

(Already overwhelmed in step 1. *Laughs nervously*)

First of all, we have to create the basic conditions for the actual solution to work. With the deactivation of the SG plugin the Guestmode works, so the issue with Guestmode is fixed. Let’s do the next step.

2. Familiarize yourself with the crawler simulation in the Crawler menu item.

OK, I’ve read LS’s Crawler documentation.

I went ahead and configured these settings in case that was the next step, but the error persists. How can I properly proceed from the Crawler’s settings?

Before that there would have been an intermediate step, but it doesn’t matter, tell me what you entered in the crawler simulation and whether you purged the cache.

We’ll do that with the crawler later, because otherwise you’ll get out right now. ??

Oh, thanks for your patience! As I said, I entered these settings, and yes, I purged the cache. Again, the language displayed when switching to another language shows the previous language prior to switching.

(Also, the page looks like it loads twice before being fully loaded).

Then we (you) have a problem and what I feared happened. This means that not only does the crawler simulation for the cache warmup not work, but there is no solution to your problem. There is a solution and one could compensate for the dysfunction of the crawler simulation via .htaccess, which would then work. But the settings in the .htaccess are not taken into account by quic.cloud and if QC does not work, this solution cannot be used either. Without QC everything wouldn’t be a problem and we would have been done long ago.

Nevertheless, we can solve something else, namely the age verification query. This doesn’t work either.

Oh, that’s so bad! :”( How is that the .htaccess settings have no impact on quic.cloud, and the other way around? Does it mean this website doomed?

At this point, disabling “Object cache” is the only workaround to make things work (I’ve just did it, plus purging). Not the ideal scenario because it’s a key optimizing setting, but at least, the user gets the right language.

What would you do, even in a bigger picture? Maybe switching from Complianz to another cookie manager? Switching Age verification to another solution? Should I ask my webhost to tune my server in some way?

If disabling of Object cache works, then disable it and keep the cache always warmed with the crawler. This is much faster as Object Cache. You only notice the disadvantage of the deactivated object cache in the checkout.

Switching Age verification to another solution?

No, just do the following setting in cache plugin.
– Go to menu -> Cache -> Excludes tab and enter “age_gate” without quotation marks in textfield “Do Not Cache Query Strings”

– Do a cache purge all

– Give Feedback if done