http://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692013-09-19T10:27:50ZTYPO3 ForgeTYPO3 Core - Feature #52090: Merge Save Buttonshttp://forge.typo3.org/issues/52090?journal_id=1834282013-09-19T10:27:50ZPhilipp Gampephilipp.gampe@typo3.org
<ul></ul><p>According to the UX ticket, the last state needs to be saved.</p>
I would prefer a setting in the backend user settings for this:
<ul>
<li>last state (default=</li>
<li>save</li>
<li>save and close</li>
<li>save preview</li>
<li>save and new (save and close)</li>
</ul>
<p>If save and new does not exists, then the button should fallback to save and close as this is the most matching behavior.</p>
<p>What do you thing?</p> TYPO3 Core - Feature #52090: Merge Save Buttonshttp://forge.typo3.org/issues/52090?journal_id=1857912013-10-10T16:44:00ZMathias Brodalambrodala@pagemachine.de
<ul></ul><p>This change would also finally make at least one of those buttons usable by vastly increasing its hit area.</p> TYPO3 Core - Feature #52090: Merge Save Buttonshttp://forge.typo3.org/issues/52090?journal_id=1863142013-10-12T17:05:48ZXavier Perseguersxavier@typo3.org
<ul></ul><p>I like the idea.</p>
<p>UX Question: would the last option be automatically selected as default option next time?</p> TYPO3 Core - Feature #52090: Merge Save Buttonshttp://forge.typo3.org/issues/52090?journal_id=1915332013-11-25T00:33:15ZErnesto Baschnyeb@cron.eu
<ul><li><strong>Status</strong> changed from <i>Accepted</i> to <i>On Hold</i></li><li><strong>Target version</strong> changed from <i>6.2.0</i> to <i>7.0</i></li></ul><p>This should be tackled for future TYPO3 versions.</p> TYPO3 Core - Feature #52090: Merge Save Buttonshttp://forge.typo3.org/issues/52090?journal_id=2237222014-07-10T18:04:24ZChristian Toffolo
<ul></ul><p>There should be the possibility (configurable) to hide the label(s) of the button(s) or else the clutter will be nearly the same as the 4 buttons inline.</p> TYPO3 Core - Feature #52090: Merge Save Buttonshttp://forge.typo3.org/issues/52090?journal_id=2332342014-10-20T00:01:07ZFelix Kopp
<ul></ul><p>I vote for the merge by reducing down to one button: Save and close.</p>
<p>Save+Preview can be done after Save+Close with the preview icon in docheader of page or folder.<br />Also frontend editing should be used to preview.</p>
<p>Also Save+new can be done directly afterwards with one more click.</p>
<p>It will help users to return to the context focus after close to gather the thoughts and start the next step.<br />Any objections?</p> TYPO3 Core - Feature #52090: Merge Save Buttonshttp://forge.typo3.org/issues/52090?journal_id=2332452014-10-20T08:57:32ZMathias Brodalambrodala@pagemachine.de
<ul></ul><p>Felix Kopp wrote:</p>
<blockquote>
<p>I vote for the merge by reducing down to one button: Save and close.</p>
</blockquote>
<p>Yes, at least "Save" alone doesn't serve much purpose. Actions which need saving once already (e.g. plugin selection) ask for and trigger it itself.</p>
<blockquote>
<p>Save+Preview can be done after Save+Close with the preview icon in docheader of page or folder.</p>
</blockquote>
<p>This strongly depends on the workflow. Some people open the page to preview in advance, some start after saving once. Thus I'd vote for keeping this one.</p>
<blockquote>
<p>Also frontend editing should be used to preview.</p>
</blockquote>
<p>People are used to editing in backend and viewing in frontend and I guess this will stay unless FE editing is overhauled a bit to get closer to Neos.</p>
<blockquote>
<p>Also Save+new can be done directly afterwards with one more click.</p>
<p>It will help users to return to the context focus after close to gather the thoughts and start the next step.</p>
</blockquote>
<p>I can only halfly agree with this one. Yes, the loss of context hurts the editing experience and forces you to stop and think sometimes but a huge advantage is using values of the previous record as default values for the next one (TCA <code>useColumnsForDefaultValues</code>). Configured correctly this can speed up record creation massively and should be kept under all circumstances.</p> TYPO3 Core - Feature #52090: Merge Save Buttonshttp://forge.typo3.org/issues/52090?journal_id=2423202014-12-23T19:48:22ZMathias Schreibermathias.schreiber@typo3.com
<ul><li><strong>Target version</strong> changed from <i>7.0</i> to <i>7.1 (Cleanup)</i></li></ul> TYPO3 Core - Feature #52090: Merge Save Buttonshttp://forge.typo3.org/issues/52090?journal_id=2618252015-06-15T17:45:09ZBenni Mackbenni@typo3.org
<ul><li><strong>Target version</strong> changed from <i>7.1 (Cleanup)</i> to <i>7.4 (Backend)</i></li></ul> TYPO3 Core - Feature #52090: Merge Save Buttonshttp://forge.typo3.org/issues/52090?journal_id=2701722015-08-05T10:46:09ZSusanne Moogsusanne.moog@typo3.org
<ul><li><strong>Target version</strong> changed from <i>7.4 (Backend)</i> to <i>7.5</i></li></ul> TYPO3 Core - Feature #52090: Merge Save Buttonshttp://forge.typo3.org/issues/52090?journal_id=2773742015-09-24T11:28:55ZBenni Mackbenni@typo3.org
<ul><li><strong>Target version</strong> changed from <i>7.5</i> to <i>7 LTS</i></li></ul> TYPO3 Core - Feature #52090: Merge Save Buttonshttp://forge.typo3.org/issues/52090?journal_id=2816202015-10-14T22:01:28ZMathias Schreibermathias.schreiber@typo3.com
<ul><li><strong>Status</strong> changed from <i>On Hold</i> to <i>Resolved</i></li></ul><p>fixed with ModuleTemplate API</p> TYPO3 Core - Feature #52090: Merge Save Buttonshttp://forge.typo3.org/issues/52090?journal_id=3464312017-10-21T17:45:04ZRiccardo De Contardierredeco@gmail.com
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul>