Add object-cache awareness for persistent backends #32

Open
opened 2026-07-01 01:05:28 +00:00 by manlycucumber · 0 comments
manlycucumber commented 2026-07-01 01:05:28 +00:00 (Migrated from github.com)

Problem

Sites with a persistent object cache (Redis/Memcached) should benefit from it, while sites without one still work via the database transient store. The caching layer should not assume a backend.

Acceptance criteria

  • Caching works correctly whether or not a persistent object cache is present.
  • On sites with an external object cache, transients are not needlessly duplicated in the options table.
  • Cache group naming is consistent and documented.
  • No behavioural difference in served content between the two backends.

Notes

Transients automatically route to the object cache when one is installed; verify keys are grouped sensibly.

## Problem Sites with a persistent object cache (Redis/Memcached) should benefit from it, while sites without one still work via the database transient store. The caching layer should not assume a backend. ## Acceptance criteria - [ ] Caching works correctly whether or not a persistent object cache is present. - [ ] On sites with an external object cache, transients are not needlessly duplicated in the options table. - [ ] Cache group naming is consistent and documented. - [ ] No behavioural difference in served content between the two backends. ## Notes Transients automatically route to the object cache when one is installed; verify keys are grouped sensibly.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Directorium/Ordo#32
No description provided.