Actions
Feature #15464
closed
setup.override.startInWorkspaceManager=1
Start date:
2006-01-20
Due date:
% Done:
0%
Estimated time:
PHP Version:
4
Tags:
Complexity:
Sprint Focus:
Description
After a few days working in the new fantastic spaces im quite shure, that the workspace manager will become the startingpoint for the work of the most editors. having some
setup.default.startInWorkspaceManager=1
setup.override.startInWorkspaceManager=1
would be great I think.
(issue imported from #M2330)
Updated by old_pekue about 18 years ago
hi kasper,
maybe it could be solved more general with a
setup.override.startInModule
where the value can be an $MCONF['name'] like
setup.override.startInModule = user_ws
just an idea ;)
nice greetings!
peter
Updated by Stefano Cecere about 17 years ago
with 4.1 you can define starting modules...
so this issue could be closed (i guess)
Updated by Michael Stucki about 17 years ago
Yes, Thomas Hempel has recently implemented such a feature.
Updated by Michael Stucki over 10 years ago
- Category changed from Communication to Workspaces
Updated by Michael Stucki over 10 years ago
- Project changed from 624 to TYPO3 Core
- Category changed from Workspaces to Workspaces
- Target version deleted (
0)
Actions