TYPO3 Core

I agree. One of first bug reports from clients we got about 9.5-based web sites was regarding the "missing Save&Close" button. Clients use this all the time and missing such button in plain sight is disturbing for them.

Correct me, but isn't this one of the big great changes in 9? You can just click "Close". If anything was changed you will be prompted whether you want to save those changes.

You can even use the tab-Key to switch to save button.

The new Save and close solution in v9 need 2 clicks.
Save and close button need only 1 click.

Daniel Siepmann wrote:

Correct me, but isn't this one of the big great changes in 9? You can just click "Close". If anything was changed you will be prompted whether you want to save those changes.

You can even use the tab-Key to switch to save button.

The Save action is already selected by default, so you can simply hit Return here.

Thank's for the Tipps! I have no problem with it but the editors. Everyone asks for it. :(

+1
More than one single click for Save+Close in inacceptable for most users!

@Daniel Hinderink Siepmann

Correct me, but isn't this one of the big great changes in 9? You can just click "Close". If anything was changed you will be prompted whether you want to save those changes.

You can even use the tab-Key to switch to save button.

Tell this to customers. They will tell you back that they want the save and close button, period. "Close" or not "Close", they want "Save & close". Not everybody there is a tech person. Not everybody wants to click close and then confirm to save. They just want a single click: save & close.

Daniel Siepmann wrote:

You can just click "Close". If anything was changed you will be prompted whether you want to save those changes.

That does not work after editing fields starttime / endtime; just closes without save

I can only agree. Please bring this button back. If not by default at least make it configurable.

+1 for bringing back - why has this been removed at all?

Curiously a similar feature seems to exists on a per-content-element scope?
https://b13.com/de/blog/direktes-speichern-von-neuen-inhaltselementen-in-typo3

the decision to remove the "save and close" button has been already taken and goes in the direction of simplifying the TYPO3 backend

If three clicks instead of one means "simplifying", than I misunderstand the meaning of the "simplifying" word :)

There is a separare ext to get this back in v12, which seems to be popular. There is a discussion here. There are requirements from various customers to get it back. If this is not enough for getting the button back, then it is more like "we did it and we do not care what you think" attitude from the core team than the usability issue.

Removal of this button was someone's idea, not based on any study if the button was used by others or not. That person did not have a use for the button and decided that it should be removed. I believe this is how it was. I never could understand why someone would remove something instead of simply hiding it by default. If it is there, if people use it, why remove it? Why make people disappointed and insist on the bad decision?

Well...

The simplification here was the removal of extra buttons and the complexities of drop-down buttons.

In v13, doing this with a keybord shortcut is IMO a cool way to achieve the functionality without cluttering the UI with buttons and dropdowns. Also, having a popular extension is a good thing and showcases you can make TYPO3 adjust into more than just "how the core team sees it". It helps to foster a community of diverse views and implementations.

Please understand that there are probably as many people wanting it how it is, and they would raise their voices if we canged it back. We cannot satisfy each party, and having changed it and then changing it even again would feel like there is not clean UI line being followed here. What is a bad decission for you, is a good one for someone else.

Each patch for TYPO3 is reviewed and discussed.
Removing the button was NOT the will of a single person, but a combined decission. That's why it's great to be involved in the development process and voicing feedback there; not after the fact. Otherwise, we would not make progress at all.

I hope you can understand. We did not close this lightly. At least 4 people were actively involved in addressing your feedback.

First of all, I know how it works: I was a core team member since 3.7 to 6.2 and the topmost contributor to 4.5 :)

As I wrote: you could hide the button by default and save us (users) a lot of trouble instead of creating such trouble. If the functionality is already there, then it is there for a reason and somebody is using it. Even if 20 core members discuss and decide they think it is not needed, it does not mean that their decision is right because it is just 20 people out of thousands of TYPO3 users. Hide it but do not break it, because somebody else definitely uses it and they will be unhappy. This goes on for years now, and we have to patch every TYPO3 version since this one button was removed. These are hundreds of web sites by the way.

Keyboard shortcuts in this case is neither a cool thing, nor they are a replacement for the button. Editors are usually not technical persons, they often do not even use keyboard shortcuts like ^S in MSWord and having keyboard shortcuts on the web page is neither standard, nor it is a common practice. This is a cool thing technically but absolutely not cool for the usual daily use.

Keeping UI compatible and familar is important if the system wants to be user friendly. Remember when Windows came with all this new cool-new-UI-because-it-is-better? And everybody asked to have the old good "Start" menu back. Nobody wanted this new version and finally MS gave up and brought that Start button back. Suddenly killing something that people actively use, is always a bad idea!

Now compare to Apple, who makes only small steady refiments from version to version, keeping old options hidden or disabled but still available. The system changes but it changes slowly allowing people to get used to it. Updating macOS is simple and safe because you can always turn on old options and turn off new ones. Everybody is happy: new users and old users.

With Save&Close in TYPO3 you could simply hide it and achieve your goal of streamlining the interface by default for new users. And you could have a flag in TSConfig to enable it back for those who used it for years and does not want to lose it.

I wonder, was the solution with TSConfig even considered?..

In any case, you are the core team now and you decide. We will continue patching the core while we can...

I agree with Dmitry, if this button seemed like too much for someone it should have been hidden only optionally (or vice versa).

I also think that the underlying problem is that these X people who make the decisions are most likely developers who never or little operate as editors intensively and so they miss the real needs of a editors. This leads over time to TYPO3 becoming more of a CMS for developers than for editors, and this is a drag on TYPO3's spread.