Active
Project:
Automember
Version:
4.5.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Reporter:
Created:
20 Dec 2004 at 23:27 UTC
Updated:
16 Feb 2006 at 06:28 UTC
I might be missing something, but when I invite someone to the target role, "and do not have selected that someone must 'opt-in,' which I assume means they have to check the box on their profile page that they want the role of "special," the invitee sees no notification of their invite so they don't know they have been given the new role.
I'm trying to use this for a role to test some new features, but I don't want every user to see a checkbox regarding the role and have to explain to them that some people get to test out new features. However, I do want people invited to know they have been invited and have a chance to respond. Is this possible?
Comments
Comment #1
grohk commentedSeconded. This would be a nice feature. The Buddylist module currently has such a function when you are added to someones buddylist. It simply prints a div called "messages status" saying a user has added you to his/her buddylist the next time they load the homepage. Or perhaps an email could be sent to notify the user?
Comment #2
jasonwhat commentedis this module still being maintained?
Comment #3
grohk commentedYes, njivy is the maintainer. I am sure that he is considering this feature request and perhaps will implement it in the future.
Comment #4
njivy commentedHi guys. I'm back from Nevernever Land and am looking into this.
Would it be satisfactory if every user got an email notification when they were granted the target role by the module?
Comment #5
jasonwhat commentedsure, that could work. It would be nice though if they knew who invited them if someone did invite them, so maybe that name could be in the emai?
Comment #6
(not verified) commentedI had planned to do this today but ran out of time. I did not forget! Thanks for your patience.
Comment #7
njivy commentedThat was me, btw.
Comment #8
Kobus commentedThis feature was built in to the 4.6 version of the module, and therefore will definately be in 4.7 too.
Once I sorted out all the porting bugs, I will confirm whether it works as expected.
Regards,
Kobus
Comment #9
Kobus commented