caching for logged in users? confusing conceptually, need guidance.

[darrenc]

I'm trying to understand how I could have users log in as "members", provide them with a customized experience, but still serve them cached pages?

For example let's say I have 3 roles

• Guest
• Member
• SuperUser

And let's say I have a NavBar type component that has a menu. Plus it has "log in!" if guest,  or "logged in as Mike Smith"

• I would want guests to see a cached site with guest-only page access.
• Members should also see cached pages, but their menu may have access to members-only pages or fields or information. Furthermore they might have a "logged in as Mike Smith" element.
• SuperUsers can stay uncached.

How does one go about creating that cache so that visitors aren't constantly re-creating the menu? Or that when "Sally Baker" logs in, she doesn't see a homepage that is cached for "Mike Smith" with all his elements?

Thank you in advance for any replies. 

 

 

[Zeka]

Hi @darrenc

You can use MarkupCache or WireCache to cache some specific areas of your frontend.

[loukote]

@Zeka

 

@darrenc

Each si te has its own strategies when it comes to FU. Common to them is the use of roles to decide which block should have what content. This is an argument that supports caching for logged in users is only useful per role, not for all together.

Having a similar issue with a website I'd be interested in a solution if it exists.