Eduardo Sans

Hi! Thanks for answering, would you mind elaborating a little bit more on your response? as for instance:

1- If I leave it the way it is, is this going to affect my ads in any way (since Google very specifically recommends to enable it)?

2- Out of curiosity, if I chose to enable the consent mode in the Site Kit instead, what steps should I follow on your plugin (removing code, disabling options, etc.) to not conflict with it?

Thanks!

All good, tahnks

Now it should be solved, could you check please?

Got it! could you check again please? Thanks

Done. Could you check again and confirm everything is right please? Thanks!

Hi there, thanks for answering. I already followed the steps (updating the plugin and connecting to the webapp), the only problem is that I don’t know whether the code is properly placed (I made sure it is above the google tag code, but I don’t know if the cookie yes code is below it because I’m using hooks). Could you please double check that the code is properly place and therefore the consent mode v2 properly functioning? Thanks!

Also, another question, is it necessary to connect to your webapp in order to make the Google COnsent Mode v2 active? I did for my website but I’m taking care of my client’s sites as well and I have to repeat the process there as well (and it would save me time if I didn’t have to connect their sites to the webapp)

Hi there wfpeter! yes, that actually worked, it’s nice to learn about this feature! just one little question: If I export the settings of this site to another site it will also add the allowlist for the firewall (so I don’t need to repeat the process)? Thanks!

This wasn’t in any way personal, it’s not about you being right or wrong. I only cared about fixing the issue (and when I thanked you for your time I meant it).

But the fact remains: the issue was caused by files created by the plugin (it wasn’t the theme nor any other plugin nor my css). I followed the instructions to remove all possible cache using the buttons in the plugin and the tool didn’t do its work properly. Period.

I don’t think anyone would assume that in order to clean old cache stuff I’d have to get in cpanel and remove it manually. But well, now I know :).

Found the mistake. It was caused by litespeed plugin.

Generatepress’ support helped me find it. Apparently there are more .css files within the folders inside wp-content > litespeed. When I got rid of those files, the issue was gone.

@serpentdriver thanks for your time anyway

Yeah, you’re right. I deleted all folders and files inside lscache , then pressed the “purge all” button and the issue is still there

• This reply was modified 2 years, 11 months ago by Eduardo Sans.

got it. The issue is that this is a subdomain, so the way I see it these folders inside lscache would affect all the other sites inside the same cpanel account. Also I see that the folders inside lscache have letters and numbers, so I have no way in knowing what belongs to what :S.

• This reply was modified 2 years, 11 months ago by Eduardo Sans.

1) you mean if I’d have access to a certain folder in my server? yes, i’m using cpanel (i don’t know if you mean that or sth within the plugin – not an expert on LItespeed)
2) cache for admin in backend is disabled

I also tried resetting to default mode in Generatepress to see if any other styles interfered and now instead of a green top bar it shows a blue one (which is basically the last color I put before resetting to default mode in Generatepress). So my guess is that no matter what, with guest mode enabled it will always show the previous design briefly, any thoughts?

hi @qtwrk! yes then it works, if I reset to default setting with the cache enabled there’s no more issue.

So I went through all my customized configurations one by one to check what could possibly go wrong:

– I activate the quic.cloud account – no issue
– Guest mode enabled – issue appear. So I deactivate it and try to find if any other configurations trigger the issue as well, some examples:
– I activate object caché with redis method – no issue
– I activate the browser cache option – no issue
– changed server IP – no issue
– images optimization – set different configurations – no issue
– page optimization – set different configurations – no issue
– Did the same with each and every little configuration throughout the other menus and no issue.

So basically, enabling guest mode is the only configuration that triggers the issue and for performance I’d like to enable it.

More things I’ve tried:
– I removed all custom CSS – issue prevails.
– I work with a generatepress child theme so I revert to generatepress theme (in case there is something interfering with my child theme files) – issue prevails

Everything points to the guest mode. Could you guys provide any other advice? I’m kind of stuck and i don’t know what else to try. Thanks.

I just set it off and the issue remains :S

Ok, edit: I set it off, the issue remained. I put the cache off and the issue was gone (obviously), then I set the cache on with the guest mode disabled and the issue was gone (?).

So now, when i set the guest mode on the issue shows. When I set it off it doesn’t. Does it make sense? why does it behave like this now?

Also, for performance I’d rather have the guest mode enabled. Isn’t there any other way around this?

• This reply was modified 2 years, 11 months ago by Eduardo Sans.