Where is "save as draft" button ?

[LouisCuvelier]

Description

When I create an entry, there is only the button "Save". "Save as draft" only appears when I save the entry for the first time ?

Maybe I'm not understanding the logic. 🤷‍♂️
For the moment, to save a new entry but without publishing it, I have to disable the entry then save it.

As mentioned here #1021, there is an auto-save but where I can see all the drafts ?

Steps to reproduce

1. Create a new entry
2. Save
3. See the button "Save as draft" appear

Additional info

• Craft version: 3.4.5
• PHP version: 7.3.14
• Database driver & version: MySQL 5.5.5

[jamiewade]

When you create an entry for the first time, it is a Draft until you hit the save button. You will see the Draft has been saved because of the green tick:

To see all of your Drafts, you can go to the Entries page in Craft and choose Drafts from the dropdown:

Because of Craft's autosave functionality that was introduced in 3.2, if you save a Draft using the keyboard shortcut or the save button, that will then publish the Draft and put it live.

So, to create a new Draft without publishing it, you will need to follow these steps:

• Create your entry and give it a name
• Set the Enabled lightswitch to false

And that's it. As I mentioned, don't save the entry as this will take it out of a Draft state and into a live entry state. As you add/change content on the entry, you wil see the green tick icon swap between a loading spinner then back again, which is confirmation your content changes are being saved to the Draft.

Hope that helps!

[LouisCuvelier]

Oh ok, this is clear now. I understand the logic.
Thank you for your clarifications !

[LouisCuvelier]

Maybe I'm the only one, but I found that the "draft flow" is not obvious.
When I create an entry and it's a draft, the "Save" button should be "Publish", and the button "Save as draft" should be next to it. Like when I edit a published entry.

In my opinion, it's not instinctive to just quit the page without "Save as draft" because I feel that my draft is not saved due to the "Save" button right in the top corner. This is not giving a confident feeling.

[brandonkelly]

When you create a new entry, it doesn’t fully exist until the first time you click “Save”. In fact, unsaved drafts are ephemeral – they will be deleted automatically by garbage collection, per the purgeUnsavedDraftsDuration config setting.

So if you are creating a new entry but you’re not planning to fully publish it right away, then you should mark it as disabled and click Save.

There’s not much point in creating a draft for an unpublished entry – most of drafts’ value comes in working on a revision to an already-publish entry.

[narration-sd]

Sigh. I know you love it when I do this, Brandon @brandonkelly , so I'm going to delete the chain of thoughts above. But in the evening away from things, it started coming back to me how you've said before and actually here, how you think of matters, in 'pre-draft', draft-becomes-actual, current, and 'saved as draft' states.

And so I think I see where the problem lies, thus how to re-state the points I was getting at, I hope then for good use.

You evidence thinking of this area in terms of Craft internal states, while for a person just ready to edit content, there are really only two states: draft, and published. That's true even if there are posting/expiry dates, or if the published entry is disabled -- published is still the published entry, and draft is anything written (and saved-available!) before publishing.

Thus:

• a newly created entry is a draft, content-wise.
• your UI even says it's a draft
• therefore it should obey the rules for any edited content, in that moving away should trigger a stopping alert.
• That's what the 'initial' draft does not at present, so that it's very easy to lose work. My poinr-along-the-way, if not the main point. Continuing...
• since it's a draft, the initial draft should indeed have a Save button.
• that Save button should...save it. As a draft. As any other later draft. The button can say Save, or as you've done elsewhere, add a bit to make clear, thus be labelled Save as Draft. If you agree that would help. I kind of think it would, but it's not my decision.
• the saving action makes the draft 'real' for Craft, so it can be found by its title and opened again. It's a draft in the sense that any in-editing-process document is.
• now, what else does that initial draft need? It needs the ability to be published. Thus, as soon as a new entry appears, it needs a Publish button. That button will insist as ever to have a title, etc., before it will become active and operate, of course. And any setting of posting/expiry/disabled willa act on the resulting published entry as they ever do.
• pretty clearly, the Save etc. button should occur before the Publish button, thus Publish should end up the last button on the right.

