Closed (fixed)
Project:
Drupal core
Version:
7.x-dev
Component:
aggregator.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 Jun 2008 at 15:49 UTC
Updated:
22 Aug 2008 at 20:15 UTC
Jump to comment: Most recent file
Comments
Comment #1
pwolanin commentedso far I can't reproduce on 7.x, so this may be a 6.x bug.
Comment #2
pwolanin commentedNow can reproduce - an extra step is needed:
Before deleting the feed enable the block specific to that feed.
Once the feed is deleted this notice appears but then the block does not appear in the blocks UI at admin/build/block, but the notice appears on every page.
The error is in function aggregator_block() - the cause may be that the block corresponding to that feed is not deleted from the {blocks} table.
If you visit the admin/build/block page then the blocks are rebuilt and the notice goes away.
Comment #3
pwolanin commentedBasically the same thing happens if you delete a category which has an enabled block:
Comment #4
pwolanin commentedThe code from hook_block shows how the block deltas are built:
Comment #5
pwolanin commentedPatch attached for 7.x. Initial tests suggests that it resolves the bug. The 6.x backport should be simple- just change the spacing of the concat.
Comment #6
mustafau commentedI believe this should be fixed using block.module function
_block_rehash(). I working patch is attached.Comment #7
pwolanin commentedby convention the "_" means that this is not really a public function. Basically block module is broken is as much as it does not offer a readily available public function for this purpose. We can use it for D6, but perhaps we should reform block module a little for D7.
Comment #8
dries commentedPersonally, I think pwolanin's approach is slightly cleaner (direct SQL query instead of calling an internal function).
Comment #9
mustafau commentedRe-roll of the patch from #5.
Does this need some tests?
Comment #10
dries commentedI think this one can go in without a test. I've committed this to CVS HEAD and DRUPAL-6. Thanks.
Comment #11
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.