TYPO3 Core

To make it complete ("clean up" the whole menu) it would be nice to also have "More Options..." disabled e.g. by
options.contextMenu.pageTree.disableItems = moreoptions,[...]

Modify function main in class tx_extrapagecmoptions (/typo3/sysext/extra_page_cm_options/class.tx_extrapagecmoptions.php, line 86)
change

// Detecting menu level
if (!$backRef->cmLevel) [...]

into

if (!in_array('moreoptions',$backRef->disabledItems) && !$backRef->cmLevel) [...]

Or to make it easier, remove the Versioning menu item if the user has no access to the Versioning module.

But of course, a general option to disable page contect menu options (on a per user/grpu basis) are a fine thing.

Versioning context menu is displayed even if the user/group has no access to the versioning module.

Added two patches to address versioning and moreoptions removal from context menu

Changes have been described by Karl-Ernst Kiel. I have provided the diffs and testet it on several sites.

For me this seems to be a nobrainer, so I would be happy if it will be included in 4.0.4

Although the core docs have to be updated, I do not consider this to be a new feature but rather a bugfix.

Sincerely
Helmut Hummel

would have been nice it this one would have made it into 4.1 as it a useabillity-bug to me - and really easy to fix :(

it'll be also nice if the second menu-level of the moreoptions could be disabled, so that hiding/unhiding, pageproperties etc. are still available.

set: options.contentMenu.pageTree.disableItems = moreoptions_extended

and modify function main in class tx_extrapagecmoptions (/typo3/sysext/extra_page_cm_options/class.tx_extrapagecmoptions.php, lines 93 to 99):
---- from ------------------------
$localItems['moreoptions']=$backRef->linkItem(
$GLOBALS['LANG']->makeEntities($LANG->getLLL('label',$LL)),
$backRef->excludeIcon(''),
"top.loadTopMenu('".t3lib_div::linkThisScript()."&cmLevel=1&subname=moreoptions');return false;",
0,
1
);
-------------------------------
---- to------------------------
if(!in_array('moreoptions_extended',$backRef->disabledItems)) {
$localItems['moreoptions']=$backRef->linkItem(
$GLOBALS['LANG']->makeEntities($LANG->getLLL('label',$LL)),
$backRef->excludeIcon(''),
"top.loadTopMenu('".t3lib_div::linkThisScript()."&cmLevel=1&subname=moreoptions');return false;",
0,
1
);
}
-------------------------------

just a reminder...
would be nice 4.1.2

I'd appreciate it if we could have this in 4.1.2 guys, seems quite simple and if you have users who you don't want to use versioning it's really quite essential.

Hi Thorsten, I think you can commit this now...

What about the item "send to review/pub"? Shouldn't it also be possible to remove that one?
BTW: sorry if this is a stupid question but i couldn't find out anything about it and if its true that should also be corrected in the core docs, i think the "perms" item listed in the TSConfig has no function?

thanks for patch.
------------
comments to tx_extrapagecmoptions patch:
1) (it disables all extra click items):
it would be fine if it is possible to only deny the "more options..." items (means only the clickmenu-submenu) - without disabling all other items in the clickmenu.

2) we should also add permission check for the "mount as treeroot" item.

e.g. a
if (!in_array('mounttreeroot',$backRef->disabledItems)) before
$localItems['perms'] = $backRef->DB_tempMountPoint($uid);

Thorsten has committed a fix for this now (committed to TYPO3_4-0, TYPO3_4-1, Trunk).
The versioning module is no longer visible if the user has no access to it.

After all, I don't see a reason why this should still be configurable, so I ask if this issue can be closed now?

Hi Michael, good news :)

But:

Not showing the versioning button in clickmenu, when the user hasn't access to it is one thing. To have the possibility to disable the item, like any other item in the clickmenu is something different. And in addition there is the request to have the possibility to disable moreoptions item.
So I don't consider this issue as resolved.

Yes, but then it's just a new configuration feature which is not at all related with versioning. So maybe someone should update the bug description or (even better) create a new bug record.

Sorry, just changed my mind! ;-) Of course the feature does already exist, I just didn't find it because the term "disableItems" is splitted over two lines in TSconfig.

So forget my last comment, the bug remains open.

Patch attached on 14.09.08 was committed to trunk in revision 4113.