Actions
Bug #11824
closed
Workspaces extension should respect $TYPO3_CONF_VARS['BE']['disableDefaultWorkspace'] configuration
Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
Workspaces
Target version:
-
Start date:
2011-01-01
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
When upgrading from TYPO3 4.4.x to 4.5beta, with configuration [disableDefaultWorkspace] value of 1, the workspace migration (necessary for migrating an existing custom workspace with fixed workflow) also added the default Draft workspace and made it visible in the backend. The [disableDefaultWorkspace] configuration should either suppress the creation of the Draft workspace or cause it to be not available in the backend.
Updated by Tolleiv Nietsch almost 14 years ago
- Status changed from New to Rejected
Nope - the "Draft" workspace which is created during the upgrade is a "regular" workspace which supports the full workspace-featureset. It is created to "rescue" the records which are related to the old "Draft" (a.k.a uid=-1) workspace which doesn't is deprecated.
Updated by Michael Stucki almost 11 years ago
- Project changed from 624 to TYPO3 Core
- Category changed from Workspaces to Workspaces
Actions