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

Command icon 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:

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

huzooka created an issue. See original summary.

huzooka’s picture

huzooka’s picture

Assigned: huzooka » Unassigned
Status: Active » Needs review

Status: Needs review » Needs work

The last submitted patch, 4: meta_entity-target_entity_cache_tags-3422612-4.diff, failed testing. View results

huzooka’s picture

Adding the same patch as in 4, but with suppressed deprecation warnings in MetaEntityAccessTest.

huzooka’s picture

Status: Needs work » Needs review

pfrenssen made their first commit to this issue’s fork.

pfrenssen’s picture

Created followup to address the deprecation warning: #3438861: Deprecation warning in MetaEntityAccessTest.

  • pfrenssen committed ebe9b2de on 8.x-1.x authored by huzooka
    Issue #3422612 by huzooka, pfrenssen: Target entity tags should be...
pfrenssen’s picture

Status: Needs review » Fixed

Thanks for the contribution, nice work!

Status: Fixed » Closed (fixed)

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