Please Log in to join the conversation.
Please Log in to join the conversation.
Please Log in to join the conversation.
A database query can't communicate with PHP. The authorization API is PHP based and due to its dynamic nature and extensibility via trigger it'd be impossible for it to be anything but PHP based.Why can't the query include access permissions in the first place?
Sorry, I understand your frustration and have already created a bug ticket to address the issue. Like I said you can edit the module (it is open source) and replace the access check with array() and it'll show them regardless of permissions.Eventually, I expect the number of groups to change on a daily basis... I need to be able to control how many are displayed in specific places of the site for layout purposes. As it is, this module does not work as expected.
Please Log in to join the conversation.
That's not really possible since we already have groups which are supposed to be hidden from the public and from most other members.krileon wrote: Sorry, I understand your frustration and have already created a bug ticket to address the issue. Like I said you can edit the module (it is open source) and replace the access check with array() and it'll show them regardless of permissions.
Please Log in to join the conversation.
Unpublished isn't, like I said it's a bug and will be reviewed and fixed for next release. Patches for a fix are welcome of course if you'd like to take a look in the meantime.One thing I just realized: the offending groups which are preventing the right ones from being displayed aren't even published yet. It's unfortunate that "unpublished" is an access level rather than its own database field.
Please Log in to join the conversation.