The "Promoted to front page" checkbox doesn't do anything if the /node front page listing isn't used

Created on 2 December 2010, over 14 years ago
Updated 20 March 2025, 14 days ago

Updated from #89.

Problem/Motivation

The "Promoted to front page" checkbox is primarily only useful if people are using the river-of-news style front page display. As soon as the default front page is overridden, this label makes no sense, and the label either needs to change, or the checkbox should be removed.

Proposed resolution(s)

There are a few proposed solutions for this problem. The one with the most consensus (and work done) at this point is solution #1.

1. Change the wording from "Promoted to Front Page" to something else. There is a patch at #27 to change all occurrences of the wording to "Promoted". Another suggestion is to call this "Featured content" (see #63, #65, #76).

This is the approach in the current patch, which changes the text "Promoted to front page" to "Promote".

2. Make the wording configurable per site (possibly also by content type). Likely by making it a configurable field. Or, by changing the title and hiding it when there's no title (field label)

3. Promoted to front page button should only exist if the administrator installs Drupal with the standard (not minimal) install.

4. Remove the "promoted" checkbox altogether.
This has been mentioned a few times and gained support after #51 with first patch for this in #58 and rerolled latest in #85.

5. Make the "promoted to front page" checkbox either automatically hidden in the user interface (or automatically renamed) only when it doesn't apply (#23, #51).
For example, the Node module would do that by default, but the Views module could alter the form and show it as "Promoted to front page" in the case where (a) the front page is using a view, and (b) the view has filters which suggest that the node will actually appear on the front page if the box is checked (e.g., it uses a "promoted" filter). An advantage of this approach is that it should automatically do the "right" thing for a good number of use cases, but a disadvantage is that this won't be foolproof and would involve some ugly/complicated code.

Remaining tasks

Solution #1
- Decide on a term other than "Promoted". Current popular suggestion is to call this "Featured content".
- Fix the patch from #27 or #47.
- Add description to clarify the flag (see #21).

Solution #4
- Fix the patch from #85.

Other
- Determine if there is consensus for pursing another solution.
- Create a follow-up issue for other solutions.

Related Issues

#1201592: Front page settings cleanup โ†’
#1201580: Move Front page & Error page settings out of "Site information" and into their own respective config pages. โ†’
#2029199: Rename the 'Frontpage' view to 'Latest content' or 'Featured content'. โ†’

Original report by jenlampton

I would love to see the name of this flag changed. Most Drupal sites out there do not use the default front page, and it would be easier to reuse this flag for another purpose if the label were not so specific.

๐Ÿ› Bug report
Status

Needs work

Version

11.0 ๐Ÿ”ฅ

Component

node system

Created by

๐Ÿ‡บ๐Ÿ‡ธUnited States jenlampton

Live updates comments and jobs are added and updated live.
  • Usability

    Makes Drupal easier to use. Preferred over UX, D7UX, etc.

  • Needs reroll

    The patch will have to be re-rolled with new suggestions/changes described in the comments in the issue.

  • Needs issue summary update

    Issue summaries save everyone time if they are kept up-to-date. See Update issue summary task instructions.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • ๐Ÿ‡ฆ๐Ÿ‡บAustralia acbramley

    In Drupal 11 we can easily disable the Promoted field via manage form display and we have a somewhat hidden API with base field overrides to change the label per content type. I wonder if this is enough to solve most issues people have here. Perhaps we need an issue to expose base field overrides somehow in the UI.

    However, if we want to move forward here we need a reroll onto an MR and an updated IS and title to reflect the changes. Much of the changes in the last patch no longer apply as well since things like actions have moved to contrib.

    Given the other tools mentioned above, I'd also say this probably isn't Major? And is it even a bug?

  • ๐Ÿ‡จ๐Ÿ‡ฆCanada xmacinfo Canada

    Drupal 11 we can easily disable the Promoted field via manage form display and we have a somewhat hidden API with base field overrides to change the label per content type.

    Goal changed over time

    The goal of this ticket has changed over time. Now we only need to change the default behaviour, which would be to hide the โ€œPromoted to front pageโ€ flag (and most probably hide the "Stickyโ€ flag as well).

    We need backward compatibility for existing sites and for developers who want to enable one of those flags. And for new users, make the defaults less complex.

    Issue title and summary

    Before changing the issue title and summary, let's get more comments.

  • ๐Ÿ‡จ๐Ÿ‡ญSwitzerland berdir Switzerland

    Which happens to make it a duplicate of the *even older #29338: Hide Promoted/Sticky fields by default in Form display โ†’ , lets consolidate and close this in favor of that?

  • ๐Ÿ‡ฆ๐Ÿ‡บAustralia acbramley

    Happy with that :)

Production build 0.71.5 2024