I am not going to go farther here, as generally your buttons and actions seem sensible past the point of that new entry initial draft. You do do some added indicative labeling; some of that might be visited in seeing how you may choose about amplifyubg the label of the initial entry's Publish button.

Fini.

I suspect this outline will answer the initial request by @LouisCuvelier , and his later concern again for logic.

Personally I would feel it can make Craft that much more approachable, and easily sensible in use, especially for those content creators we serve. I'm always ready to see and understand your improved idea should you see differently; you know that. Thanks for listening.

[brandonkelly]

• a newly created entry is a draft, content-wise.
• your UI even says it's a draft

Well… yes, and that is technically true, but the page title says “Create a new entry”, which should indicate that the entry is still in an unsaved state.

• therefore it should obey the rules for any edited content, in that moving away should trigger a stopping alert.
• That's what the 'initial' draft does not at present, so that it's very easy to lose work. My poinr-along-the-way, if not the main point. Continuing...

Actually since it’s a draft and drafts get autosaved, the consistent behavior is to not show an unload confirmation. If you accidentally leave the page, your content will still be recoverable for a while from the Entries index page, by selecting “Drafts” in the status menu.

• since it's a draft, the initial draft should indeed have a Save button.
• that Save button should...save it. As a draft. As any other later draft. The button can say Save, or as you've done elsewhere, add a bit to make clear, thus be labelled Save as Draft. If you agree that would help. I kind of think it would, but it's not my decision.
• the saving action makes the draft 'real' for Craft, so it can be found by its title and opened again. It's a draft in the sense that any in-editing-process document is.

I agree that it was counterintuitive for the “Save” button on the draft to publish the entry. So I’ve just relabeled that button as “Create” instead (f96e6f3), so it’s more clear what happens when you click it.

Changing the behavior so it saves the entry as a “real” draft doesn’t make a ton of sense. To do that, we would still need to save a real entry first, populating it with a title and probably whatever other content you’ve already entered, and then also create a new draft for that entry. If that’s in fact what you want to do, then you can get to that state easily enough by clicking “Create” followed by “Save as a draft”.

[narration-sd]

Hmm, hmm. I like 'Create' -- that opens new avenues, with better semantics. I've just been trying it out via your latest dev.

Scenario: So, I write some info into the fresh (says its a draft, saved as) form. I want to leave and come back, finish it later. No buttons or submenus say how I can do this. If I back-button to Entries, nothing shows. Yes, I could find it in Drafts, if I had a thought of that.

Secondary attentions: I note that there had been a Create and add another submenu button. But then I would have published my non-filled-in-or-finished draft. Also, if I find the draft I managed to silently 'leave' (not Create), go back in, it's the Create button again, still same meaning(s), but less clear somehow as I'm clearly in a draft again.

I won't be around much today, Brandon, so let's see if I can make a quick run at moving even better, starting with what we now have from your good move.

• Create is Great.
• But, it should in my view be Create Draft. Meaning really, in your behind-the-scenes view, create a visible Draft.
• Once a draft is a (visible) Draft, it has three properties:
  • you'll get the alert, if you try to back out of it
  • now its main, farthest right button says Publish, which will be eminently clear
  • the secondary button Save Draft appears, active on further changes, acts as you expect
  • this is how it will be for un-Published Drafts, editing forwards, now or later rejoined
• On the Entries pane, now drafts show with others in All - as would be expected
  • same is true any time you re-enter the Draft

Last thought is for the perhaps findable backed-out Draft.

