Feature #10551
closed
Improve handling of non-versionable records
Added by Francois Suter about 14 years ago.
Updated 10 months ago.
Description
When working in a workspace, it is possible to edit records that belong to a table for which versioning is not activated. Upon saving a cryptic error message is shown (see attached screenshot). The least that should be done is to improve the error message so that it explains what the real problem is.
Even better would be to make the records "unmodifyable". See proposed mock-up, which grays out the list display for the problematic table and explains why it is grayed out.
Files
- Status changed from New to Accepted
- Target version set to 4.6
- Assignee set to Oliver Hader
Just to add some thoughts.
Show message if:
!$TCA[$table]['ctrl']['versioningWS_alwaysAllowLiveEdit'] &&
!$TCA[$table]['ctrl']['versioningWS'] &&
!$currentWorkspaceRecord['live_edit']
- Category set to Workspaces
- Project changed from 624 to TYPO3 Core
- Category changed from Workspaces to Workspaces
- Target version deleted (
4.6)
- Target version set to 7.5
- Target version changed from 7.5 to 7 LTS
- Target version deleted (
7 LTS)
- Status changed from Accepted to Under Review
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Related to Bug #101282: Do not inform user about versioning, if workspaces is not installed added
- Status changed from Resolved to Closed
Also available in: Atom
PDF