Home › FUEL CMS News › Share
Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
CRITICAL SECURITY VERSION UPDATE:
https://github.com/daylightstudio/FUEL-CMS/releases/tag/1.4.13
https://github.com/daylightstudio/FUEL-CMS/releases/tag/1.4.13
CMS page caching & authentication
I've created a login system using Ion Auth and CI's controller hooks, together with Fuel's page variables in certain layouts. So a hook determines when a page variable requires a login for a CMS page, and Ion Auth authenticates.
In these layout views, there is a block that retrieves user data from the Ion Auth session data ("Welcome back... last login..." etc). Providing the CMS page is set not to be cached, this works OK. What I'd like to do is force "no cache" for layouts that are to be authenticated - I have 2 such - just in case the client forgets to do this when they create a new page with these layouts. Obviously, when the pages are cached, user data is stored and that's not good!
Is this possible? What's best practice for Fuel & authentication?
In these layout views, there is a block that retrieves user data from the Ion Auth session data ("Welcome back... last login..." etc). Providing the CMS page is set not to be cached, this works OK. What I'd like to do is force "no cache" for layouts that are to be authenticated - I have 2 such - just in case the client forgets to do this when they create a new page with these layouts. Obviously, when the pages are cached, user data is stored and that's not good!
Is this possible? What's best practice for Fuel & authentication?
Comments
$this->fuel->set_config('use_page_cache', FALSE);