Is it necessary to have an API key for each user?

If you want each user to be able to have custom notifications sent to their iPhone, than each user will need to have their own API key.

If you only want to use it to send system notifications to a site admin for example, than you only need the one key for the site, and only that user would receive notifications.

Hi there,

if you want to remove the per-user API key form, simply disable the Prowl User Integration module.

cheers,

Adrian

Maybe i misunderstand what's going on, but it seems a little inflexible.

I have a site for an online mag.

There's Editors and Contributors.

When a Contributor posts, i'd like the same message pushed to all Editors via prowl.

I really *don't* want the prowl API key to appear when a new user registers, or on the user form for anyone except editors.

I'd like to use the Prowl Messaging module to let the Messaging framework handle the settings for each user.

So, I tried to follow the advice here and disable the Prowl User Integration module, but the Prowl Messaging module has that listed as a dependency.

What's the best plan of attack?

Hi there,

sorry it took a while to respond - looks like basically you would like to restrict prowl API keys to a certain role(s). This is a very reasonable request, but not one I have time for at the moment. I will certainly be happy to review a patch, you'll want to look at the implementation of hook_user() in the prowl_user.module file.

thanks for looking at this, sorry but i'm not using this module any more. We've come up with an alternative solution for our use case.

I too needed to be able to specify which roles could access Prowl, and this patch does the trick. I was able to tackle the issue by adding an additional permission of "View Prowl Settings", and by toggling which role can view the settings; you can effectively hide all functionality from any role that you don't specify. This was a quick way to get around the issue, hope that it can help!

I have applied this patch to the 2.x branch and created a dev release - please test and let me know if you find any problems.

Marking as fixed.