Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Processors are currently called without checking their module weight. The aggregator_processors array is built with module_invoke() though and thus processor keys _should_ be in the right order. Need to double check.
$processors = variable_get('aggregator_processors', array('aggregator'));
foreach ($processors as $processor) {
module_invoke($processor, 'aggregator_process', $feed);
}| Comment | File | Size | Author |
|---|---|---|---|
| #3 | drupal-aggregator-processor-order-414160-3.patch | 2.91 KB | twistor |
Comments
Comment #1
bdu CreditAttribution: bdu commentedA drupal newbie trying to help.
The mentioned code is split and the variable_get is moved to a generic function.
aggregator.admin.inc:
Assuming th form does not change the order, you would say this is in the correct order as long as no
draconic things happen like a change of weight in a module. As a newbie I have no idea if that is even possible.
Comment #2
ParisLiakos CreditAttribution: ParisLiakos commentedComment #3
twistor CreditAttribution: twistor commentedThis is the first thing that pops into my head. It needs work, but leaving at needs review to get feedback.
Comment #15
SpokjeThe
aggregatormodule has been removed from Core in10.0.x-devand now lives on as a contrib module.Issues in the Core queue about the
aggregatormodule, like this one, have been moved to the contrib module queue.Comment #16
larowlanAll of that code is long gone