Basically, when a user selects a location, I want them to see the content dashboard and only have the ability to right click the node and choose "create".
Not sure what you're trying to do above? Is this something you're trying to lace in the web.config?
The user permissions in the context menu should be handled in the users section under "user permissions" for the created user. Here you can make sure they can simply just create nodes. Make sure that both "Create" and "Browse" nodes are checked. If they're not allowed to browse a node they can't see it
Unfortunately, I just don't seem to be getting the desired effect :(
I've seperately configured the permissions to only allow my users "create" and "publish" functions, but in my right click menu's, they are still able to do an audit trail, reload nodes and notifications. I'm hoping to use this package to remove those.
Sorry I didn't get back to you earlier, been off today! Are you running the latest version? When you say its not working, is it doing any of it (click action or menu items), or is nothing happening at all?
The DocTypeAlias is case sensitive, so be sure to check the casing, can you get it to work with a nodeId or other doctypes?
Let me know and I'll look into this and see if I can repro!
No worries at all and thanks for getting back to me. I've been trying to reply using iPhone and iPad over the holidays, but for some reason it wouldn't work :(. Back on the laptop now.
I downloaded the zip file earlier in the day from 'our' so I guess it's the latest version. Installed it in a 4.7.1 instance that has no other packages installed, just some base content that we've put in to it.
There's a document type called Location which has document types of Status published within it. The idea is to allow an open/closed status to be published against different offices.
All I've done to the config file since the install is add the line that I've put in the first forum post. Unfortunately I don't see any results at all.
I am worried though that there's something wrong with the permissions structure of my install. The logged in user doesn't have permission to the 'Audit Trail', but they still get the context menu item and can use it. I'm assuming they shouldn't have? Unless this is an error with the 4.7.1 version?
I'm going to install another fresh install and test that out first to see if I can replicate that more fundamental issue. It may not be a problem with the package and more with my install :-)
If it's a permissions thing, its possible that the DLL wasn't copied to the bin folder maybe? Have a look in there for the file "Attackmonkey.CustomMenus.dll". If that's not there, then copy it in from the package zip and you should be good to go! I've just tested on a fresh 4.7.1 install, and it seems to be working OK, so it could be the DLL not being there maybe?
I've put the package into a fresh install of 4.7.1 and it works a treat, no problems whatsoever.
So, I can only assume I've messed something up with my main install. When I first set it up, it was running in a virtual directory called "status" (which I know is not strictly a supported model), but I've since moved it out into it's own website.
I'm guessing that going through that process, something hasn't quite settled properly. When I first installed the package, it tried to install the files to /status/bin and /status/config rather than just /bin and /config. I've been copying them back into the right locations (which seems to "refresh" the app as you'd expect), but I guess it's not enough. I'll see what I can find out about why it's retaining knowledge of the vdir first.
If I ever get to the bottom of it, I'll post back here for the benefit of anyone reading this. I may just have to install a fresh version and migrate into it.
No worries! please do let me know if you get to the bottom of it, that way if there's anything I can add to the package to account for the problem, I will!
Does this work with 4.7.1?
Hi,
Having a little difficulty getting this to show just the "create" menu item on a "Location" document type using the rule:
<add docTypeAlias="Location" nodeId="" clickAction="javascript:UmbClientMgr.appActions().openDashboard('content');" menuItems="create" />Basically, when a user selects a location, I want them to see the content dashboard and only have the ability to right click the node and choose "create".
Thanks
Hi Richard
Not sure what you're trying to do above? Is this something you're trying to lace in the web.config?
The user permissions in the context menu should be handled in the users section under "user permissions" for the created user. Here you can make sure they can simply just create nodes. Make sure that both "Create" and "Browse" nodes are checked. If they're not allowed to browse a node they can't see it
Hope this helps.
/Jan
Hi Jan,
I've installed the "Custom Menu" package from Tim (http://our.umbraco.org/projects/backoffice-extensions/attackmonkey-custom-menus) into a 4.7.1 instance and the code above has been put into the /config/customTree.config file.
Unfortunately, I just don't seem to be getting the desired effect :(
I've seperately configured the permissions to only allow my users "create" and "publish" functions, but in my right click menu's, they are still able to do an audit trail, reload nodes and notifications. I'm hoping to use this package to remove those.
Rich
Hi Rich
Ah, sorry I did'nt notice where the post was placed. My bad.
I'm not sure how to solve this issue then.
/Jan
Hi Rich,
Sorry I didn't get back to you earlier, been off today! Are you running the latest version? When you say its not working, is it doing any of it (click action or menu items), or is nothing happening at all?
The DocTypeAlias is case sensitive, so be sure to check the casing, can you get it to work with a nodeId or other doctypes?
Let me know and I'll look into this and see if I can repro!
Hi Tim,
No worries at all and thanks for getting back to me. I've been trying to reply using iPhone and iPad over the holidays, but for some reason it wouldn't work :(. Back on the laptop now.
I downloaded the zip file earlier in the day from 'our' so I guess it's the latest version. Installed it in a 4.7.1 instance that has no other packages installed, just some base content that we've put in to it.
There's a document type called Location which has document types of Status published within it. The idea is to allow an open/closed status to be published against different offices.
All I've done to the config file since the install is add the line that I've put in the first forum post. Unfortunately I don't see any results at all.
I am worried though that there's something wrong with the permissions structure of my install. The logged in user doesn't have permission to the 'Audit Trail', but they still get the context menu item and can use it. I'm assuming they shouldn't have? Unless this is an error with the 4.7.1 version?
I'm going to install another fresh install and test that out first to see if I can replicate that more fundamental issue. It may not be a problem with the package and more with my install :-)
I'll feedback as soon as poss.
Cheers
Rich
Hiya,
If it's a permissions thing, its possible that the DLL wasn't copied to the bin folder maybe? Have a look in there for the file "Attackmonkey.CustomMenus.dll". If that's not there, then copy it in from the package zip and you should be good to go! I've just tested on a fresh 4.7.1 install, and it seems to be working OK, so it could be the DLL not being there maybe?
Let me know how you get on!
:)
Hi Tim,
I've put the package into a fresh install of 4.7.1 and it works a treat, no problems whatsoever.
So, I can only assume I've messed something up with my main install. When I first set it up, it was running in a virtual directory called "status" (which I know is not strictly a supported model), but I've since moved it out into it's own website.
I'm guessing that going through that process, something hasn't quite settled properly. When I first installed the package, it tried to install the files to /status/bin and /status/config rather than just /bin and /config. I've been copying them back into the right locations (which seems to "refresh" the app as you'd expect), but I guess it's not enough. I'll see what I can find out about why it's retaining knowledge of the vdir first.
If I ever get to the bottom of it, I'll post back here for the benefit of anyone reading this. I may just have to install a fresh version and migrate into it.
In the meantime, many thanks for your help :-)
Rich
Rich,
No worries! please do let me know if you get to the bottom of it, that way if there's anything I can add to the package to account for the problem, I will!
:)
is working on a reply...