Allow "save and stay" to be the default save button action

[jordie23]

I'm currently evaluating Directus CMS for our site.

While testing, I've noticed the save button on content is "save and return to list". I know this will annoy our writers, is there a way to default it to "save and stay"? I know there's command+s, but not all our writers are the most tech-aware and would opt for the button still.

If it's not a feature already (couldn't see it anywhere) then I'd like to request it. Perhaps it could be a user preference option?

[benhaynes]

Would this be a Project, Role, User, or Collection setting?

[benhaynes]

I vote for global user preference only. It defaults to what we have now, but users can override this with a default action (global, not per collection/role). We could take that a step further and have a project default... but that's more of an add-on.

[jordie23]

I vote for global user preference only. It defaults to what we have now, but users can override this with a default action (global, not per collection/role). We could take that a step further and have a project default... but that's more of an add-on.

Basically how I envisaged it. Though I did think it could be something people could toggle in their own profile, a global default would at a minimum be very helpful.

[philleepflorence]

I vote for global user preference only. It defaults to what we have now, but users can override this with a default action (global, not per collection/role). We could take that a step further and have a project default... but that's more of an add-on.

This works!

[Microphunk]

Also would be nice if you could Hide these "Special Actions" , the ... button.
And fields "Clear Field" and "Raw Value" seems quiet odd feature to me as well. Users just don't interact with apps like this. If they want to clear the field, they will focus on input and backspace it or select txt -> delete. (Visibility options) for these would be nice.

[benhaynes]

Users just don't interact with apps like this.

Can you provide a but more insight regarding this? These features were added by request. Some interfaces are not as easy to clear (eg: a map, relational data, etc)... and with our support for custom interfaces, we need to have fallback in case developers forget to include these key features.

Also, any reason the "..." save menu should have an option to be hidden? Adding random settings like this can make the platform far more complex to configure, with little benefit.

[insidesmart]

Is there any clean way to override the default save functionality via extensions until the feature is available in the product ?

[rijkvanzanten]

No, extensions currently don't have the ability to override the save button behavior in-app 👍🏻

[JonL1]

Another use case for refactoring Studio client/server logic into (scoped?) system-flows. Humongous refactoring project I know…but one can dream :)

I can also imagine the bug triaging nightmare 😂

[rijkvanzanten]

Heya! Thanks for opening this feature request!

This feature request has received over 15 votes from the community. This means we'll move this feature request to the Under Review state!

The Core team will schedule a meeting to review this request as soon as possible. The discussion will then be approved or denied. You may or may not be invited to join this meeting with the core team.

For more information, see our Feature Request Process.

[rasco]

Has anyone started working on this issue?
I think just a global pref would suffice for us.
We prefer the "Save and stay" option as default.

[rasco]

Now, with the v10.2.0 release having Preview Mode, the default "Save and leave" functionality makes less sense.

Especially considering that the mod+S keyboard shortcut (at least on Mac/Chrome) often doesn't work correctly (it is sometimes captured by the browser which then tries to save the HTML page on disk).

As long as preview mode is enabled, I'd expect the default save functionality to save and refresh the preview pane, so I can view my changes.

[rijkvanzanten]

Applying different functionalities to the same button doesn't feel like good UX.
So I tend to both button being visible - ideally on all pages for consistency.

I don't know if I agree there. There's 3 different save options + a discard changes option within that subnav; having all 4 as buttons side by side might be very confusing too

[rasco]

A part of the solution could be to make the different save buttons have different designs:
The default one could be red, as it is now, while the 'Save and stay' one could be white inside with a thick red border.

[rijkvanzanten]

The default one could be red, as it is now

Do you have custom CSS configured? By default, it's purple (primary) 👀

[rasco]

Ooops haha, yes, the default primary color I mean. Not red

[a-fazal]

Due to the preview functionality personally it makes most sense for me to set the save option by collection. However by user is also good with me! Whatever makes it easiest to start with

[rijkvanzanten]

Here's some ideas!

• We should split up "Save and X" from "Save as Copy" and "Revert Changes"
• Then we can default to main button to the "Save and X" operation you used last.
• We can store that in localstorage maybe?
• I think it'd annoying to have to go to a different page to configure this, as it feels like something you might want to change on a case by case basis.
• I don't think it should change the keyboard shortcuts
• It should change the icon + tooltip for whatever the current "default" action is

[rijkvanzanten]

One two more things:

• Per collection or global?
• Save it to the user to persist?
• Make it per session?
• Not make it persist at all?
  • By that I mean as soon as you navigate away from the item detail page it resets back to the default default
  • ^ that feels good

[paescuj]

LOVE IT! How about a button similar to

?

[craigharman]

My vote would be for per collection.
Per user persistence would be great.

[nalognl]

Any progress here ?

We use Directus as CRM system and redirect after every client card or deal change is very annoying for users.

Users are mainly regural managers and it is hard to explain to them about 3 dots option button, the just forget and complain about redirect.

Lets make it per collections setting.

Ideal will be to save and refresh page option becasue we use preview.

Such as it is not possible to change button via extention this feature is very urgent for us.

[rolodato]

To me, the facts that CMD/Ctrl + S is the shortcut for "Save and Stay", and that there is no keyboard shortcut for "Save and go back", are a clear signal that the default action should be Save and Stay. Users that mainly use the mouse or touch input (i.e. usually non-technical folks) are left out of this quick convenience, unfortunately.

I would be very curious to see a use case where Save and Stay should not be the default, I really can't think of any other application that behaves this way.

Also, the wording of the Save icon tooltip is deceiving given this default behavior. "Save" in every single application means just Save, and not doing anything else.

[Vahagn-Zaqaryan]

I agree with @rolodato.

Our team is new to Directus, and we're we're loving it. However, we find the current saving logic a bit unintuitive for both technical users and those without a tech background. Given that our team primarily consists of content writers, they found it particularly challenging to adapt to using CMD/Ctrl + S for save and stay.

This issue becomes even more problematic when content writers are working on nested content. Accidental press of the save button leads to a redirection to the collection page of the nested element, which can be very confusing for them.

For my specific scenario, I would appreciate having two levels of control: one that's global and another that's role-based.

Many thanks to the Directus team for your hard work on such an excellent product!

[matiyin]

It's been more than 3 years since this topic started, but still nothing decided?

+1 for per-collection and role-based, otherwise global or 'remember last action' would already be an enormous improvement for editors. If you press ctrl+S when focused inside an input the browser save popups up instead of triggering a save in directus.