Feature #16365
closedmake workspaces an extension
0%
Description
Versioning is part of the Core but the UI is optional (as an extension). It should be the same for WSs. If you don't need it, then you don't load.
(issue imported from #M3872)
Updated by Thorsten Kahler over 18 years ago
+1
WS are one of the few "features" of TYPO3 that can't be disabled (ok, you can hide the "shortcutFrame" for BE users or BE groups completely - which causes collateral damage). And it's overly buggy and insufficient. IMHO it's often a show stopper for a version upgrade.
Updated by Andreas Wolf over 18 years ago
+1
Edit: I just wonder if any of you has ideas on how this should look like... Ok, it's clear to move the module "user->workspace", the box at the bottom right to the extension. But what about the workspace-records? What else would have to be moved?
Updated by Dmitry Dulepov over 18 years ago
Andreas, workspace records can be created only on the Globe level, so they are visible to admin user only. In any case, they should not be edited directly but through the workspace module!
Updated by Andreas Wolf over 18 years ago
Dmitry,
I meant whether the creation of workspace-modules (and thus the table which contains the records) would have to be moved to an extension or not. As the two default workspaces (live and draft) are internal and don't have a matching database-record, I would suggest moving the table to the extension.
Updated by Michael Stucki almost 11 years ago
- Project changed from 624 to TYPO3 Core
- Category changed from Workspaces to Workspaces
- Target version deleted (
0)