This goes in pair with #1066830: Change /node path to /latest and allow admins to disable. and #1210366: Per-bundle node listing pages, blocks, feeds..

I realize that novice users coming to the views admin interface can easily spot a view labeled 'Frontpage' and they surely grasp what it's meant for, but once people change either their default home page setting or the path of that view, then it simply makes no sense to still call it 'Frontpage' and can in fact cause confusion (#987242: The "Promoted to front page" checkbox doesn't do anything if the /node front page listing isn't used).

In short: It makes a lot more sense to have a 'Latest content' or 'Featured content' view and set it as the site's home page.

CommentFileSizeAuthor
#26 interdiff-23-26.txt3.41 KBtadityar
#26 D8-core-rename-frontpage-view-to-promoted-2029199-26.patch28.82 KBtadityar
#23 D8-core-rename-frontpage-view-to-promoted-2029199-23.patch43.18 KBjustinchev
#21 D8-core-rename-frontpage-view-to-promoted-2029199-21.patch39.83 KBjustinchev
#19 D8-core-rename-frontpage-view-to-promoted-2029199-19.patch39.96 KBjustinchev
#14 D8-core-rename-frontpage-view-to-promoted-2029199-14.patch42.57 KBjustinchev
#13 D8-core-rename-frontpage-view-to-promoted-2029199-13.patch44.18 KBjustinchev
#8 D8-core-rename-frontpage-view-to-promoted-2029199-8.patch44.17 KBjustinchev
#7 D8-core-rename-frontpage-view-to-promoted-2029199-7.patch44.17 KBjustinchev
#5 D8-core-rename-frontpage-view-to-promoted-2029199-5.patch44.17 KBjustinchev
#5 content-create.png112.26 KBjustinchev
#5 edit-content-type.png129.46 KBjustinchev
#5 edit-view1.png197.15 KBjustinchev
#5 Views-list.png197.87 KBjustinchev
#5 welcome-screen.png70.61 KBjustinchev

Comments

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented

...also, please see my proposal in #1201592-57: Front page settings cleanup

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented
Title: Rename the 'Frontpage' view to 'Latest content'. » Rename the 'Frontpage' view to 'Latest content' or 'Featured content'.

...a better alternative to "Latest content" would be "Featured content".

klonos’s picture

klonos
he/him
Primary language English
Location 90% Melbourne, Australia - 10% Larissa, Greece
commented
Issue summary: View changes

...adding #987242

dawehner’s picture

dawehner
Primary language German
commented
Issue tags: +VDC

Noone will find issues, especially if they are not tagged as VDC.

dawehner’s picture

dawehner
Primary language German
commented
Issue summary: View changes

...adding alternative 'featured' instead of 'latest'.

justinchev’s picture

justinchev commented
Issue summary: View changes

