Remove custom eu_cookie_compliance_data cache entry

Created on 3 July 2025, 27 days ago

This is a follow up to the recent conversation β†’ regarding removing the changes introduced by #3015612: [1.x][2.0.x] Better caching for cookie performance popup β†’ . In summary, the custom cache entry introduced in that issue is redundant with the render cache, causes additional complexity, makes it easier to cause bugs ( πŸ› DNT (Do Not Track) header detection not working when caching enabled Active ), and causes this module to care about unrelated modules (domain module).

πŸ“Œ Task
Status

Active

Version

1.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States pianomansam

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @pianomansam
  • Pipeline finished with Success
    27 days ago
    Total: 115s
    #538440
  • πŸ‡ΊπŸ‡ΈUnited States pianomansam

    pianomansam β†’ changed the visibility of the branch 3534024-remove-custom-eucookiecompliancedata to hidden.

  • Pipeline finished with Success
    27 days ago
    Total: 49s
    #538451
  • πŸ‡ΊπŸ‡ΈUnited States pianomansam

    Merge request created.

  • πŸ‡ΊπŸ‡ΈUnited States pianomansam

    Also adding that ✨ GPC Implementation Active requires the changes in this task.

  • πŸ‡ΊπŸ‡ΈUnited States pianomansam
  • πŸ‡³πŸ‡ΏNew Zealand atowl

    Hi @pianomansam

    So i've spent some time going over this, and i think i've tested enough to make sure this works, just making sure since this will affect performance if we do get it wrong :)

    In my ddev env turned on enough caching to get the X-Drupal-Cache to have a 'HIT' on a 2nd page refresh.
    (For those playing along at home i had to use

    $settings['cache']['bins']['render'] = 'cache.backend.database';
    $settings['cache']['bins']['page'] = 'cache.backend.database';
    $settings['cache']['bins']['dynamic_page_cache'] = 'cache.backend.database';

    )

    I then took your patch, and placed a log message after it, cleared the caches (drush cr), and refreshed the page.
    First page load after cache clearing, i saw X-Drupal-Cache: MISS, and the log message.
    Every then every subsequent page load was a X-Drupal-Cache: HIT, and no log message, as it's obviously coming from the cache.

    Is that what you were expecting/tested?

  • πŸ‡ΊπŸ‡ΈUnited States pianomansam

    @atowl I think your manual testing proves that my change doesn't break page caching, at least. I'd be curious to know if it affects performance or not. I doubt it does, though. It's less about performance and more about maintainability. I don't know how we could easily test performance. Unfortunately, it doesn't look like the original issue did any performance tests, either.

  • Pipeline finished with Skipped
    24 days ago
    #540599
  • πŸ‡³πŸ‡ΏNew Zealand atowl
  • Pipeline finished with Skipped
    24 days ago
    #540605
  • πŸ‡³πŸ‡ΏNew Zealand atowl

    Hi @pianomansam,

    All merged, thanks for your time on this issue!

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024