Changing default cookie prefix

  • Resolved jpimagines

    (@jpimagines)


    2 months ago

    By default, the consent category cookies set by this plugin use the prefix wp_consent (e.g. wp_consent_functional). However, some caching solutions, including those provided by some WordPress hosts, will exempt pages from cache if any cookies starting with wp are present. I know that Pressable exempts pages from caching that way: https://pressable.com/knowledgebase/how-does-batcache-page-caching-work/

    I understand that there is a wp_consent_cookie_prefix filter that can be used to programmatically change the default cookie prefix. Using that requires some level of coding familiarity though, and also assumes you know that the prefix can or should be changed.

    Would it be possible to have the default prefix changed to not start with wp? Or alternatively include a UI setting to change the prefix?

Viewing 1 replies (of 1 total)
  • Plugin Author Rogier Lankhorst

    (@rogierlankhorst)

    2 months ago

    As this is intended for core. The wp_ prefix seems the most logical choice. Additionally, suddenly changing this might break integrations.

    A user interface is not something that belongs in this plugin, as there is nothing to configure. Adding it for this one setting seems a bit overkill.

    For this particular use case I’d say the developers of the caching tools should exclude the consent api cookies, which is the simplest solution.

    Alternatively, someone could create a simple add-on plugin to handle this.

    For now, I think the filter solution you mentioned is the best approach.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.