Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
aggregator.module
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
3 Feb 2015 at 03:21 UTC
Updated:
29 Sep 2015 at 04:01 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
ParisLiakos commentedi was able to reproduce it, but i dont get why testbot doesnt fail...there are certainly tests for this :/
Comment #2
ParisLiakos commentedah, i see..i get this right after enabling the module..if i clear cache, it works..its probably why testbot doesnt have those fails
Comment #3
dawehnerThis is one way to solve it.
Comment #4
dawehnerAnd this time with a test.
Comment #5
dawehner.. this time with a proper patch.
Comment #7
ParisLiakos commentedthanks for the patch!
nit: typo, probably discoveries
Comment #8
dawehnerHAHA, this looked super weird, but I could not figure out why.
Comment #9
larowlanAssuming green.
Should we be documenting somewhere that there is some black magic in plugin.manager.{x} naming that results in the plugin cache being cleared on module install?
Comment #10
alexpottWe can do this without the service name change (and therefore API change) and the magic. Just tag the service with
Comment #11
alexpottLike so.
Comment #12
ParisLiakos commentedgood to know where the magic is hidden :P Thanks!
Comment #14
catchCommitted/pushed to 8.0.x, thanks!