Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter jodriscoll

    (@jodriscoll)

    Hi @merijnmolenaar,
    Thanks for your response –

    When you say “our system”, what exactly are you referring to? The defined className’s within the code? If so, those can easily be changed and support the (cache specific) flexibility mentioned above.

    What I’ve done:
    I’ve gone ahead and changed the code to reflect what my client required for our caching infrastructure within Pantheon. I’ll bring in your plugin updates on a case-by-case basis going forward, unfortunately.

    Functionality doesn’t fully support dynamic content control based on cookie states
    The only other solution I see with being restricted to follow the developers cookie naming convention ––– a user would be forced to write JavaScript on-top of the cookie plugin functionality to handle the dynamic, uniquely named cookies. On systems such as Pantheon/WP Engine, cookies are never cached (unless they follow the structure I mentioned initially), which means we cannot conditionally control PHP parsing based on the cookie state (such as rendering elements on a page), hence why JS is now required.

    In the future
    If this changes in a future update to support more flexibility around the naming convention of the cookie (Allowing the user to define variables for cookie name structures, ex:{cookieName}-{cookieVersion}-{multiSiteVerion}), I’ll be sure to roll back the custom plugin approach I had to take.

    Thanks,
    J

    • This reply was modified 5 years, 5 months ago by jodriscoll.
    Thread Starter jodriscoll

    (@jodriscoll)

Viewing 2 replies - 1 through 2 (of 2 total)