"Exclude entities from persistent caches" option is misleading

Created on 30 September 2022, over 1 year ago
Updated 9 February 2023, over 1 year ago

Problem/Motivation

The "Exclude entities from persistent caches" option is misleading. The description in the UI: "This will ensure unencrypted data will not be exposed in the cache, but will have a negative impact on performance."

What this option actually does is exclude ALL entities of an entity type that has field encryption enabled, regardless of whether or not they actually have a field that is encrypted.

For example, if you have 10 content types, like Article, Page, Landing Page, Blog Post, and so on, and only one has a field with field encryption enabled, then using the "Excluding entities from persistent caches" will remove all nodes of all content types from the cache.

Proposed resolution

For now, make the description clearer in the UI. But long term, it would be great if only entity bundles that had a field with field encryption enabled would be excluded from caching.

πŸ› Bug report
Status

Fixed

Version

3.1

Component

Documentation

Created by

πŸ‡―πŸ‡΅Japan ptmkenny

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.

Production build 0.69.0 2024