The aggregator module as a core extension of Drupal still hides much of its functionality behind custom code. This severely limits its usefullness and appears to be a situation that could be easily remedied by converting feed output to a view. This would follow the standard Drupal plan of converting module output to views for flexibility.

This would makes it easy for web developers to change the aggregator page title (without coding prowess), alter the format and size of images, or customize additional fields that are added via the manage fields page.

It would also help if aggregator's output was added as a custom content type, to be more fully exposed and customizable for non-coders.

CommentFileSizeAuthor
#31 2680527-31.patch10.12 KBdcam
#27 2680527-27.patch10.12 KBdcam
#25 2680527-25.patch8.86 KBdcam
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

zoon_unit created an issue. See original summary.

cilefen’s picture

Status: Active » Postponed (maintainer needs more info)

Can you please rewrite the issue summary into an single issue that is solvable?

zoon_unit’s picture

Not sure what you want me to do. The single biggest issue is lack of a Views definition for Aggregator default output, making it difficult or impossible to make changes without "hacking" Drupal.

cilefen’s picture

In the spirit of helping you out with your needs, I am trying to channel this toward a solvable goal, or it may be ignored and you may be more frustrated. You may want to convert this issue to the "Plan" category, and lay out a series of tactical goals, which can later be turned into actionable sub-issues.

zoon_unit’s picture

cilefen, thanks.

The main issue is a lack of a view for customizing feed output. After more research, I found that someone filed an open issue proposing changing the output to a view four years ago, so I guess this request is redundant. :-)

I don't want to make my issue non-specific on purpose, but there are several other problems with aggregator that makes it appear as if work has stopped on it. For instance, the views that ARE included (aggregator/sources) are not fully functional. (I filed a separate issue for that one)

Also, the help text at "/admin/config/services/aggregator" refers to the "latest items" block, but that block is non-existent.

For my own purposes, I've realized that I can "fix" the existing view, and make my own "feeds" view to solve my immediate concerns, but since aggregator is included in Drupal core, I would think the developers would want to make it functional out of the box, hence the issue. Feel free to close this issue if you consider it non-standard.

cilefen’s picture

@zoon_unit The issue, as is, is a feature request. Can it be fixed with a patch? If so, should the title could be "Add a view for customizing feed output", clean up the issue summary to relate to that specifically, and we're good.

zoon_unit’s picture

Title: Aggregator output is not customizable » Convert aggregator feed output to a view
Category: Feature request » Plan
Issue summary: View changes
Priority: Major » Normal
zoon_unit’s picture

@cilefen, I've followed your suggestion. :-)

One last thing: I am not a coder, so I'm not set up to issue patches, but I "could" export the corrected "aggregator/sources" view and the "feeds" view, after I've fixed them, and post them here, if you think that would be helpful . . .

cilefen’s picture

Version: 8.0.5 » 8.2.x-dev
Category: Plan » Task
Status: Postponed (maintainer needs more info) » Active

It would help.

cilefen’s picture

Please attach them - do not paste them. You can refer to them in the issue summary.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Project: Drupal core » Aggregator
Version: 9.4.x-dev » 1.x-dev
Component: aggregator.module » Code

The aggregator module has been removed from Core in 10.0.x-dev and now lives on as a contrib module. Issues in the Core queue about the aggregator module, like this one, have been moved to the contrib module queue.

larowlan’s picture

Title: Convert aggregator feed output to a view » Use views to output aggregator items
Category: Task » Feature request
Issue tags: +Aggregator 2.x
larowlan’s picture

Version: 1.x-dev » 2.x-dev
Issue tags: -Aggregator 2.x
dcam’s picture

Category: Feature request » Task
Status: Active » Needs review
FileSize
8.86 KB

Let's see what breaks.

I made a couple of bonus edits to the feed template file. I noticed that they were needed while I was trying to understand how to make the feed title not be rendered.

Status: Needs review » Needs work

The last submitted patch, 25: 2680527-25.patch, failed testing. View results

dcam’s picture

FileSize
10.12 KB

The failures were due to post-migration entity counts that needed to be updated since I added three new entities.

dcam’s picture

Status: Needs work » Needs review
dcam’s picture

Status: Needs review » Active

I'm setting this back to active because there's more work to be done on it. An upgrade path needs to be written. We need to decide whether the Items component of the Feed view should be deprecated. I'd say "yes." I looked at what the Taxonomy module does for Terms to try and find a best practice. It doesn't appear to have a component for displaying referenced entities, deferring that responsibility to Views. Feeds and their Items are a slightly different scenario, but I'd still prefer to do all query building with Views.

larowlan’s picture

Exciting to see this moving 🎉

dcam’s picture

FileSize
10.12 KB

Rerolled 27.