• this would really only occur if you answered the alert that you really wanted to leave the page
• it's not going to work if you didn't write a title.
  • in fact you'll find that it doesn't work now without a title -- with a bug.
    • a blank-titled item will appear (at the end of) the Drafts list
    • you can't select and use it w/o title
    • and if you attempt to put a title in via checkbox=>menu, click it, you'll get a 404 and the draft truly disappears. With whatever you might actually have entered into its Body, etc.
    • so this needs fixing, one way or another -- auto-dummy-title, perhaps??

But this overall last thought-and-consequences does seem to illuminate further how much good it would do to make Drafts fully visible, always protected citizens. Which by forced-to-Create in the sense offered above, would be guarded always to have titles.

A smile...always

(saved off a screenshot, don't think we'll need it)

[brandonkelly]

Craft 3.4.6 is out now with the change to the submit button label.

@narration-sd I kinda feel like you didn’t read/address this point:

Changing the behavior so it saves the entry as a “real” draft doesn’t make a ton of sense. To do that, we would still need to save a real entry first, populating it with a title and probably whatever other content you’ve already entered, and then also create a new draft for that entry. If that’s in fact what you want to do, then you can get to that state easily enough by clicking “Create” followed by “Save as a draft”.

[narration-sd]

Hey, @brandonkelly, could be, if it means save as draft converts it to one, with no posted. Out of office, will have a look evening when home & when eyes un-dilated... Cheers

…

On Tue, Feb 18, 2020, 13:43 Brandon Kelly ***@***.***> wrote: Craft 3.4.6 is out now with the change to the submit button label. @narration-sd <https://github.com/narration-sd> I kinda feel like you didn’t read/address this point: Changing the behavior so it saves the entry as a “real” draft doesn’t make a ton of sense. To do that, we would still need to save a real entry first, populating it with a title and probably whatever other content you’ve already entered, and then *also* create a new draft for that entry. If that’s in fact what you want to do, then you can get to that state easily enough by clicking “Create” followed by “Save as a draft”. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#5661?email_source=notifications&email_token=AAB4RCJ6EZXB22CX5B4OZZTRDRI6TA5CNFSM4KWOGUHKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMFKTBI#issuecomment-587901317>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAB4RCILL5ST7RV24AOLLCDRDRI6TANCNFSM4KWOGUHA> .

[narration-sd]

Brandon @brandonkelly , I did have a look with regards your text last night, just had not eyes-capable-of-screen back to look past that save-as-draft didn't answer how I saw things. And in fact, that's what your quote really says, that it doesn't intend to.

But this delay did give me a chance to reflect, and so I think our difference of view may be as follows:

• how Craft worked before there were Drafts, is that always a new Entry would be live, after it was first saved -- unless a later posting time or disabled were set.

• Now that we have Drafts, my thinking ran that it seems Craft would suit content creating more conveniently if it did not automatically make posts live, giving a free chance to build them up. But you still need always to save the uncompleted work.

• I think that how this would be quite helpful is nicely illustrated by considering to use the dropdown option to Create and add another . Without recoverable save of a 'real' current draft, and especially without having been forced to title it, you are going to lose your work for good, via the becomes-404 lookup error mentioned above even if you thought to select Drafts.

• Side point but important is that All Entries doesn't presently include Drafts...with AlwaysRealDrafts™, the issues one can see behind this omission become much more coverable, no?

So I guess it's up to you if you'd like to make the transition. If so, I suspect the Create Draft - Publish arrangement I proposed would suit this, or indeed something else you made of its intents.

I do well realize the trickiness in the implementation behind what appears on the screen -- the intermediate steps of what seems an initial draft becoming a real one. I felt that instituting the alert for leaving, now at the written-into-pre-Draft/seems-a-draft stage would handle this. You'd never lose work unintentionally, and as well would avoid matters like the no-title/no-findee/404 error I turned up.

Hope this is clear enough, and then you can reflect also...

[LouisCuvelier]

@narration-sd you're just reading my mind about this subject.

I agree that it was counterintuitive for the “Save” button on the draft to publish the entry. So I’ve just relabeled that button as “Create” instead (f96e6f3), so it’s more clear what happens when you click it.

