You cannot configure standard display suite layouts AFTER creating layouts for forms using renderable elements [#1345960]

Hi,

Maybe a bug not sure. I can live with it but it may help others to know.

I noticed that if you create a display suite/renderable elements form layout you cannot then configure a 'standard' display suite layout for the same content type, the vertical tabs disappear.

If, however, you configure the ds node layout first then you can.

Rich

Comment	File	Size	Author
#6	ren save button gone.PNG	6.85 KB	MLZR

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

lurkingbeast CreditAttribution: lurkingbeast commented 5 December 2011 at 09:36

Any news about this one? I have this problem and I can't fix it using the configuration order which Rich suggested.

- I create a content type,
- set DS node display layouts,
- click manage form and select all elements
- I apply a layout in manage fields and hide the vertical tabs from user
- I go back to node display layouts and the vertical tabs are hidden, including Save button

On a related note, I set the content type status default is Published. Now if I hide the Published/Unpublished option from the form and the user creates a node, it's not published. If I add the published status option on the form, the created node is published like it was set default.

Both DS and Rel are really cool modules and I'm using them as much as I can, I will try to debug the problems mentioned above but as a timesaver would be cool if the author could point me in the right direction.

Comment #2

dgtlmoon CreditAttribution: dgtlmoon commented 12 March 2012 at 23:49

On a related note, I set the content type status default is Published. Now if I hide the Published/Unpublished option from the form and the user creates a node, it's not published. If I add the published status option on the form, the created node is published like it was set default.

I've seen the same strangeness, but can't quite confirm what's happening, i can confirm tho that the $form structure is changing and 'status' is no longer $form['options']['status'] instead it's just $form['status'] which might impact some modules (like the premium content module form_alter)

Comment #3

firfin CreditAttribution: firfin commented 7 June 2012 at 13:11

Created a new issue for the 'related note'
See #1621116: Node gets unpublished if 'Published' setting is hidden.

Comment #4

miss_3alek CreditAttribution: miss_3alek commented 1 December 2012 at 11:33

same problem!

there's no save button on manage display page after using ds and render elements together.

Comment #5

deanflory CreditAttribution: deanflory commented 25 May 2014 at 17:31

Issue summary:

View changes

Is this still an issue?

Comment #6

MLZR

Zutphen

CreditAttribution: MLZR commented 21 August 2014 at 16:42

File	Size
ren save button gone.PNG	6.85 KB

Yes.

I uses DS an try renderable elements.
Bud then the save- button from the form of renderable elements is gone, bud also the save- button on the form from that content-type is gone?!

See screenshot;
1) where is the save button for saving renderable elements
2) the save- button on the bundle/ content type is also gone.

I installed ren, figure out it was not the solution for my situation. Then I set back the form to his origin (checkout from ren).
Now both buttons are gone.

Comment #7

thoughtcat CreditAttribution: thoughtcat commented 29 October 2014 at 14:15

Reproducible here... this seems to only happen if I tick the "save" element box when registering the node form. After that, the "save" button will not show on the node form (for users of any role, regardless of permissions etc) even if it's not hidden in DS Forms. So I reset the form and re-registered it without ticking "save". I actually found it simpler to use Node Form Columns than the DS Forms sub-module in terms of hiding stuff.