wpSGCacheBypass cookie

Hey @youandus

The cookie is set for both logged-in and non-logged-in users.

The purpose of the cookie is to bypass the cache when you are logged-in, so you can check the changes you make.
When the users logged-out, we change the value of the cookie.

We will remove the bypass cookie for users who have never logged-in on the site and will leave it for registered users only.

Regards,
Stanimir

Perfect thanks

Hi Stanimir

Just one more question regarding the bypass. I’m making some styling changes to my site (changing footer and header colours). I have put my cloudflare in development mode to see changes immediately and I thought the bypass allows me to see changes too but still can’t see them. Is there something I need to do with the sg optimizer plugin to see changes?

Thanks
Celina

Hey @youandus

If you want your non-logged-in visitors to see the changes you have made, you need to purge the cache first.

There is “Purge SG Cache” button on the admin bar that will flush all caches.
After the cache is flushed the non-logged-in users will see the changes

Regards,
Stanimir

great thanks

Sorry, I know this is resolved but did not want to bother you guys with a new thread (unless you want me to make one).

I am getting this notification on my website when I click “inspect element” on any page and then “console”: “Cookie “wpSGCacheBypass” will be soon rejected because it has the “sameSite” attribute set to “none” or an invalid value, without the “secure” attribute. To know more about the “sameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite”

Could you help me out with this please? Is this serious? I see a similar error even on www.ads-software.com but the cookie name is different.

Again if a new thread needs to be made, I will.

Thanks!

• This reply was modified 4 years, 4 months ago by hbk747.

Thanks for reporting ths, it will be fixed in the upcoming maintenance release.