Bug #15316

ext "version" not loaded : PB with workspace module

Added by Brice BERNARD over 15 years ago. Updated over 7 years ago.

Must have
Target version:
Start date:
Due date:
% Done:


Estimated time:
TYPO3 Version:
PHP Version:
Is Regression:
Sprint Focus:


I've imported the new TYPO3 (4.0beta1b) but (in the backend) when I click on the module WORKSPACE, I see that ext "version" is not loaded as it should.

It's an upgrade not a full install based on dummy package...

TYPO3 Fatal Error: Extension key "version" was NOT loaded! (t3lib_extMgm::extRelPath)
(issue imported from #M2109)

Related issues

Related to TYPO3 Core - Bug #15346: Turn off workspaces module for certain users not possibleClosedDmitry Dulepov2006-01-03

Has duplicate TYPO3 Core - Bug #15664: EXT version not installed but required by WorkspacesClosedKarsten Dambekalns2006-02-18


Updated by Sebastian Kurfuerst over 15 years ago

What happens when you install "version" through the EM? It is shipped with TYPO3 4.0 beta. (Might be a "shy" extension)



Updated by Brice BERNARD over 15 years ago

it worked but I thought this extension should be enable by default...


Updated by Karsten Dambekalns over 15 years ago

While I am in the EM code anyway, what about making version a required ext? This would break TYPO3 on MySQL 3.23.x, so it is not an option. Alternatives: * disable workspace stuff if versioning not loaded or (see also 2160) * make versioning work differently

What is the best way? Dmitry, are you looking into this?


Updated by Sebastian Kurfuerst over 15 years ago


did you consider http://www.wmdb.de/versionfix ? I am not sure if it still works as expected with all the workspaces stuff, but it might be worth a try. We could maybe offer the user on installation which versioning he wants to do - as the performance of version_swapfix is not as good I suppose.

Anyways, if it doesn't work, +1 for disabling workspaces when version is not installed.

Greets, Sebastian


Updated by Dmitry Dulepov over 15 years ago

We talked with Kasper about it some time ago. He said he thinks about changing Version extension to be compatble with 3.23. I do not remember what was decided about Workspace module if versioning is not present. I will take a look at it tomorrow. Probably workspace module will just say that versioning extension is not present, so it cannot continue.

Just having Version extension enabled in the system with mysql 3.23 does not break anything. I [have to] use 3.23 and versioning extension is enabled. I just do not use it.


Updated by Dmitry Dulepov over 15 years ago

...and I will check the patch that Sebasian mentioned too.


Updated by Karsten Dambekalns over 15 years ago

Sebastian, when writing about changing the way versioning works, I was thinking about the wmdb versionfix, indeed.

Is it possible to disable workspace handling at all, in a way that no versions are ever created?


Updated by Dmitry Dulepov over 15 years ago

It is possible to disable workspace module but not wokspace handling. Workspace overlaying and other operations are still performed by core. If I am not mistaken, Versioning exstension is required by only Workspace module. But Workspace module is only a user inteface, it is not required for proper functioning of typo3.


Updated by Michael Stucki over 7 years ago

  • Category changed from Communication to Workspaces

Updated by Michael Stucki over 7 years ago

  • Project changed from 624 to TYPO3 Core
  • Category changed from Workspaces to Workspaces
  • Target version deleted (0)

Also available in: Atom PDF