To me "Create" doesn't seem very clear and is confusing. Is it "Publish" ? Is it "Save" ? What does it mean ? (From an editor's point of view).

As a real use case, a friend of mine wrote some content for me. He didn't understand the "Save" button for a draft. He would not understand neither "Create". I'm using Craft since a year now and, me too, I was like "Wtf ? I don't want to publish it ? What should I do ?". Instinctively, I finished by disabling the entry and save it.

It is unsettling and not reassuring to have two different ways of saving entries :

1. Auto-save for drafts. If I quit the page it's ok.
2. No auto-save for published entries. If I quit I'm f****ed.

For a long time, the Craft's UI taught us to click the save button to not losing our content. Now, it's unnecessary for drafts. It loses people.

So, I think that "Save as draft" and "Publish" combo is much more understandable.
Why ? "Save as draft" already exists in the UI. It's something that the user is used to. And "Publish" is clearly saying the purpose of the action : "My draft will be live".

therefore it should obey the rules for any edited content, in that moving away should trigger a stopping alert.

Because of auto-save, a stopping alert doesn't seem relevant. It would be an extra bonus.

I hope that I'm clear 😅

[narration-sd]

Just a quick reply, @LouisCuvelier , to say you are very clear - dans le soir, en anglais :)

A point -- the stopping alert looks necessary on a fresh entry, so that you actually save the draft, with a title also as required. After that, I think your view seems correct, that it isn't needed.

Gone again, so Brandon can have his thinking about this...

[narration-sd]

...though I meant to say at the beginning, Drafts are a very nice achievement, would want you to know, @brandonkelly .

Which I fully appreciate, having tracked along to wire other software with them, as they were created.

The change in view from how things were, just opens the opportunity for us to get them fully smooth -- and with all their advantages.

[wsydney76]

We also found that this draft work flow can be confusing, so ended up with adding a custom module to each project that changes the button texts and adding some hints.

The texts are project specific, whatever the client understands best, e.g. 'Current' is the term used in the header drop down, 'finish your work' is a term used in other tools the client is familiar with.

/Mel

[RitterKnightCreative]

To me "Create" doesn't seem very clear and is confusing. Is it "Publish" ? Is it "Save" ? What does it mean ? (From an editor's point of view).

Yeh I think the button should be renamed from "Create" to "Publish". After an entry is published, it should then read "Save" (which is does now).

If a draft is not yet published (ie live), "Create" is a bad verb. It doesn't imply that the entry someone is working on will be published. However, if I try to save a brand new entry without a title, for example, in Craft's error message, it does complain the draft can't be published—which implies Craft already "created" something.... a slight continuity disconnect.

So, it seems at the very least, Craft should be more consistent in its terminology throughout.

Also, on a brand new entry, Craft is saving my work but if I hit the back button, I can navigate away without it complaining. I'm not sure if that's good or bad. As mentioned above, Drafts are definitely saved and you can access if you know where to look for them. However, it would be nice if there was some discoverability there... even if it's just in the dialog box. "Really navigate away from this page? (Your draft is still being saved though, you can find it in the Drafts section" or whatever.)

[JoeyNK]

@brandonkelly I have been testing craft now for about 8 months as we intend to use it on multiple sites. We use it as a headless API. I use to be able to query drafts via Element-API by simply including the draftId in the query criteria but today, I have realised that Craft no longer returns a particular draft (searched for by draftId) of a published article. It only returns the published version even if the draftId is part of the query criteria.

Is this something that has been disabled or I'm I doing something wrong?

[brandonkelly]

Hey @JoeyNK, that seems unrelated to this issue; can you email us at support@craftcms.com ?

[leevigraham]

@wsydney76 Can you share the code for "Possibly conflicting draft"? I just posted this #6176 which I think addresses the same issue.

[wsydney76]

