Timeline for Clearing local tasks cache
Current License: CC BY-SA 3.0
12 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Sep 13, 2016 at 13:02 | comment | added | Pierre Buyle |
With the added code, the answer make sense. Adding the entity type cache_tags to the derivatives clear the needed cache on entity insertion/delete.
|
|
Sep 13, 2016 at 12:41 | history | bounty ended | Pierre Buyle | ||
Sep 12, 2016 at 1:00 | vote | accept | Pierre Buyle | ||
Sep 10, 2016 at 2:16 | comment | added | LionsAd | I reported the core bug here: drupal.org/node/2797745 Could you accept the answer or is there still something missing? | |
Sep 9, 2016 at 11:42 | comment | added | LionsAd | I edited my answer to provide the final solution, still need to file a core issue though. | |
Sep 9, 2016 at 11:41 | history | edited | LionsAd | CC BY-SA 3.0 |
Added better solution for list cache tags.
|
Sep 8, 2016 at 22:48 | history | edited | LionsAd | CC BY-SA 3.0 |
added 730 characters in body
|
Sep 8, 2016 at 22:37 | comment | added | LionsAd | It is a core bug and a very nasty one for that. I can reproduce it with normal core search pages starting from the third search page. I get the curious issue that one one page I have 2 tabs on the new page I have three tabs. Clearly cached by page_cache and dynamic_page_cache. | |
Sep 8, 2016 at 22:13 | comment | added | LionsAd | Hmmm, maybe you need to add "class: \Drupal\Core\Menu\LocalTaskDefault" to your *.task.yml? | |
Sep 8, 2016 at 21:56 | comment | added | LionsAd | The core bug / limitation here is that you have no way to tell core the cacheability metadata that you need. It should really be associated with the LocalTask item itself. e.g. you want to show the list and entity cache tags when displaying a list of entities. I am just unclear how e.g. search pages get around that issue (if they do). And yes it might well be that the discovery cache needs to be cleared as well. | |
Sep 8, 2016 at 20:45 | comment | added | Pierre Buyle | I don't think that would be a core bug. Core does not known about my custom deriver. It cannot known it has to clear/cache something related to local tasks when a custom config entity is inserted/delete. I don't have to test ATM, but I'm pretty sure this is not a render cache issue. My current assumption is that multiple cache are involved, the render cache may be one but I guess plugin and menu cache are involved. | |
Sep 8, 2016 at 19:30 | history | answered | LionsAd | CC BY-SA 3.0 |