I have a user that complained that all of their entity changes weren't being saved (create new, add existing, edit, delete). Turned out he was clicking the inline "save" button, but not the main node "save" button at the bottom of the page.

Views says:

* All changes are stored temporarily. Click Save to make your changes permanent. Click Cancel to discard your changes.

We should say something similar!

CommentFileSizeAuthor
#6 1750964-6.patch847 byteskhiminrm
#5 edit_page.png25.88 KBarunkumark
#2 help_message_for_ief_saving_data.-1750964-2.patch889 bytesvasike

Comments

Anonymous’s picture

Anonymous (not verified) commented

My workaround for now is to add a Drupal style yellow warning message to the bottom of the IEF form:

/**
 * Implements hook_form_FORM_ID_alter()
 * 
 * Add warning to IEF that you need to click the main save button at the bottom of the page
 * otherwise all changes will be lost
 **/
function YOUR_MODULE_form_product_display_node_form_alter(&$form, &$form_state, $form_id) {
	$warn = '<div class="messages warning">* All changes are stored temporarily. Click Save at the bottom of the page to make your changes permanent.</div>';
	$element = &$form["field_product"]["und"]["actions"];
	// don't forget about any existing suffix
	$element["#suffix"] = (isset($element["#suffix"])) ? $warn.$element["#suffix"] : $warn;
}
vasike’s picture

vasike
Location Ramnicu Valcea
commented
Status: Active » Needs review
StatusFileSize
new help_message_for_ief_saving_data.-1750964-2.patch889 bytes

i think this is helpful, patch attached.

i also think this should be accompanied by this one : #1891696-2: Rename the 'Save variation' button to 'Update variation'.

JvE’s picture

JvE commented

I like it. My users are having the same issues.

But the classes do not work on themes that exclude system.messages.css (like bootstrap).
And the "Save" button may not be called "Save" so the message probably needs customizing.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented
Issue summary: View changes

Actually, I am seeing that both Update/Save buttons must be clicked to make sure all the data is reliably saved.

arunkumark’s picture

arunkumark
Location Coimbatore
commented
Status: Needs review » Reviewed & tested by the community
StatusFileSize
new edit_page.png25.88 KB

The patch was working as expected. Attached screenshot for the reference.
Making the patch into RTBC

khiminrm’s picture

khiminrm commented
StatusFileSize
new 1750964-6.patch847 bytes

Re-created the patch to latest dev.

geek-merlin’s picture

geek-merlin
Primary language German
Location Freiburg, Germany
commented
Issue tags: +Port to D8+

  • ram4nd committed 11ca051 on 7.x-1.x 
    Issue #1750964 by khiminrm, vasike, arunkumark: Add views-style warning...
ram4nd’s picture

ram4nd commented
Status: Reviewed & tested by the community » Fixed
dww’s picture

dww
we/he/they
commented
Status: Fixed » Patch (to be ported)

Thanks for this UX improvement.

Is there a D9+ version of this? Seems weird to be adding new features for D7 that don’t have parity in D9+. It’d become a regression for folks that rely on this in D7 when they try to upgrade.

ram4nd’s picture

ram4nd commented

Isn't it in core in D8+?

bluegeek9’s picture

bluegeek9 commented
Status: Patch (to be ported) » Closed (outdated)

We appreciate your contributions to Inline Entity Form. Drupal 7 in End-of-Life. We encourage you to upgrade to a supported version of Drupal.

//www.flaticon.com/free-icons/thank-you Thank you for your contribution! Your continued support makes this project sustainable.
There are multiple ways to show appreciation for the work contributed to this project including:

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.