Task #8688
Instead of OK/Cancel buttons, use Commit?
| Status: | Resolved | Start date: | 2010-07-06 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Sebastian Kurfuerst | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - |
Description
To me, it is not yet clear how the OK/Cancel buttons (shown when editing page properties) play together with the "Commit"-feature when you edit content.
There are several possibilities I think:
- After pressing "OK", the changes are on the live site
- After pressing "OK", the change still needs to be committed.
- get rid of the OK/cancel buttons altogether and instead display the "commit" button like when editing content
The same issue occurs when deleting a page: Is it still needed to commit this change?
Related issues
History
#1 Updated by Sebastian Kurfuerst about 5 years ago
- Category set to User Interface
#2 Updated by Jens Hoffmann about 5 years ago
- Assigned To deleted (
Jens Hoffmann)
As discussed via Skype in the Daily Scrum:
- NEVER, push something to the live site >> Everything need to be committed through a workflow process
- Remove the "OK/cancel" BTN for all Properties dialogs >> Use Version Comment Dialogs instead!
- Hide the Dialog by clicking to the Content Frame below or any Menu Icon
#3 Updated by Robert Lemke about 5 years ago
- Status changed from New to Needs Feedback
- Assigned To set to Sebastian Kurfuerst
question answered?
#4 Updated by Sebastian Kurfuerst about 5 years ago
- Status changed from Needs Feedback to Resolved
yes.
#5 Updated by Robert Lemke about 4 years ago
- Project changed from Core Team to Base Distribution
- Category deleted (
User Interface) - Target version deleted (
593)
#6 Updated by Robert Lemke almost 3 years ago
- Project changed from Base Distribution to TYPO3.Neos