Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Simon Dingley 1474 posts 3431 karma points c-trib
    Sep 17, 2018 @ 11:16
    Simon Dingley
    0

    Missing Actions Menu For Content Nodes

    What is required in order for the Actions menu to be visible to a user group? I have a site that has a custom user group which restricts a particular user groups actions & content/media access but the site also has a custom menu action which they should be able to access but can't because the action menu does not appear?

    The user group has the following permissions enabled:

    Administration

    • Audit Trail

    Content

    • Browse Node
    • Delete
    • Create
    • Publish
    • Update

    Other

    • Custom Action

    Structure

    • Copy
    • Move
    • Sort

    In the umbracoeditormenu.directive.js I see the following:

      var directive = {
         restrict: 'E',
         replace: true,
         templateUrl: 'views/components/editor/umb-editor-menu.html',
         link: link,
         scope: {
            currentNode: "=",
            currentSection: "@"
         }
      };
    

    At a guess, does restrict: 'E' mean that it is restricted to members of the Editor group only? If so I will raise this as an issue on the tracker because it should be more flexible than that in my opinion as you can't assume that all installs want or need to use the OOTB user groups.

    Thanks, Simon

  • Yakov Lebski 590 posts 2344 karma points
    Sep 17, 2018 @ 16:45
    Yakov Lebski
    0

    I guess that 'E' is mean ELEMENT in AngularJS. All permission managed in user/group settings in Umbraco Backoffice

  • Simon Dingley 1474 posts 3431 karma points c-trib
    Sep 17, 2018 @ 20:17
    Simon Dingley
    0

    I guess that 'E' is mean ELEMENT in AngularJS

    OK, so not what I thought - thanks

    All permission managed in user/group settings in Umbraco Backoffice

    Yes, thanks, that is how I configured the above permissions but that doesn't help me solve the problem. Something is causing the entire menu to be hidden despite the group having permissions that should appear in the menu.

  • Simon Dingley 1474 posts 3431 karma points c-trib
    Nov 15, 2018 @ 13:15
    Simon Dingley
    0

    I'm still fighting with this unfortunately. There is another directive umb-editor-header which contains the following:

    <umb-editor-menu
        data-element="editor-actions"
        ng-if="menu.currentNode"
        current-node="menu.currentNode"
        current-section="{{menu.currentSection}}">
    </umb-editor-menu>
    

    If I remove the attribute ng-if="menu.currentNode" then I see the action button but I get no options. Progress of sorts! But...I can't for the life of me find out why this is as the directive is setting menu: '=' and as a result, it stands to reason that it should never be visible?

Please Sign in or register to post replies

Write your reply to:

Draft