Can't Assign Author to Gallery

Hi!

I’m running into a problem with NextGen where I cannot assign a user as the author of a specific gallery if the author is not in one of the default WordPress roles (Contributor, Author, Editor or Administrator). I use Justin Tadlock’s Members plugin to control the capabilities of users and on many of those sites, I have to create personalized roles with specific sets of capabilities that are different from any of the default roles. This system is especially important for me on a largish mulsite network install that I manage. In the site, a number of artists-painters have their own separate sites on the network.

The problem I have is that, when I open a specific gallery page on a user site (when logged as a superadmin), users with roles other than the WordPress defaults never appear in the “Author” drop down list. This means that, if I make edits to the gallery and save, the gallery author “property” gets reassigned to the first user with a default role in the list (usually an admin).

If the user itself edits their gallery, the same problem happens as I had to give them the “NextGEN Manage others gallery” capability with Members since, as an admin, I often have to get in a users gallery to make changes or fix something they have done and that the gallery author usually gets set to me. If they didn’t have the “NextGEN Manage others gallery” capability, they wouldn’t be able to access some of their galleries.

But now I’m working on a quote for another site but that one will not be multisite so “artist” users will not be “isolated” from one another. They will need to have access to one specific page and one specific gallery and I will need to assign them a non default role too. So I can’t give them the “NextGEN Manage others gallery” capability as I don’t want to to have access to other users galleries at all. So I need the author property to remain set to that specific user and not be reset to an admin or other user with a default WordPress role.

Is my description of the issue clear enough? Is this something that can be fixed relatively easily in a future update?

Thanks very much in advance for any help or input on this!