Views integration

What does a views integration mean? What are you trying to do?

Closing this as BManuel never responded.

I'm not sure this has anything to do with Views integration, nor can regcodes be created by normal users, so none of this is relevant to this module. Perhaps look at the Invite module.

We were having trouble with the registration code List page causing a white screen, because we have generated so many codes (45K+) on one of our sites. I also wanted to get some experience with the Table Wizard module, so I decided to add Views integration via a custom Registration Code Views module. Once enabled, this new module allows the Views module to be used to generate custom Registration code reports or lists.

The module also includes a default view that replaces the standard List page (admin/user/regcodes/list) with a Views generated page that mimics the original. The Views version of the page includes a pager, in order to eliminate white screen issues for sites that generate a lot of registration codes.

One thing I haven't yet figured out is how to maintain the menu tabs that were on the original page (Settings, Create, List, & Import). If anyone knows how to do that while still using Views to generate the page, please feel free to jump in and address that issue. The handlers output by the Table Wizard module could probably be tweaked to better handle the date & time fields and to transform the Boolean fields to Yes/No, instead of (blank)/1.

Here's an update that includes the proper field handler for the is_active/Enabled boolean field.

The views_handler_field_date handler seems to expect a different date format than the one used by the regcode table, so I'm not yet sure how to get it to handle the date fields as dates instead of text.

Hi Matt V,

Very cool, thanks for the work you've done. However, I'm actually just finishing up full views integration and a new tagging system which should make dealing with many regcodes much easier.

It's also integrated with views_bulk_operations as well which means it's easy to mass delete, disable, tag, etc.

I should have it ready to go tomorrow, hang tight.

I've just committed the latest version to CVS on the 2.x branch. A development release should show up in the next 12 hours.

This new version has full views integration, but it's a complete rewrite of both the API and admin pages. This means there's heaps of bugs, so it's definitely not recommended for production.

I'm marking this as fixed, so keep an eye on the 2.x changelog.