TYPO3 Core

I've seen the code snippet in the version ext_tables modlue on our test site (4.5.0beta3), and all I can report at this time is that it is not effective to load the version module for users not configured for access to the workspaces module.

I will be willing to research this more thoroughly, but as far as I can tell, some form of call to the modAccess() function would be required to determine the current user's access to the workspaces module.

The reason for this configuration, which we are currently successfuly using in our production 4.4.x site, is that the version module offers a simplified user interface for editors that still allows them to participate in the workflow, since version does present the necessary workflow controls in its UI.

In our case, simpler is definitely better, at least for now. The version capability focuses on changes pending in a single page or folder rather than being global to the workspace and we see that as an advantage for our editors in our use of TYPO3. Even though the new workspaces extension does offer the capability to display changes in a single tree, the automatic selection of infinite as the recursion level is too broad for us, I think.

Well but switching on the old module is not a good option at all - I'd rather make the depth-selection-box configurable than enabling both modules side-by-side.

Mark - is this issue still relevant for you or can we close it?

So how to proceed? Using both side-by-side is no option here.

The "Basic Editor" (non-admin) user is able to add and update items in the workspace, but even with the Workspaces extension enabled cannot see the workflow functionality. I've uploaded two screenshots of the same folder with each logged in that shows the issue.

As mentioned, this behavior is happening on an upgrade of a completely functional workspace from TYPO3 4.4.x to 4.5.0beta3 (actualy the workspace was originally set up in a v4.2.x site that has since been upgraded).

I've tried to set up a new site based on a fresh TYPO3 demo site on 4.5.0beta3, but so far have not been able to achieve successful access by a non-admin user to a configured workspace at all. I don't know of any comprehensive documentation for site administration of the new custom workspace functionality at this stage of its development, so I figured my next steps might most productively be to add a configuration page to the wiki for this project. Whatever missteps I am making can then be commented on, and the result should be a beginning point for the missing documentation.

If you know of any successful non-admin test installation, I'd be glad to try to integrate an export of such into a new 4.5.0beta3 install to 1) verify that I can make it work, and 2) if it is working, identify how it is different from the way I have been trying to do it.

What has all this to do with "Web>Versioning"? This seems to be a bug - but bringing up "Web>Versioning" is totally wrong at this point.

Well, I'm focusing on the non-admin user aspect of the report, but you are focusing on the Web->Versioning aspect. The bottom line is that there are currently problems for non-admin users to use the new workspaces functionality. If that should be a new issue report, I'd be up for that.

There should eventually be some written documenation that clarifies how upgrades to Workspaces 4.5 should be administered with the changes being introduced compared to earlier versions of TYPO3, since this is one example of how a successfully operating configuration may break on the upgrade. If that's already planned in a separate action (and I will be happy to contribute if I can be helpful), this ticket can be closed.

Well showing "Web>Versioning" was your request - the fact that there might be a bug within the existing module wasn't really mentioned in your first reports. I'm going to open a new bugreport. This one is too long to motivate others to look at it ;)