Conflict between Admin Role and Features

Ok thanks for the report. Was it specific permissions that were not checked?

Ok. Try using the latest version as well, and re-open if its still an issue for you. Thanks for taking the time to report this!

I had the same issue when I enabled 'content permissions' using the 'features' module. Every permission available from the content permissions module was unchecked. Going to user settings and saving checked all the permissions for my admin role.

I am seeing the same problem as reported above. Roles and permissions are being managed with the features. I noticed that some permissions are not checked for the role set by the Admin Role module. I haven't yet checked whether these permissions were from new modules added recently, or if they're from permissions added recently in existing custom modules on the site.

Visiting the user settings page and hitting save set the permissions correctly for the admin role.

The admin role module just assigns the permissions when new modules are added. So it's not going to be able to react to features very well. This is a problem features has with several modules. We *could* introduce something in adminrole to react to a features revert that would run the perm setting.

I'd be open to that kind of patch since features is so prevalent.

Considering admin role got in as its most basic functionality, I assume Features will have the same problem on D7 core. We shouldn't put in a solution that will only work on D6 but then regress again for core.

I'm interested in looking into this, but am not that familiar with D7 yet, and haven't got a lot of time at the moment. If I actually start work on patch(es) I'll update here as I start.