• Resolved spacecookie

    (@spacecookie)


    Hi there,

    I currently upgraded to the latest beta and I’m facing some really odd problems.

    1. Menu items are displaced when restricted

    When I restrict access to all areas of an menu item (for example settings) the whole menu gets displaced (http://i.imgur.com/RrZQkDb.png). What’s going on there?

    2. First sub item of each menu item has to be present
    When I manually restrict access of sub menu items, I have to keep the first sub menu item of it public. If I restrict the access to the first sub menu item, the whole item will be restricted.

    3. Properties for almost every plug-in do not exist
    There are no properties in AAM for almost all the plugins I installed. I cannot check their plugins manually. To make plugins available for menu restriction I have to check the “manage options” property (which unfortunately also the configuration item available in the menu restrictions)

    Before upgrading (from 1.9.1) everything worked as it supposed to be.

    http://wordpress.org/plugins/advanced-access-manager/

Viewing 6 replies - 1 through 6 (of 6 total)
  • Hi spacecookie,
    Appreciate your feedback. The issue 3 has been fixed and is going to be included in next release within few days.
    Issue 2 is actually is not issue. Usually the Main menu and first submenu are the same page. That is why if you restrict access to first submenu, it also restrict access to entire menu. Yes, I know that AAM 1.x worked different way, but current 2.0 version is way more closer to WP Core and that is why we are trying to follow the rules.
    Issue 1 is odd. I’ll try to reproduce it. It might be some CSS issues in WP Core. I have to check before confirmation.

    Appreciate your interest in AAM.
    Vasyl

    Thread Starter spacecookie

    (@spacecookie)

    If you leave your e-mail I can mail you some test access data to the website, so you can inspect #1 in detail.

    Regarding #2
    Thanks. That’s indeed true, didn’t even think about that 😀
    Nevertheless it would be cool if that feature could be implemented again.
    I use AAM pretty often to simplify the wordpress backend for our customers. Often I don’t need the first sub-item of an item to be displayed since it’s not meant for the user to be visible (for the sake of simplicity).

    Would it be much effort to implement that feature again?

    Thanks for bringing up this issue. Issue #2 is also very important to our website. It would be greatly appreciated if the menu item could remain while restricting the first item.

    Hi spacecookie,
    It gave us actually a good idea. The problem with AAM 1.x and restricting the first submenu is that when you do that and user click on main menu, the screen “Access denied” is shown. It kind of annoying because user has to click back button and hit on submenu directly.
    So I came up with idea to redirect user to next available submenu if main menu is restricted.
    We will try to implement this feature asap and include in next release.

    Regards,
    Vasyl

    Thread Starter spacecookie

    (@spacecookie)

    So I came up with idea to redirect user to next available submenu if main menu is restricted.

    That’s actually a great idea. I’d love to see it in action

    Hi spacecookie,
    We successfully implemented your idea and it is going to be included in next release. Whether tonight or tomorrow.

    Regards,
    Vasyl

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Menu Items Displaced’ is closed to new replies.