Allow excluding view mode configuration in order to selectively override the display when needed.

Created on 26 May 2021, about 3 years ago
Updated 29 May 2024, about 1 month ago

Hi,
This module is a big help for me.
I have a requirement where I need to exclude the view_mode. It creates a problem when the field(field_xyz) has referenced of node( on each selected view_mode as well). But when I display the field(field_xyz) it starts displaying the data according to the view_mode selected on each node instead of field(field_xyz) has view_mode.

Proposed solution:
Provide a config for excluding view_mode like we do for allowing view_mode on each bundle.

✨ Feature request
Status

Active

Version

1.0

Component

User interface

Created by

🇮🇳India rksyravi New Delhi, 🇮🇳

Live updates comments and jobs are added and updated live.
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.

  • 🇨🇷Costa Rica hjuarez20

    @vaibhavjain I was able to reproduce the problem, in my case we don't want the module to change the view mode when we are using a preview, listing, etc. in a view, the module changes in all view modes to the view mode that is selected in the field, I am submitting a patch to apply the module only in the full/default view mode

  • 🇫🇷France CopainGeorge

    Patch #4 works fine for me.
    Indeed, in Views for content rendered by content display mode, if a different display mode from default is selected, it is correctly applied to contents that have default value selected in their view_mode_selection field. But, in the case of a content that has a different value than default selected in its view_mode_selection field, its render in a view will be the selected one in view_mode_selection field and not the one configured in the view.

    #4 patch corrects this issue.

Production build 0.69.0 2024