Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
action.module
Priority:
Normal
Category:
Task
Assigned:
Reporter:
Created:
10 Jul 2013 at 18:07 UTC
Updated:
29 Jul 2014 at 22:38 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
tim.plunkettThanks for opening the issue!
Comment #3
tim.plunkettApparently it hates caching (wasn't cached in HEAD).
Comment #4
dawehnerWas there a special reason it didn't had a cache before?
Comment #5
tim.plunkettNo idea. Let's see what breaks.
Comment #6
tim.plunkettComment #8
berdirGetting a "The plugin (node_delete_action) did not specify an instance class." during the installation. I guess it's trying to do something with the configuration before the caches are cleared?
We might need a generic solution to clear plugin caches when a new module is installed? As this could happen with stuff too?
I know that I had to add a manual cache clear where I'm looking for now plugins in a hook_modules_installed() to create default configuration for them.
Comment #9
tim.plunkettI saw the same thing.
I don't know why we don't have that problem for views stuff as well.
I hate to think it might be an alphabetical thing...?
Is it worth having tagged plugin managers?
I'm not sure...
Comment #10
aks22 commented#5: action-2039021-5.patch queued for re-testing.
Comment #12
tim.plunkettOpened #2155635: Allow plugin managers to opt in to cache clear during module install for #8/#9.
Comment #13
xanoPicking this up.
Comment #14
xanoRe-roll. No changes. PHPUnit passes.
Comment #16
xanoComment #17
berdir16: drupal_2039021_16.patch queued for re-testing.
Comment #19
berdirRe-roll, patch applied fine with git apply -3, then updated the cache bin to discovery.
Comment #20
dawehnerWe don't need to initialize the discovery here. The parent cares about that and you never know, maybe at some point someone comes up with derivatives for it.
Let's not alter it twice.
Comment #21
berdirThanks!
Comment #22
dawehnerThank you!
Comment #23
catchCommitted/pushed to 8.x, thanks!