AttackMonkey Custom Menus

New in Version 2.2:

Updated the package so that it now workjs with newer vewrsions of 7. This fixes the issue where the menu items weren't rendering correctly, and the actions weren't firing right.

New in Version 2.1:

Updated so that you can target media/content root nodes and remove menu items. To target a root node, set the node id to "-1" and the DocType Alias to eith "media" or "content", and then set the remove menu items as normal.

New in Version 2.0:

Updated for v7!!! This version will not work in earlier versions, for v4/6, use version 1.5. No new features, just ports existing functionality to the v7 API and Angular back office.

New in Version 1.5:

Fixes and issue where create and delete were being set to RelationType instead of content in newer versions of Umbraco.

New in Version 1.4:

Fixes an issue where create and delete weren't getting removed from menus if they were set in removeMenuItems on 4.11+.

New in Version 1.3:

Minor performance tweaks, addition of custom method which allows you to apply the rules to your own menu nodes if required (say if you were building your own tree).

New in Version 1.2:

You can now set context menu items to be removed, by specifying a comma separated list of menu items to remove in a property called "removeMenuItems" in the config file (see included config file for example). Note: If you have normal "menuItems" rules, those cause ALL items to be removed first, which means you don't need to set the "removeItems" property.

To update, just replace the old DLL with the one from the new package and you're good to go, no other changes required.

New in Version 1.1:

You can now make it so that members of the administrator group see the "normal" menus instead of your custom ones, by setting the new config value "ignoreForAdmin" to "true".

You can also make the rules be applied to the media section as well, by setting the new config value "useInMediaSection" to "true".

If you are updating from a previous version, just replace the DLL and add the two new values to the customMenus.config file (see the example config in the package for the defaults).

--------------

It's quite a common practice to set up a "settings" area in your back office in Umbraco. This is a set of nodes that contain site settings for things like copyright notices, rotating images for homepages and the like. These are just for admin purposes and are not displayed on the front end.

The last thing you want is to get a call from a client saying "errr, you know that settings section, I kinda deleted it. And emptied the recycle bin". Noooooo! You could set the node permissions for individual users, but you have to do it each time a new user is added. You could also code a custom event handler that would remove the menu items based on nodeId/DocType. But what if you can't code C#, or you just don't wanna?

This package allows you to set up rules to override the default menus on nodes within the content tree, based on either docType or node id. Using this package its possible to:

• Remove all menu items from certain nodes
• Only have certain menu items for certain nodes
• Overide the click action for the node (so they can't edit the properties for example)