WordPress.org

Forums

Advanced Access Manager
[resolved] Version 2.1.1 Upgrade Shows No Users or Roles (21 posts)

  1. cjanteater
    Blocked
    Posted 1 year ago #

    After upgrading this plugin, which is a great plugin, everything works fine, except Users and Roles are not loading up, and I and getting a lot of JavaScript errors like:

    • Uncaught Error: cannot call methods on tooltip prior to initialization; attempted to call method 'Manage'
    • Uncaught Error: cannot call methods on tooltip prior to initialization; attempted to call method 'Filter Posts by Post Type'
    • Uncaught Error: cannot call methods on tooltip prior to initialization; attempted to call method 'Add Event'
    • Uncaught Error: cannot call methods on tooltip prior to initialization; attempted to call method 'Delete'
    • Uncaught Error: cannot call methods on tooltip prior to initialization; attempted to call method 'Unlock Default Accesss Control'

    Is there any other way to resolve this without having to deactivate other plugins, as other plugins are needed as well, and I cannot disable them on our site? Can someone provide an explanation of what is going on? Is this a jQuery conflict? Does the developer of AAM, plan on fixing this in the next update?

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

  2. WP AAM
    Member
    Plugin Author

    Posted 1 year ago #

    Hi cjanteater,
    Please check this topic http://wpaam.com/forum/viewtopic.php?f=6&t=3

    Regards,
    Vasyl

  3. cjanteater
    Blocked
    Posted 1 year ago #

    Vasyl,

    Thanks, but I don't see how that is helpful to me????

    Is there any suggestion as to why this error is occurring in the Javascript?

    Do you plan on fixing this issue in the next upgrade?

    Is this a jQuery or other Javascript issue?

    The errors that come up are very difficult to discern.

    I am a developer and can manage this on my own, if you can supply a reasonable answer. If you cannot provide me with some feedback, I will change to another plugin. This is pretty much a frustrating way to have to go about fixing a plugin that doesn't work 100%.

  4. WP AAM
    Member
    Plugin Author

    Posted 1 year ago #

    Hi cjanteater,
    The problem is that there is some other plugin or your theme the prints redundant jQuery. AAM uses the WordPress default jQuery library. Unfortunately there are some developers who does not understand the WordPress Core abilities and print scripts and styles that affect other plugins. There is nothing we can do to fix it.
    Our development practice is simple - if _GET['page'] == 'aam' then print whatever we need to support AAM.
    Not everyone does this.

    I hope this is helpful.
    Regards,
    Vasyl

  5. cjanteater
    Blocked
    Posted 1 year ago #

    There is a way to create non-conflicts, and still use jQuery from WordPress. I refer you to this: http://api.jquery.com/jquery.noconflict/

    It would behoove you to use it, so that regardless of conflicting scripts from other plugins, this will avoid it. Have you tried that?

  6. WP AAM
    Member
    Plugin Author

    Posted 1 year ago #

    Hi cjanteater,
    I will.

    Also thank you for your honest rate even if we do not believe it worth one star.

    Best regards and good luck.
    Vasyl

  7. cjanteater
    Blocked
    Posted 1 year ago #

    So I disabled all other plugins and still the same errors appears, and still no User or Role list. I have no way to manage my users!

  8. WP AAM
    Member
    Plugin Author

    Posted 1 year ago #

    Then it might be your theme. I'm sure you are not using the default WordPress theme.

  9. cjanteater
    Blocked
    Posted 1 year ago #

    No, I am not. We use a custom theme I built myself. I am also noticing a lot of errors are due to JQMIGRATE issues, which means a lot of the jQuery code you use is not up-to-date with the current version of WordPress' jQuery. Below are the migration warnings given right before each of the Uncaught Errors:

    • JQMIGRATE: jQuery.fn.attr('selected') may use property instead of attribute: for AAM.initCapabilityTab(); AAM.initSettings(); and jQuery.ajax.success() in the aam.js file
    • JQMIGRATE: jQuery.fn.attr('checked') may use property instead of attribute: for blogTables.capabilities.jQuery.dataTable.fnRowCallback() in aam.js

    If you're using WordPress' native jQuery instance, then your javascript is not full y compatible with it, and WordPress' JQMIGRATE handler is catching these.

  10. WP AAM
    Member
    Plugin Author

    Posted 1 year ago #

    cjanteater,
    We are using the jQuery that WordPress offers. Check the aam.php file.

    Ok. So you are using custom theme. Switch to Default WordPress theme Twenty Thirteen and let me know if you see any difference.

    Regards,
    Vasyl

  11. cjanteater
    Blocked
    Posted 1 year ago #

    Right. If you're using the current WordPress jQuery instance, which I agree you are, then you have incompatible code in AAM's javascript.

    I am in the process of hunting down other instances of jQuery in my code, but I know for sure we do not use another instance as we also use the current WordPress instance of jQuery as well. Besides there are other jQuery instance in your plugin that are working, so I suppose that it is a compatibility issue.

  12. WP AAM
    Member
    Plugin Author

    Posted 1 year ago #

    I will check too but as far as I remember we do not create any new instance of jQuery.

    Let me know if you'll find anything.
    Thanks,
    Vasyl

  13. cjanteater
    Blocked
    Posted 1 year ago #

    That's not what I was saying. I was saying that your javascript code, which uses the current WordPress instance may not be fully compatible with it. That's why WordPress devs went through the trouble of building a jQuery migration tool, so that other plugin devs could bring there jQuery code up-to-date.

    Anyhow I resolved it. I had an instance of jQuery UI that includes some features that WordPress doesn't include. So I simply turned off the script queue if we are on the AAM admin page.

  14. leadspringadam
    Member
    Posted 1 year ago #

    Hi,

    We're having the same issue. It's working fine on one site but then unable to access users or rolls on another. I'll try deactivating plugins as suggested.

  15. WP AAM
    Member
    Plugin Author

    Posted 1 year ago #

    Hi leadspringadam,
    We will try to come up with solution asap. I believe cjanteater has a good point. We will try to isolate AAM from other scripts & styles.

    Regards,
    Vasyl

  16. Lisa
    Member
    Posted 1 year ago #

    Same problem here even with all other plugin's deactivated.

  17. cjanteater
    Blocked
    Posted 1 year ago #

    Lisa,

    You may want to check your theme, if it is custom. I have to use some elements of jquery-ui that aren't avaialble in the WordPress instances of jquery-ui, and I discovered that it conflicts with whatever elements AAM is using. This can be resolved by not using the same namespace as WordPress does for jquery (it uses jQuery.())

    The best way to avoid jquery conflicts is either use jQuery.noConflict() in a plugin instance, or in your own instantiation of jQuery, provide a custom namespace variable

    i.e.

    jQuery(function($my) {
        $my('#selector').css({...});
    });
  18. WP AAM
    Member
    Plugin Author

    Posted 1 year ago #

    Thank you cjanteater for input.

    Lisa, I have on my schedule to resolve the conflicts tonight. I'll keep you updated.

    Best Regards,
    Vasyl

  19. WP AAM
    Member
    Plugin Author

    Posted 1 year ago #

    Hi Lisa & cjanteater,
    Please try the Development Version.
    I believe the problem was with attribute "tooltip" which is also used by jQuery UI Tooltip widget.

    Please let me know if it works for you guys.
    Vasyl

  20. Lisa
    Member
    Posted 1 year ago #

    Vasyl,

    Thanks for your work on this. I tried the Dev version, but didn't see any change in the end result. it's still a mostly blank access control page (this matches the screenshot in the post from Cristina. I looked for errors in the error console, but there's just a bunch of the usual css warnings, declaration dropped.

    Here's what I'm using:
    theme: twenty twelve, no customization
    all plugin's deactivated

    I was able to roll it back with a copy of the 2.1 version of the plugin and everything worked fine.

    Lisa

  21. WP AAM
    Member
    Plugin Author

    Posted 1 year ago #

    Hi Lisa,
    I'm sure that this is the same problem as it is discussed here: http://wordpress.org/support/topic/access-control-is-broken?replies=12

    Please read my reply and let me know that this is helpful.

    We are looking forward to resolve this but we do not have enough information why this is happening in your system.

    Regards,
    Vasyl

Topic Closed

This topic has been closed to new replies.

About this Plugin

  • Advanced Access Manager
  • Frequently Asked Questions
  • Support Threads
  • Reviews

About this Topic