lachlanphillips

Super_admin’s also aren’t considered for cache_varys in the admin page. You might need to look at this.

Also in other caching plugins there’s a really clear header showing which vary is active. This would make debugging this kind of thing infinitely easier than trying to read through debug logs.

Thanks

The repro is:

1) Create a new subdomain site
2) Do not add the superadmin user to this site.

The functions I mentioned check user role against the current subsite. Super Admins can be logged in WITHOUT being a user on the site, so it checks the user’s roles and finds none, therefore assumes the user to be a guest.

Cheers

I’ll add that debugging this is very difficult because there’s

1) no indication of the varys in the headers. Eg it’s impossible to tell whether it’s public or private, and which vary is being invoked (if at all)
2) completely contradictory information in your documentation – any cookie with “_lscache_vary*******” is meant to trigger a vary, but in practice it appears that it needs to be setting both a clean “_lscache_vary” AND an additional vary cookie eg “_lscache_vary_mycustomvary”.

Hi, I am having the exact same issue. It’s a bit of an issue to be honest.
Are there any words from the dev on this?

Thanks

forgot to mark as resolved!

That worked perfectly! Thanks for the prompt and helpful assistance!

Sure

Full capability:
https://ibb.co/6PgTNMh

Limited capability:
https://ibb.co/YZtXF53

It continues to show the “Client approved” title, leaving this weird blank space there. I would assume that “capability” would hide the entire row.

Cheers