Add option to disable session data.

  • Resolved NCompass

    (@ncompass)


    1 year, 7 months ago

    Since 3.5.0 sessions have been introduced to this plugin which are created on every page. This breaks cloudflare page caching provided by Super Page Cache for Cloudflare plugin across my entire website (which requires no sessions or cookies or the cache is bypassed). It also breaks our hostings page cache mechanism too (which is similar).

    It’s my understanding that sessions are kind of a bad idea in 2023, a session generally implies unique data for that user and breaks caches. So unless you are of course logged in, or checking out or something, it should be avoided. But I understand it may have been added to support some of the more advanced features of this plugin.

    I personally only use referer on one form on our website — we just need to know where they came from, which worked perfectly on 3.4.0 with cache disabled for that one page which held the form.

    But now the plugin has effectively disabled the page cache across our entire website, which is really not worth it for the functionality we need on one page.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Tessa (they/them), AuRise Creative

    (@tessawatkinsllc)

    This is valid feedback. I can take a look for an alternative to using sessions. The reason I used sessions was to be able to access the current post object during an AJAX call, which is used for cache compatibility mode for certain built-in shortcodes since it’s otherwise unavailable in an AJAX call.

    But you’re absolutely right that this feature, which may or may not be used, doesn’t outweigh all of what you mentioned.

    Plugin Author Tessa (they/them), AuRise Creative

    (@tessawatkinsllc)

    If you update to version 3.5.3 of the plugin, you’ll see that sessions were scrubbed completely.

    Built-in shortcodes that are listed here, including CF7_referrer can still use cache compatibility mode since they’re retrieved via JavaScript and no AJAX request is sent.

    The shortcodes that require looking up the current page ID are likely already cached anyway and shouldn’t be using cache compatibility mode, so I guess it’s more or less moot to even try to make a fix for something that ain’t broke!

    Thank you <3

    Thread Starter NCompass

    (@ncompass)

    Thank you so much, all working!

    We can now also use the cache friendly mode and no longer exclude that one page from cache ??

    Thank you again – couldnt ask for a better response/result.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Add option to disable session data.’ is closed to new replies.