Problem/Motivation

As @webchick said in #1510544-126: Allow to preview content in an actual live environment

I found my natural inclination while testing this was to want to be able to save right when I'm looking at the page

Follow-up of #1510544: Allow to preview content in an actual live environment

Proposed resolution

Add save dropbutton as per #1751606: Move published status checkbox next to "Save" to the preview bar.

Remaining tasks

  1. Postpone on #1510544: Allow to preview content in an actual live environment and #1751606: Move published status checkbox next to "Save".
  2. Add save dropbutton.

User interface changes

We'll have a save dropbutton next to "Back to content editing" link.

API changes

None

save button.png

CommentFileSizeAuthor
save button.png39.97 KBjibran
Members fund testing for the Drupal project. Drupal Association Learn more

Comments

jibran’s picture

Bojhan’s picture

I am not sure how I feel about this, the idea is that you return to the content creation page - as that is the central interface.

webchick’s picture

If anything I'd turn the "Back to content editing interface" button into a drop-down to save space.

yoroy’s picture

Interesting case where you can't save on the node form when preview is made required: #2354469: Can't create node, if preview is required

swentel’s picture

dawehner’s picture

Component: base system » node system

.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

yoroy’s picture

Issue tags: +ux-workflow

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

pixelmord’s picture

Issue tags: +dcmuc16
Dimiter’s picture

Assigned: Unassigned » Dimiter
yoroy’s picture

Oooh nice, did you get anywhere with this?

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

jibran’s picture

Do we still need this? Even after the recent changes in node form?

Berdir’s picture

This has nothing to do with them I think, so would still be useful.

However, I expect quite a few problems with this, specifically that all non-field based things would be lost if we simply save the node, e.g. menu link changes. Otherwise we'd need to submit the node form and not just save the node we have.

webchick’s picture

Issue tags: +Needs usability review

I had always envisioned this working in the way you describe, so carrying over all of the field values as well as the node values. (I'm surprised it doesn't already do that, given that it previews those values?)

However, we might want to revisit this issue in UX meeting, because we recently ripped out the dropbutton pattern on the node form due to its obtuseness for content authors.

Berdir’s picture

Yes, it wouldn't be a dropbutton anymore, just a save I guess and possibly explicitly display the status?

node values = field values (a node/entity is nothing but a set of fields with values). But there are things that are *not* saved on the node, and the menu link settings are one example of that. That's not visible because we are not actually previewing/showing that anywhere. It works right now because we store the whole form state including all submitted values and then we restore it, but it woudln't work if we'd just do a $node->save(), then those changes would be gone.

Bojhan’s picture

Issue tags: -Needs usability review

Lets proceed with the idea, but we need to figure out the best execution.

handkerchief’s picture

Great! I'm glad this will be implemented. This is a very important feature for us, because it's intuitive to save the node direct in the preview. Less unnecessary clicks.

handkerchief’s picture

It would be nice, if the save dropbutton would also be at the end of the form as usual. But it's a "nice to have".

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.