@leevigraham Sure, don't have access to the final version right now, but this one should already work:

https://github.com/wsydney76/craft-drafts-module

@ Werner Sorry to have brought your old man's retired account back to life :-)

/Mel

[mmikkel]

Changing the behavior so it saves the entry as a “real” draft doesn’t make a ton of sense. To do that, we would still need to save a real entry first, populating it with a title and probably whatever other content you’ve already entered, and then also create a new draft for that entry. If that’s in fact what you want to do, then you can get to that state easily enough by clicking “Create” followed by “Save as a draft”.

That's not a solution, at least not an intuitive one :)

From the perspective of a lot of content editors, what they often want to do when creating a new entry is to save their work, without publishing it. Currently, there's no intuitive way to accomplish that.

The initial auto-draft that Craft creates doesn't meet the use case. It's ephemeral (hence it's not really "saved"), and also doesn't offer the reassurance that some content editors need in manually clicking a "Save" button.

Disabling the entry before hitting the "Create" button kinda works, but it's not intuitive at all that what the user needs to do, is to "disable and create", rather than to simply "save as draft" (or "save the draft"). Add to that the fact that a disabled entry and an actual draft is not the same thing.

I think that regardless of how drafts and auto-drafts work behind the scenes, it'd be great if there was a way to improve AX in this area.

[brandonkelly]

That makes a lot of sense @mmikkel.

[RitterKnightCreative]

If you take a page from, say, WordPress, the default action there is Publish but there's another (text only) option to Save draft or Preview.

Inside Craft, I could see something similar, using the dropdown button:

[leevigraham]

My custom module UI:

[brandonkelly]

I’ve just resolved this for Craft 3.6. Going forward, when you click the “New entry” button, the entry will start out life as an “unpublished draft” rather than an “unsaved draft”. Unlike the former concept, unpublished drafts aren’t ephemeral. They will continue to exist until explicitly published or deleted. And their primary action is to be saved, rather than “created”.

Pictures are worth a thousand words, so here’s how the editing experience compares between 3.5 and 3.6 when clicking “New entry”…

Normal drafts have gained an explicit “Save draft” button as well (saves and takes you back to the entry index), plus “Save and continue editing” (triggers an autosave), and “Publish and add another” actions. Again, 3.5 vs 3.6:

You might notice that the actions available to unpublished drafts are identical to normal drafts, which is intended. The only difference is that in the case of an unpublished draft, there’s no source entry yet, up until someone publishes it.

[brandonkelly]

Craft 3.6 RC2 is out now with this change.

[brandonkelly]

Craft 3.6 has now been officially released ✨

[RitterKnightCreative]

@brandonkelly Not to drudge up an old issue here but is there a UX reason why after pressing Save on a published entry Craft sends you back to the Entries screen? Craft doesn't do this when a draft is not yet published—it takes you to the published entry's screen.

I just had a client the other day make changes to the "live" published version of an entry. She did everything right, including pressing the Save button. However, because that entry was already published, the client thought she had made a mistake since she was now seeing the "export" button on the bottom of the entries window after pressing Save. She apparently had missed the "entry saved" notification on the top. However, the entry was saved and her changes published.

I know it's always been this way but I've felt it's always been a workaround.

To that end, I wonder about changing the "Save" button to a "publish changes" button on current / live documents? That would at least make it clear what's going on.

[brandonkelly]

Craft doesn't do this when a draft is not yet published—it takes you to the published entry's screen.

@RitterKnightCreative If you are editing an unpublished draft and click the “Save draft” button, it will in fact take you back to the Entries index page, like all other Save buttons.

To that end, I wonder about changing the "Save" button to a "publish changes" button on current / live documents? That would at least make it clear what's going on.

We currently reserve the word “Publish” to refer to the act of converting a draft into a published entry. Not completely opposed to expanding on that, but it would be something we’d need to discuss a bit. Feel free to post a new issue about it.