Now that aggregator.module is no longer broken beyond all recognition (thanks guys!), the page split is now easy!
| Comment | File | Size | Author |
|---|---|---|---|
| aggregator_11.patch | 63.02 KB | Crell |
Now that aggregator.module is no longer broken beyond all recognition (thanks guys!), the page split is now easy!
| Comment | File | Size | Author |
|---|---|---|---|
| aggregator_11.patch | 63.02 KB | Crell |
Comments
Comment #1
fgmNot sure whether these come from the patch, but there seem to be some issues with aggregator menus. Using paths:
aggregatorshows a list of posts with the title "news aggregator" and breadcrumbs (bc) limited to "Home", no local tasksaggregator/categoriesshows a list of categories and their most recent posts, with bc "home > news aggregator"aggregator/categories/<cid>shows a visually identical list of posts with the same title as in (1), the same bc as in (2), and local tasks, but no title or mention in the bc about the current categoryThis seems inconsistent: it seems that
Otherwise we're missing consistency.
Again, this might not be due to the patch, but a preexisting error that should be fixed, possibly by this patch since it redistributes content.
Comment #2
Crell commentedfgm: Can you check without the patch and see if those problems are there before hand? If so, I'd rather apply the patch now and fix them later as the split patches are fragile, since they touch so much. As long as it's not introducing any new bugs, it should be fine.
Comment #3
eagle15 commentedI've verified (with a clean checkout) that the aggregator issues mentioned exist before this patch.
Comment #4
dvessel commentedOnly point 3 is different from 5.x. Doesn't mean it's correct but if anyone wants to change that, lets leave that to another issue.
Works without problems.
Comment #5
dries commentedI've committed this patch but we probably want to file an issue for the remaining issues.
Comment #6
fgmI created a separate issue at http://drupal.org/node/173188 for the menu / breadcrumbs consistency problem, so this patch can rest in peace, since it appears to be a separate problem.
Comment #7
(not verified) commented