When using Display Suite to change field markup, if the option "Sticky form actions" is on, the Update for the field disappears.

We are only left with a save button at the bottom.

Follow the screen shots with and without "sitcky form actions" activated.

With option activated

Without option activated

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

jmary created an issue. See original summary.

mathiasgmeiner’s picture

It's the same problem ith the Paragraps-Module.
So every module with a form with ".form-actions.form-wrapper".

My simple fix is to activate the "adminimal-custom.css" and put (for the Paragraphs-module) this css definition in it:

body.sticky-actions .field-type-paragraphs .form-actions.form-wrapper {
	position: inherit;
	box-shadow: none;
	border-top: none;
	width: inherit;
	padding: inherit;
	background-color: transparent;
}
mathiasgmeiner’s picture

Title: Display Suite Update Field Markup » "Sticky form actions" with multiple forms
shadysamir’s picture

Same problem for Translations Export page admin/config/regional/translate/export

gmclelland’s picture

Off topic, but just an FYI... There is a module that provides the same functionality as this theme. https://www.drupal.org/project/sticky_edit_actions

Maybe this theme could just add the styling needed?

PhilY’s picture

Same problem with Field Group.
Anyway, "adminimal-custom.css" trick by mathiasgmeiner at comment #2 might be the only way to fix every concerned modules.

kopeboy’s picture

Priority: Normal » Major
FileSize
329.82 KB
328.44 KB
kopeboy’s picture

Use #2 and substitute .field-type-paragraphs with .field-ui-overview if you want to fix for the "Update" and "Cancel" buttons when editing field formats in the Manage Display tab of content types as well.

soyarma’s picture

Title: "Sticky form actions" with multiple forms » "Sticky form actions" with multiple forms hiding update/cancel buttons
soyarma’s picture

This CSS should be able to generically target most ajax forms (field settings, views, etc...)

body.sticky-actions form .ajax-new-content .form-actions.form-wrapper {
	position: inherit;
	box-shadow: none;
	border-top: none;
	width: inherit;
	padding: inherit;
	padding-top: 2em;
	background-color: transparent;
}

Side note: I prefer using CSS injector for stuff like this as you can target the theme and/or certain pages while keeping the source of the edit in the DB rather than the filesystem which usually is not as easily recoverable.

Rotozaza’s picture

Field settings or Display Suite update of fields works with Save button at bottom, but not other type of updates as Display Suite configure Dynamic Field.

If stumble upon such, I switch to Seven, update and switch back to Adminimal.

kopeboy’s picture

Status: Active » Reviewed & tested by the community

#10 works perfect.

ndewhurst’s picture

Status: Reviewed & tested by the community » Needs review
FileSize
893 bytes

Here's a patch that incorporates mathiasgmeiner's and soyarma's CSS directly into the relevant part of the theme's CSS. It works well for me, and, as soyarma pointed out, should cover all the various manifestations of the issue described above.

frederickjh’s picture

Hi!
Just a thought, while we are adding css for the buttons could we also color them more to the Adminimal Theme colors, instead of the grey that the the Update and Cancel buttons currently are in the stick form actions?

Greetings!
Frederick

Rudi Teschner’s picture

Patch from #13 works for me. Paragraphs can now be used properly with the sticky setting

xax’s picture

I had the same problem, the sticky setting one meant the bottom part of any page (e.g. when you add content the 'publishing options' were stubbornly behind the sticky bar at the bottom). Using the CSS from #2, #10 or the patch in #13 worked, but then I found that when using the media browser module you lose the bottom part of that modal..

So I ended up (cleaner solution than patching the adminimal module's own CSS using #13) putting the following CSS in the 'adminimal-custom.css' (in sites/default/files once you tick that box in the adminimal settings), and now all works everywhere:

body.sticky-actions .field-type-paragraphs .form-actions.form-wrapper {
	position: inherit;
	box-shadow: none;
	border-top: none;
	width: inherit;
	padding: inherit;
	background-color: transparent;
}

body.sticky-actions form .ajax-new-content .form-actions.form-wrapper {
	position: inherit;
	box-shadow: none;
	border-top: none;
	width: inherit;
	padding: inherit;
	padding-top: 2em;
	background-color: transparent;
}

body.sticky-actions.adminimal-skin-material #page {
    margin-bottom: 80px!important;
    padding-bottom: 80px;
}

.media-browser-tab.ui-tabs-panel {
    border: none;
    padding-bottom: 80px;
}

(I guess another module may one day require a similar line of padding-bottom to cover it's particular divs and classes)..

jmev’s picture

I was experiencing this for all display suite field settings edit forms and was switching back and forth. It was driving me nuts. Thanks, xax, for the quick fix, works like gold.

asya_asina’s picture

Status: Needs review » Reviewed & tested by the community

The patch from comment 13 applied and working.

COBadger’s picture

Status: Reviewed & tested by the community » Needs work

The patch from comment 13 does not solve the problem as experienced when a user is editing a paragraphs-based field. Revised patch forthcoming.

COBadger’s picture

Status: Needs work » Needs review
FileSize
793 bytes

Revised patch attached.

Soubi’s picture

I added this to my adminimal-custom.css

body.sticky-actions form .ajax-new-content .form-actions.form-wrapper,
body.sticky-actions form .draggable .form-actions.form-wrapper {
    position: inherit;
    box-shadow: none;
    border-top: none;
    width: inherit;
    padding: inherit;
    background-color: transparent;
}

because draggable is more generic compare to .field-type-paragraphs

COBadger’s picture

@soubi I agree; thanks.

Revised patch attached.

BhumikaVarshney’s picture

Status: Needs review » Reviewed & tested by the community

Hi,
@COBadger,
The above patch works fine for me.
Thanks

andrey.troeglazov’s picture

Assigned: Unassigned » andrey.troeglazov