I've created a content type (standard stuff) and I want each node to use a custom view mode by default that I've set up. I see several custom display settings for view modes under "Manage Display" >> "Default" >> " custom display settings" tab.

Right now all my articles are not adhering to my settings and are using a non-coded plain page without any of my styling by default.

How do I configure the custom display settings / view modes so that a default is picked that's one of my customized layouts?

I see "Default", "Full", "Teaser" etc but if I create "Full Two" for example, why cant I make that the Default one selected by my nodes / articles automatically and by default?

Comments

Dru Pal created an issue. See original summary.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now 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.

manoj selvan’s picture

Assigned: Unassigned » manoj selvan
manoj selvan’s picture

Hi @Dru Pal,

Custom display settings option is provided for adding your view mode(Full Two) to Manage Display so that you can create customized layout and use it in views. The Options(Full Content, RSS, Search index, Search result highlighting input, Teaser) were provided whether the view modes needs to be displayed in Manage Display or not.

But if you want to make Full Two as your default you can use same layout(Full Two) in default. As Default is the only option and you can customize that since default is not needed.

If you want to use default and Full two. You can create a view and set view mode as Full two.

manoj selvan’s picture

Status: Active » Needs review
smustgrave’s picture

Status: Needs review » Closed (works as designed)
Issue tags: +Needs Review Queue Initiative

This issue is being reviewed by the kind folks in Slack, #need-reveiw-queue. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge require as a guide.

Closing as work as designed with the comment in #4.

If still an issue please reopen and move to needs work with an update issue summary please.