New in 2.2.1: Session-less Contexts

We added a cool new feature in 2.2.1 for sites that have no need for delivering personalized content. It's called Session-less Contexts, can improve front-end performance ~40 times, and you can read about it here.

Hey Jason,
Maybe I missed something. Posted in the context of web configuration option . But the speed of rendering the page has not changed, only became a session is not available.
What have you told a secret? [ed. note: valikras last edited this post 12 years, 8 months ago.]

If everything on a Resource is properly cached, this helps avoid the database connection completely (or session files if you configured sessions differently). If you have uncached Snippets or Plugins executing on the Resource that require a database connection, your bottleneck is there, and not with session handling.

Thank Jason for your reply.
Ha! It works!
It was not cached in the snippet .....

Hey, just thought I'd chime in with a huge caveat to this approach.

Once I enabled this setting I found that the 'published' setting was being ignored entirely. Disabling it restores the expected behaviour.

I was going to suggest that admins should be informed of this, but I can't see a case where this behaviour would be tolerable, so I guess that would be a bug. Want me to file it with the tracker?

That should definitely be reported as a bug if that is the case...

Okay, thanks. I've reported the bug at: http://tracker.modx.com/issues/7652

Thanks for catching this nasty bug. Fixed for 2.2.2-pl.

I just tried this on 2.2.2 and it stopped me logging in to the manager?

I had to delete the setting in phpmyadmin and delete config.cache.php to get back in?

You cannot add this to System Settings or the mgr Context Settings. This is for front-end Contexts ONLY.