Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
In ds.registry.inc
in _ds_entity_info_alter()
, custom view modes are defined by:
$view_mode = array(
'label' => check_plain($view_mode_value->label),
'custom settings' => FALSE,
);
I am using panelizer-7.x-3.x to allow users to customize the layout and content on a view mode created with ds, and panelizer requires 'custom settings' = TRUE
. If there not a reason for it to be FALSE, I would like to propose changing the value to TRUE to allow support with panelizer out of the box.
Comments
Comment #1
swentel CreditAttribution: swentel commentedWell, it's following the logic in core. For instance look at node_entity_info() which by default only enables the 'teaser' view mode. See http://api.drupal.org/api/drupal/modules%21node%21node.module/function/n....
Other view modes can be enabled on the 'default' tab at 'Manage display'. That should work as a work around. But you'll probably have to save the 'manage display' once to let the fields system know there are actually custom settings. But try it with just enabling first.
Of course, in case it doesn't work, I could add an option in the UI of custom view modes to let settings be TRUE, but default they will stay FALSE though.
Comment #2
Dadaisme CreditAttribution: Dadaisme commentedHi!
I just fumbled on the same issue: Enabeling a custum display from display suite in manage display for a content type (a way to setting in to true?) does not make it "panelizerable".
Suggestion?
Thx.
Comment #3
kiramarch CreditAttribution: kiramarch commentedAgreed, would also love to be able to panelize custom view modes!
Comment #4
aspilicious CreditAttribution: aspilicious commentedNot fixing this in D7 as it follows core like Swentel said. In D8 this functionality is in core and it doesn't activate the view mode either.