Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
If meta entity type is configured to not auto-create meta entities (so e.g. they are created only if needed), then the target entity might already have some cached data when the meta is created. In my use case, we render the canonical page of the target entity based on what we store in the meta entity (if it exist).
Proposed resolution
Invalidate cache tags of the target entity even if the meta entity is new.
Remaining tasks
User interface changes
API changes
Data model changes
Comment | File | Size | Author |
---|---|---|---|
#7 | meta_entity-target_entity_cache_tags-3422612-7.diff | 4.94 KB | huzooka |
|
Issue fork meta_entity-3422612
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
huzookaAdding related issues
Comment #4
huzookaUploading patch.
Comment #5
huzookaComment #7
huzookaAdding the same patch as in 4, but with suppressed deprecation warnings in
MetaEntityAccessTest
.Comment #8
huzookaComment #10
pfrenssenCreated followup to address the deprecation warning: #3438861: Deprecation warning in MetaEntityAccessTest.
Comment #12
pfrenssenThanks for the contribution, nice work!