CVS edit link for meichr

I am developing clients websites for several clients ranging from static websites for repesenting a small company up to web applications with customer accounts and shop functionality.

There are widely used and thus important modules like e.g. views, rules, signup, token, webform and many more which offer common functionality which is even more valuable by working together via their respective APIs than only on their own. In many cases such integration has already been added to the modules themselves or as separate modules, e.g. like the recently published webform rules module.

In projects for my clients I sometimes would like to use such integration, only to see that integration between certain modules is not available, although both of those modules are very popular on their own.

Recently, a project required signup and rules modules to work together and so a custom module "Signup Rules Integration" was created to integrate those modules via the Signup and the Rules API.
This module is included as the first module I would like to contribute on drupal.org.

As the mentioned client project is still ongoing, I expect more rules events and certain conditions and actions be needed in future versions of the client's webapplication and so expect the "Signup Rules Integration" module to grow and also be migrated to Drupal 7 within a few months.

Comments

meichr’s picture

Component: Miscellaneous » new project application
Status: Postponed (maintainer needs more info) » Needs review
StatusFileSize
new2.13 KB

Enclosed the package with the Signup Rules Integration module.

meichr’s picture

Title: meichr [meichr] » Signup Rules Integration [meichr]

Title change ...

arianek’s picture

Status: Needs review » Postponed

Hi. Please read all the following and the links provided as this is very important information about your CVS Application:

Drupal.org has moved from CVS to Git! This is a very significant change for the Drupal community and for your application. Please read the following documentation on how this affects and benefits you and the application process:
Migrating from CVS Applications to (Git) Full Project Applications

  • The status of this application will be put to "postponed" and by following the instructions in the above link, you will be able to reopen it.
  • Or if your application has been "needs work" for more than 5 weeks, your application will be marked as "closed (won't fix)". You can still reopen it, by reading the instructions above.
meichr’s picture

Title: Signup Rules Integration [meichr] » Signup Rules [meichr]
Project: Drupal.org CVS applications » Drupal.org security advisory coverage applications
Status: Postponed » Needs review

Hi,
I've created a Sandbox project Signup Rules for review.
Now, I'd like to apply for a full project for this module "signup_rules".
Thanks,
Christian.

berdir’s picture

Is there a specific reason why this can not be added to the Signup module directly? It can be a separate module in the same project.

It is rather common to have rules integration in the main project, creating separate projects to combine two contrib module leads to an explosion of projects..

meichr’s picture

Berdir, thanks for your question.

A rules integration module doesn't necessarily have to be in the same project as the main module, though it is in cases like the userpoints module and others.

If the rules integration module doesn't fit into the main module's project, the maintainers of the main project prefers not to have the rules integration included or the complexity of features and/or release cycles make a separate project more adequate, a separate project would be a benefit for everybody. There are good examples for rules integration in separate projects, like webform_rules (see Webform Rules integration) and context_rules (see Context Rules module).

An example for separating two projects for better independent growth and maintenance is the i18nviews module, separated from i18n now.

Please let me know what you think.

Edited, shortened on March 11, 2011.

meichr’s picture

Added two new Signup Rules events, now the project provides the following Signup Rules events:

  • User signed up to content
  • User updated signup to content
  • User cancled signup to content
  • NEW: Signup for content was opened
  • NEW: Signup for content was closed

Hope it is useful for some of you.

Sandbox: http://drupal.org/sandbox/meichr/1077134

meichr’s picture

Title: Signup Rules [meichr] » Signup Rules Integration

The Signup Rules module has received an upgrade to include 5 new rules elements:

A new event for being able to suppress the signup form based on rules conditions. This includes a new condition to check the signup form display status and two new actions for allowing and forbidding the display of the signup form.
A second new condition allows to check the signup status of a user to the currently viewed content.

Full list of Signup Rules elements
Events

  • User signed up to content
  • User updated the signup to content
  • User canceled the signup to content
  • Signup to content was opened
  • Signup to content was closed
  • Displaying signup form is being inquired

