Problem/Motivation

I wanted to subscribe to an event after a tag was invalidated

Proposed resolution

add in an event dispatch before and after tags would be invalidated.

Remaining tasks

  • Idea needs to be sanity checked, I am relatively new to Drupal and not sure if this is the best way to achieve this.
  • reviews needed
  • tests to be written or run
  • documentation to be written

User interface changes

none

API changes

Added two new event names
CacheEvents::BEFORE_TAGS_INVALIDATED
CacheEvents::AFTER_TAGS_INVALIDATED

Data model changes

none

Patch to follow

CommentFileSizeAuthor
#8 Event-before-and-after-tags-invalidated-2829839.patch6.83 KBGravypower
#5 Event-before-and-after-tags-invalidated-2829839.patch2.96 KBGravypower
#2 Event-before-and-after-tags-invalidated-2829839.patch3.01 KBGravypower
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Gravypower created an issue. See original summary.

Gravypower’s picture

Gravypower CreditAttribution: Gravypower commented
FileSize
Event-before-and-after-tags-invalidated-2829839.patch3.01 KB
cilefen’s picture

cilefen CreditAttribution: cilefen commented
Status: Active » Needs review

Status: Needs review » Needs work

The last submitted patch, 2: Event-before-and-after-tags-invalidated-2829839.patch, failed testing.

Gravypower’s picture

Gravypower CreditAttribution: Gravypower commented
FileSize
Event-before-and-after-tags-invalidated-2829839.patch2.96 KB

Created patch correctly this time (hopefully)

cilefen’s picture

cilefen CreditAttribution: cilefen commented
Title: Event before and after tags invalidated » Add an event before and after tags invalidated
Status: Needs work » Needs review

Status: Needs review » Needs work

The last submitted patch, 5: Event-before-and-after-tags-invalidated-2829839.patch, failed testing.

Gravypower’s picture

Gravypower CreditAttribution: Gravypower commented
FileSize
Event-before-and-after-tags-invalidated-2829839.patch6.83 KB

Updated Unit Tests as they did not expect CacheTagsInvalidator to have a constructor argument.

Gravypower’s picture

Gravypower CreditAttribution: Gravypower commented
Status: Needs work » Needs review

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Berdir’s picture

Berdir
Primary language German
Location Switzerland
CreditAttribution: Berdir at MD Systems GmbH commented
Status: Needs review » Postponed (maintainer needs more info)

We already support tagged services, cache_tags.invalidator.checksum uses that for example. There is no explicit before/after, but there is support for priority, so if you want to be the first/last, you can set a very high/low priority.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

smustgrave CreditAttribution: smustgrave at Mobomo commented
Status: Postponed (maintainer needs more info) » Closed (outdated)

If still a valid feature request please reopen addressing #11.