In the Beta 1 release I see that this sort of content is now referred to as 'Promoted'. Since that is what it is now called I suggest that we use plain 'Promoted' for the view name instead of 'Frontpage' (as it's currently set).

This will also need to be set in a couple of other places. An example is when editing the view and choosing the type of content to show - it's still using the label 'Promoted to front page status'.

* edit: I started going through the code to see what would need to be changed out. Found several of the 'UI' bits of text as seen from the admin pages, but having done a search for 'frontpage' through all files I see that there are quite a few uses of it within the site code in a view machine name/function name type of scenarios. In an ideal world all references to the Frontpage view should be changed.

Is this something to progress or something which could have an impact on things such as contrib mods?

justinchev’s picture

justinchev commented
Status: Active » Needs review
StatusFileSize
new welcome-screen.png70.61 KB
new Views-list.png197.87 KB
new edit-view1.png197.15 KB
new edit-content-type.png129.46 KB
new content-create.png112.26 KB
new D8-core-rename-frontpage-view-to-promoted-2029199-5.patch44.17 KB

I went ahead and changed all instances I could find where it should be referred to as 'Promoted' rather than 'Frontpage'. This mainly involved UI labelling and descriptions as well as renaming the 'frontpage' view along with it's the machine name and test references.

I did leave references to 'Front page' when it was actually referring to the actual Frontpage.

Below are some screenshots of some of the UI changes...

Status: Needs review » Needs work

The last submitted patch, 5: D8-core-rename-frontpage-view-to-promoted-2029199-5.patch, failed testing.

justinchev’s picture

justinchev commented
Version: 8.0.x-dev » 8.0.0-beta1
StatusFileSize
new D8-core-rename-frontpage-view-to-promoted-2029199-7.patch44.17 KB

Ahhh forgot to change the version this patch goes against...

justinchev’s picture

justinchev commented
Status: Needs work » Needs review
StatusFileSize
new D8-core-rename-frontpage-view-to-promoted-2029199-8.patch44.17 KB

I'm really making a mess of this... once more with status set back to 'needs review' :s

Status: Needs review » Needs work

The last submitted patch, 8: D8-core-rename-frontpage-view-to-promoted-2029199-8.patch, failed testing.

Status: Needs work » Needs review

justinchev queued 8: D8-core-rename-frontpage-view-to-promoted-2029199-8.patch for re-testing.

The last submitted patch, 7: D8-core-rename-frontpage-view-to-promoted-2029199-7.patch, failed testing.

Status: Needs review » Needs work

The last submitted patch, 8: D8-core-rename-frontpage-view-to-promoted-2029199-8.patch, failed testing.

justinchev’s picture

justinchev commented
Status: Needs work » Needs review
StatusFileSize
new D8-core-rename-frontpage-view-to-promoted-2029199-13.patch44.18 KB

And again, hopefully with a fix for the one thing failing testing...

justinchev’s picture

justinchev commented
Version: 8.0.0-beta1 » 8.0.0-beta2
StatusFileSize
new D8-core-rename-frontpage-view-to-promoted-2029199-14.patch42.57 KB

I've updated the patch so that it applies successfully to Drupal 8.0.0 beta 2.

Status: Needs review » Needs work

The last submitted patch, 14: D8-core-rename-frontpage-view-to-promoted-2029199-14.patch, failed testing.

Status: Needs work » Needs review

justinchev queued 14: D8-core-rename-frontpage-view-to-promoted-2029199-14.patch for re-testing.

Status: Needs review » Needs work

The last submitted patch, 14: D8-core-rename-frontpage-view-to-promoted-2029199-14.patch, failed testing.

justinchev’s picture

justinchev commented

Seems the latest patch is failing on one of the Language tests ('NodeLanguageTest.php').

I don't really understand why but it seems the test is trying to override the config for the Promoted view to test language filters. What I don't understand is that it appears to be targeting a view named promoted ( $config = \Drupal::config('views.view.promoted');)

This confuses me as the patch I'm providing is changing the view from it's current name of 'frontpage' to 'promoted' so wouldn't have thought there would be a test targeting it.

My dev knowledge is fairly limited so I could be completely missing something obvious. Any ideas as I'd like to get this patch passing again?

justinchev’s picture

justinchev commented
Version: 8.0.0-beta2 » 8.0.0-beta3
Status: Needs work » Needs review
StatusFileSize
new D8-core-rename-frontpage-view-to-promoted-2029199-19.patch39.96 KB

Patch updated so it applies to Drupal 8-beta 3.

Status: Needs review » Needs work

The last submitted patch, 19: D8-core-rename-frontpage-view-to-promoted-2029199-19.patch, failed testing.

justinchev’s picture

justinchev commented
Status: Needs work » Needs review
StatusFileSize
new D8-core-rename-frontpage-view-to-promoted-2029199-21.patch39.83 KB

Patch rerolled to pass tests - it should apply to Drupal 8-beta 3.

See screenshots in #5 for some of the changes.

Status: Needs review » Needs work

The last submitted patch, 21: D8-core-rename-frontpage-view-to-promoted-2029199-21.patch, failed testing.

justinchev’s picture

justinchev commented
Status: Needs work » Needs review
StatusFileSize
new D8-core-rename-frontpage-view-to-promoted-2029199-23.patch43.18 KB

Patch rerolled to pass tests - it should apply to Drupal 8-beta 3.

See screenshots in #5 for some of the changes.

Status: Needs review » Needs work

The last submitted patch, 23: D8-core-rename-frontpage-view-to-promoted-2029199-23.patch, failed testing.

dawehner’s picture

dawehner
Primary language German
commented
Version: 8.0.0-beta3 » 8.0.x-dev

Let's use the right version number here.

tadityar’s picture

tadityar commented
Status: Needs work » Needs review
StatusFileSize
new D8-core-rename-frontpage-view-to-promoted-2029199-26.patch28.82 KB
new interdiff-23-26.txt3.41 KB

re-rolled, fixed some capitalisation and used -C instead the usual diff.

Status: Needs review » Needs work

The last submitted patch, 26: D8-core-rename-frontpage-view-to-promoted-2029199-26.patch, failed testing.

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

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

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

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

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

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.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.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.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.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

lendude’s picture

lendude
Primary language Dutch
Location Amsterdam
commented

With the coming of Drupal CMS we should just nuke this View I recon. Along with some other Views that ship with core.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.