Feature #18994
closedAdd possibility to disable TYPO3 draft workspace by localconf.php configuration
0%
Description
It would be a very useful feature if there would be the possibility to disable the TYPO3 draft workspace by localconf.php configuration.
That could be done by the the localconf.php configuration:
$TYPO3_CONF_VARS['BE']['disableDefaultWorkspace'] = '1';
That could be done by changing the t3lib/config_default.php file to add these option to the install tool with 0 by default. For these change I added the patch config_default_patch.diff.
Furthermore there is a change needed in t3lib/class.t3lib_userauthgroup.php to check these localconf.php option. For these change I added the patch t3lib_userauthgroup_patch.diff
(issue imported from #M8778)
Files
Updated by Jonas Felix over 16 years ago
I tested the patch, it's working great!
Updated by Steffen Kamper over 16 years ago
are you sure that this is the only place to change? Workspace handling is hardcoded at many places in Core.
May be Workspace will be seperated completely from core to sysextension, that would make such patch much more easy
Updated by Benni Mack over 16 years ago
Yes. I would love to see this functionality in a sysextension with a installer-time configuration "Enable Draft Workspace". Anyone willing to do the task?
Updated by Jonas Felix over 16 years ago
@Steffen: There are some areas of course where it's not disabled, like in BE Group and User configuration. But it's enough for my purpose.
The main thing is, that the users (also admin users) never see or use the default workspace. It's often the case that you have one custom workspace "draft" and it's confusing with the default workspace.
We never ever give admin access to regular customers (not developers) but also for developers it's anyoing this default -1 workspace. I would even think about removing it completely, it would be easier to make a sql insert for a default workspace instead of hard coding everything into the core....
Updated by Steffen Kamper over 16 years ago
yes, hiding the entry would be fine.
But i'm not sure what's in the versioning module and other versioning action.
The best solution would be indeed to move all workspace-stuff in a system extension to seperate the hardcoded things from core. Then it should be easy to disable draft workspace. (don't misunderstand, i really appreciate hiding this, but a proper solution would satisfy me more - eg deinstall workspace complete for some installations where it's not needed.)
Updated by Jonas Felix over 16 years ago
@Steffen: Our current solution is working great, we already started 3 new projects and its working. But I understand you.
Workspace is at all a topic which has to be talked about in future, a lot of extensions ignore it and it is realy difficult to implement it in the frontend.
We'll keep it in our core patch extension as one of all the improvments which didn't go into the core :-)
Updated by Steffen Kamper over 16 years ago
be patient - i started with this issue, see here:
http://support.typo3.org/projects/typo3-4-3general/m/typo3-project-4-3-moving-versioning-to-sysextension-350501/p/1/
Updated by Peter Niederlag over 15 years ago
will be fixed in project workspace enhancement http://forge.typo3.org/wiki/typo3v4-workspaces
Updated by Sonja Schubert over 14 years ago
As discussed on the workspace meeting in Wiesbaden I've created a patch (patch-bug8778.diff) which adds an extension configuration file to the version extension and checks in t3lib_userauthgroup if the option in the extension config isset. The option is not set per default which means the draft workspace is not shown per default.
If there are any further changes needed to the diff patch please just tell me.
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)