Hey regcode-users!

in coordination with our regcode-maintainer Colan, i created a completely new and refactored version of regcode.module, with many new features and optimizations, including:

- db-storage with multiple fields, with (per code):
* role granting by code
* expiry of availability
* one-time-only or re-usable codes
* tracking of code-usage (user, date)
* info-column for freestyle-usage
- filter- and order-able code listing / search
- import (with flexible CSV--setting, file-upload- or textarea-import and a default code-data-template)
- permission to override even mandatory regcode-input for adding new users (helpful for admins)

This current development has been sponsored by plazamedia.com

Find attached the refactored regcode.module, ready to be tested and reviewed.
Simply copy the new module directory over your old and -IMPORTANT!- run Drupal's update.php and give it some time to import existing old registration codes into the new db-based code-storage.

I'm planning to upgrade this to D6 and D7 this spring and probably to add a drush-action for a batch-import.

So: Is this ready to be committed as recove 5.x-3.0?

cheers,

daniel

CommentFileSizeAuthor
regcode-5.x-3.0-2009-05-18.zip19.91 KBdanielnolde

Comments

danielnolde’s picture

This new version solves a lot of feature requests and issues in one combined version, e.g.:

http://drupal.org/node/253627
http://drupal.org/node/234684
http://drupal.org/node/361527
http://drupal.org/node/203576
http://drupal.org/node/154355
http://drupal.org/node/311815
http://drupal.org/node/311353

So, review it, test it and tell me whether is solves your issue well enough.
Well, for the first 5.x-3.0 release i certainly won't *add* new features, but please review whether something's conceptually or functionally broken.

The next steps (after this 5.x-3.0 and an already planned 6.x-3.0 release), toward a 6.x-4.x version would then be topics like flexible code-providers (like web services, external code databases etc.) and at last a simple yet solid hook-based API (like hook_regcode for a code's import/creation/deletion/expiration/validation/usage/user-assignment etc.). I suggest that we discuss any of those new advanced "4.x"-feature in a different thread later on, when 5.x-3.0 and after that 6.x-3.0 have been made official.

cheers,

daniel

summit’s picture

Hi,
great you are reworking on this!
I do not know, if this is the time to ask, but anyway, I try it :)
Would it be possible with this module to login ONLY using the registration code and not having to login using username/password. I would like to build a site using a survey module like quiz (www.drupal.org/project/quiz), and give users access to the survey by only having to type in a code and not needing to have to register through username/password.

Thanks a lot for your answer in advance!
greetings, Martijn

danielnolde’s picture

Hey Martijn,

authentication with registration code instead of password is not supported at the moment.
My ideas for a 4.0 version would be to provide hooks to be able to implement such things with a small add-on module.

cheers,

daniel

summit’s picture

Hi Daniel,
Great you have it in scope! Hopefully 4.0 will not long due.
Thanks for your response.
greetings, Martijn

daniel.marston’s picture

How is the upgrade to 6.x coming along, just wondering if it will be done within the next two weeks, it would be great if i could use it for a website that is launching 1st july.

Thanks,

Daniel M

aidanlis’s picture

I've created a D6 port of the great code provided by danielnolde. It supports some new features and cleans up a few things.

Colan, could you please add danielnolde and myself as maintainers of this project? Alternatively if you prefer, I'll create a new project under a different name.

colan’s picture

I've given CVS permission to aidanlis and ilo. danielnolde doesn't have a CVS account, so I couldn't add it. Have fun coordinating! =)

If you'd like me to sign the project over, create a separate issue for this. I need to okay it there, and then you can send a request to the site admins to actually switch the owner.

ilo’s picture

Colan pointed me to this issue. We will do the merge of this and other modules (Daniel is also aware of this) so I guess all this functionality should be provided by the final merge and not by this one.

Commiting this will increase the issue queue for the final days of this project, and would difficult the merge later (I've found some issues when testing the features of this module). I don't like to do this, but would do commit if people request.

In any case I should suggest to wait for the merging operation already started.

summit’s picture

Great this is moving forward, please bring: http://drupal.org/node/466630#comment-1628830 authentication with registration code only also within scope, and hopefully D6 supporting!
Greetings, Martijn

aidanlis’s picture

Status: Needs review » Closed (fixed)