Doesn't work at all on 3.5

Same issue here. I received the error that CameronGilroy and John Brown mentioned above:

Error: cannot call methods on dialog prior to initialization; attempted to call method ‘destroy’

I agree that this is clearly an issue with version 3.5.

If you revert back to 1.6.8 (does that temporarily resolve the issue), until the developer fixes this?

Will give it a go & run a diff to see what is the difference & if it can be fixed!

Yeah garymgordon, I installed v1.6.8 on a wp3.5 install and I didnt have any problems.

This is one of my favourite plugins for WordPress to explicitly configure the clients view and capabilities when i’ve built their site. Really disappointed that this is no longer working with wp 3.5 and really hope the developers fix it soon! Anyone suggest a suitable alternative while they fix it?

I used two plugins as an alternative. I do not think it has all the features but they work just fine for me.

Admin Menu Editor (free version) and
User Role Editor

When used together, you can customize how you would like the dashboard to appear to clients when they log in.

Hi All….
I am getting the same issue with fresh WordPress setup. There is nothing installed neither plugin nor theme. Still getting the issue. It means plugin is not compatible with WP35.

The below trick just displays the hidden components. But, error displaying is the same.

#aam_wrap{
    /*display: none;*/
}

Well, this issue is since some weeks with Version 1.6.8.1.
– – –
First I have installed the AAM to my Dutch customers, with WordPress 3.5 (with the same plugins).
There was no problem. Everything works fine.
– – –
When i installed it to a English customer with WordPress 3.5 (with the same plugins) I had the problems like above.

Below in the footer of the website:

Warning: Invalid argument supplied for foreach() in /home/xxx/domains/xxx/public_html/wp-content/plugins/advanced-access-manager/mvb_wp_access.php on line 434

foreach ($wp_admin_bar->get_nodes() as $node) {
if (!$this->getAccessControl()->getMenuFilter()->checkAccess($node->href)) {
$wp_admin_bar->remove_node($node->id);

When I start AAM:

Error: cannot call methods on dialog prior to initialization; attempted to call method ‘destroy’

I have made a fresh install WordPress (English) (empty) and the first and only plugin I have activated was AAM.
Conclusion: The same Errors like above. So only with English.

Somebody have a explanation?

any update on when a new version is going to be release to work with WP3.5?

I have a blank page for AAM in WP 3.5, and the css file doesn’t seem to show up on the list in the plugin editor. I don’t need to touch the settings though – will it still work the way I had it set before, or are certain user groups now seeing things they’re not supposed to in the admin area on my site?

I agree with cadencehart. Just use those 2 plugins and you pretty much have covered the functionality of this one. And they work perfectly together.

At this point, I would say that this plugin isn’t working with 3.5 at all.

still doesn’t work. css hack helps, but javascript error is still active.
– button ‘restore default settings’ doesn′t work
– MU plugin settings affect single site settings. If I do globale settings, it is a problem for different settings on different single sub-sites of MU

thank you, great plugin. hope it will run again perfectly as we know it so far.

Hello,
I found a trick who works fine for me on a multisite install.

Add a line in YOURPREFIX_options table database for each site :
option_name = YOURPREFIX_wpaccess_first_time
option_value = 1
autoload = yes

I just spoke with the developer and he has updated the plugin to v1.6.8.1 to correct the problem.

You can access the new version at https://www.ads-software.com/extend/plugins/advanced-access-manager/

Please let me know if this resolved your issues.

??
Gary Gordon
https://www.wpbns.com/

Ver: 1.6.8.2
Fixed JS issue with dialog destroy
Last Updated: 2013-1-17

I guess the problem is solved ??
Thanks.