Problem/Motivation

The last sentence in the text information at the top of the admin/config/services/aggregator page still reads "For each feed, the latest items block may be enabled at the blocks administration page." This was correct for D7, but for D8, you place a 'Aggregator Feed' block and select which feed it is to show. I found this confusing, and I almost filed an issue saying that the latest items blocks weren't being created. This should be corrected.

Steps to reproduce

Enable aggregator.
Go to admin/config/services/aggregator.
Read the help text.

Proposed resolution

Change
For each feed, the latest items block may be enabled at the blocks administration page.
to
For each feed, the Aggregator feed block may be enabled at the block layout page.

Remaining tasks

User interface changes

Before

After

API changes

Data model changes

Release notes snippet

CommentFileSizeAuthor
#17 2610520-17.patch1.71 KBquietone
#17 After.png26.23 KBquietone
#17 Before.png26.7 KBquietone
#8 documentation_wrong_aggregator-2610520-8.patch1.77 KBhansfn
#6 interdiff-2610520-3-6.txt1.67 KBsnehi
#6 documentation_wrong_aggregator-2610520-6.patch1.67 KBsnehi
#3 documentation_wrong_aggregator-2610520.patch1.65 KBmisc

Comments

Ben Coleman created an issue. See original summary.

misc’s picture

misc commented
Assigned: Unassigned » misc
Priority: Normal » Minor

I will have a patch for this tomorrow, so assigning to me.

misc’s picture

misc commented
Assigned: misc » Unassigned
Status: Active » Needs review
StatusFileSize
new documentation_wrong_aggregator-2610520.patch1.65 KB

Proposed path attached.

dcam’s picture

dcam commented
Status: Needs review » Needs work
Issue tags: +Documentation

Tagging.

I can't do a proper review of the patch at the moment, but I do think that the wording sounds strange. I was thinking something more along the lines of "To display a feed, enable an aggregator feed block at the blocks administration page", with the same HTML added of course.

snehi’s picture

snehi commented
Assigned: Unassigned » snehi
snehi’s picture

snehi commented
Status: Needs work » Needs review
StatusFileSize
new documentation_wrong_aggregator-2610520-6.patch1.67 KB
new interdiff-2610520-3-6.txt1.67 KB

Changed as suggested.

snehi’s picture

snehi commented
Assigned: snehi » Unassigned
hansfn’s picture

hansfn commented
Version: 8.0.0-rc3 » 8.1.x-dev
Priority: Minor » Normal
StatusFileSize
new documentation_wrong_aggregator-2610520-8.patch1.77 KB

This documentation bug has caused many problems for my students, so I decided to update the patch for 8.1.x hoping it will be included.

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

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should 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.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should 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.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should 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.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should 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.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should 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.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.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: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should 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: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

quietone commented
Version: 9.2.x-dev » 9.4.x-dev
Issue summary: View changes
Issue tags: +Bug Smash Initiative
StatusFileSize
new Before.png26.7 KB
new After.png26.23 KB
new 2610520-17.patch1.71 KB

Update IS and updated the patch. No interdiff because this is small.

antoniya’s picture

antoniya commented
Status: Needs review » Reviewed & tested by the community

We discussed this at #3253969: Drupal Usability Meeting 2021-12-17 and agreed that this is a very valid request.

As mentioned in the meeting, one could argue about rephrasing the passive 'may be enabled', but none of the meeting attendees felt really bothered by the current suggestion. I'll mark this as RTBC as it is a rather minor change and has been reviewed by a few people already.

  • catch committed 98a9ec7 on 10.0.x 
    Issue #2610520 by quietone, snehi, MiSc, hansfn, Ben Coleman, Antoniya:...
  • catch committed 1b1d457 on 9.4.x
    Issue #2610520 by quietone, snehi, MiSc, hansfn, Ben Coleman, Antoniya:...
catch’s picture

catch
he/him
Primary language English
commented
Status: Reviewed & tested by the community » Fixed

Committed/pushed to 10.0.x and cherry-picked to 9.4.x, thanks!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.