starshot-prototype icon indicating copy to clipboard operation
starshot-prototype copied to clipboard

Hide "Promotion options" node fields where they're not used

Open TravisCarden opened this issue 1 year ago • 5 comments

Every node edit form in Drupal has a "Promotion options" fieldset containing "Promoted to front page" and "Sticky at top of lists" fields, but they don't automatically do anything. And they don't have help text explaining what effect they do have even when they are used. We're using them on "Blog post" but not elsewhere. We should hide them any time they're unused and consider adding help text explaining the effect they'll have when where are used.

TravisCarden avatar Jul 11 '24 15:07 TravisCarden

I'm okay with hiding these from the Page and Event content types for now, since they are, as you point out, not used.

phenaproxima avatar Jul 16 '24 16:07 phenaproxima

"Promoted to front page" and "Sticky at top of lists" fields are actually utilized in our Frontpage view configuration (/admin/structure/views/view/frontpage). Specifically:

  • Filter criteria: We have "Content: Promoted to front page (= Yes)" set, which means only content marked as "Promoted to front page" will be displayed.

  • Sort criteria: We use "Content: Sticky at top of lists (desc)," so content marked as "Sticky at top of lists" will appear before other content.

Given this configuration, I would advise against hiding these options. Removing them would require us to reconfigure the front page view to adjust or remove both the filter and sort criteria. These fields are potentially useful, and we might want to keep them available for future use.

boulaffasae avatar Jul 22 '24 15:07 boulaffasae

I agree with you, @boulaffasae. I sort of doubt that these fields are causing enough clutter to be worth hiding.

phenaproxima avatar Jul 24 '24 03:07 phenaproxima

I'm not sure I was fully understood. Let me try to be really unambiguous: I'm only talking about hiding the fields on the node edit screen of content types where they're not used. I'm not talking about disabling the feature so it can never be used anywhere or changing how views are configured. I'm not talking about hiding the fields everywhere they appear. The problem I'm highlighting is that there are user-facing forms where those fields appear but don't do anything, leading to a confusing experience for content authors and site builders. It doesn't make sense to promote a "Basic page" to the front page or make it sticky at the top of lists. Hence I think we should hide them on that specific form display.

TravisCarden avatar Jul 25 '24 14:07 TravisCarden

Hi Travis, yes sure it should be okey to hide them from specific content types that we think no one will be using them.

boulaffasae avatar Jul 30 '24 13:07 boulaffasae