Contrib.social

API for altering client hash caching key

Open on Drupal.org →
Created on 24 September 2013, over 11 years ago
Updated 11 February 2025, 12 days ago

At the moment, per Drupalcon Prague talk by WimLeers (it was awesome!), I asked about the option of altering the hash used for client caching in client side caching.

Use case:
Node is an entity and the "new" marker is cached per uid (& entity_id?) at the moment, but we should be able of caching per language too now that we only have one entity with translatable properties, and one contrib module (or the language module itself) should have the ability of altering the hash so language is considered.

📌 Task
Status

Postponed: needs info

Version

11.0 🔥

Component

cache system

Created by

🇪🇸Spain penyaskito Seville 💃, Spain 🇪🇸, UTC+2 🇪🇺

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Comment 12 days ago →
    🇺🇸United States smustgrave

    Thank you for creating this issue to improve Drupal.

    We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.

    Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

    Thanks!

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024