Hi,
I need a feature for a client, that signup forms shall be disabled for some content types or even the same content type with certain taxonomy terms. Another reason for disabling a signup form shall be when the acting user has too less userpoints available.

A flexible solution is having a signup rules event which is triggered whenever signup plans to display a form on a signup enabled node. When the rules event is triggered, one or more corresponding actions shall decide, whether the signup form is displayed or suppressed.

Independent from this new signup rules event and the new rules action also a new rules condition is needed for the client project to check whether the acting user is already signed up to a node.

I'm currently working on implementing these three to four new signup rules features and plan to add everything to the sandbox project signup_rules.

Christian.

PS: With these features, working on the signup_rules project becomes even more interesting as the new event and the new action are more challenging tasks to be added on top of the standard events based on the patch of user Magnus (modified into a separate module), and more details about the rules API have to be researched and mastered. Please bear with me for some more time. ;-)

Comments

meichr’s picture

meichr commented
Status: Active » Fixed

5 new rules elements have been added to the signup rules project to implement this feature request.

Now it is possible to disable the signup form on each individual content view based on rules conditions. This allows e.g. to disable the signup form if the acting user has too less user points.
An additional condition allows to check whether a user is signed up to the current content.
For details about the new rules elements please have a look at the project main page and/or the README.txt file.

As the project itself is in review I mark this issue as fixed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.