Hey, I am using Display Suite and I have exported all my settings to a feature. That works fine.
But now, when I would like to chage my Field at

admin/structure/types/manage%TYPE/display/full

I can change the field order using drag&drop but my settigs are not saved.
There is no save button ot the bottom of the form where as at other manage display pages it is visible.

So I could not change any field there. I solved the problem adding a "save" submit button to the form using hook_form_alter and klick the submit button after changing field order. That works fine.

Does anybody have a solution for that problem?

Comments

swentel’s picture

swentel commented
Status: Active » Closed (cannot reproduce)

I still can't reproduce this - it's weird, still, I'm not touching field ui, that's not my responsibility.
Also no other reports either, so it must be either another module, or something with the theme.

marcosdr’s picture

marcosdr commented

Hi,

I found this issue too where it is possible to see the save button in the Layout for certain content types but others the Save button dissappears.

Not sure why this happened though, I am using the Danland theme in this case.

I also noticed that when this occurs, the Display Suite panel for editing the layout at the bottom disappears, so for example I could not use a different view mode, or add custom fields, etc. But if I turn on the panels in the extras section of Display Suite, I can get to see it. Although the Save Button is still not visible.

marcosdr’s picture

marcosdr commented

I have been doing some Form work using Display Suite, Groups and Renderable Elements. Maybe the form for the node has altered because of this although I haven't edited these forms.

sambaynham’s picture

sambaynham commented

I've got this problem. I am using field group module, but deleting any groups on the form doesn't solve the problem. It's very odd; it occurs in a custom layout, but not in a supplied layout.

alexander.sibert’s picture

alexander.sibert commented

I also have the issue with the ERPAL distribution.

manuelBS’s picture

manuelBS commented

But the ERPAL issue appears with 2.x version. 1.8 version works perfect.

jive01’s picture

jive01 commented
Issue summary: View changes

Yep, this was happening to me. Was driving me crazy, until noticed that all of the display suite default templates were working and had this line of code at the bottom:

if (!empty($drupal_render_children)):
print $drupal_render_children
endif;

Add that to the bottom of of the custom display you are using (the .tpl file) and it should work. Hope this helps.

jive01’s picture

jive01 commented
Status: Closed (cannot reproduce) » Needs review
aspilicious’s picture

aspilicious commented
Status: Needs review » Closed (works as designed)

Yeah and thats by design. There is no other way to make this work.