Conditions

  • Is user signed up to content
  • Is display of signup form allowed

Actions

  • Allow displaying signup form
  • Forbid displaying signup form

For more information about the new and exisiting signup rules features please have a look at the Signup Rules project page, and the README.txt file and please review it for a full project.

Thanks,
Christian.

Sandbox site: http://drupal.org/sandbox/meichr/1077134

meichr’s picture

For those who would like to review or test the signup rules module the tgz and zip files of the current version are attached here.
Thanks for your testing or reviews.
Christian.

meichr’s picture

The Signup Rules module has received another upgrade to include a new rules condition "Is signup status open for content" based on a feature request of MasterChief (Issue 1090250).

Full list of Signup Rules elements
Events

  • User signed up to content
  • User updated the signup to content
  • User canceled the signup to content
  • Signup to content was opened
  • Signup to content was closed
  • Displaying signup form is being inquired

Conditions

  • Is user signed up to content
  • Is display of signup form allowed
  • NEW: Is signup status open for content

Actions

  • Allow displaying signup form
  • Forbid displaying signup form

For more information about the signup rules features please have a look at the Signup Rules project page, and the README.txt file and please review it for a full project.

Thanks,
Christian.

Sandbox site: http://drupal.org/sandbox/meichr/1077134
For non-developer testers and reviewers the current version of the module is attached to this comment in tgz and zip format.

BenK’s picture

Keeping track of this thread and hoping the project will be approved!

MasterChief’s picture

Me too :)

beifler’s picture

Subscribing!

jordojuice’s picture

Subscribing.

rteijeiro’s picture

Status: Needs review » Needs work

Please, review the project with the Coder module: http://drupal.org/project/coder

Kind regards.

jordojuice’s picture

Component: new project application » module

@meichr Is this module abandoned? If so I will gladly take over the cause. Specifically, I don't know why this isn't being offered as a patch to Signup (unless it is!). Please give us an update.

jordojuice’s picture

Status: Needs work » Closed (won't fix)

I'm closing this project application to take over development of the module. Please recognize that the author has not responded in over three and a half months, even after a request for a Coder review over two months ago. I need this module and there is no activity on it!

BenK’s picture

@jordojuice: Where are you continuing development? For D6 or D7?

--Ben

jordojuice’s picture

I did a lot of work while I was waiting for a response. I originally tried to contact meichr several months ago when I posted a patch in his sandbox issue queue, so I've been familiar with the code for some time. This weekend I took the code and did a lot of work on it, adding more conditions and actions (Rules is pretty easy to work with). The project now has an alpha release out at http://drupal.org/project/signup_rules. Signup maintainers are very busy and had no apparent objections to separating the project. I also published a Signup Status Rules module (http://drupal.org/project/signup_status_rules) which was the reason I originally became interested in this project (I needed a Signup Status Rules module badly). Signup Status Rules is dependent upon Signup Rules because it makes use of Signup data types and is much more flexible with Signup Rules enabled.

As for D7, I have ported much of Signup Rules to a 7.x version. Even though Signup 7.x is still in development it's pretty much a straight port and I dont expect any of the Signup hooks will change so it should be safe to release it soon. The only rules that are not available yet are most of the ones that relate to the signup itself. So, whereas you can set the signup as attended in the D6 version, that can't yet be done in D7. This is because data types changed a lot between Rules 1 and Rules 2, and I have to finish the work to define the Signup data type to rules.

So, Signup Rules 7.x is in the repository, but I haven't released a development snapshot yet. I can do that shortly after I do more testing. I tested the 6.x version as much as I could, bu I'm very interested to see what input I can get from users. It was changed a lot since meichr had it and people tested it. I added more conditions and actions to deal with signups like cancel all signups fo a user or node or set attended/not attended. I'll be continuing work on it for the foreseeable future.

jordojuice’s picture

Help is welcomed! : )