Need to add a status to the registration schema with at least pending and complete values. This will be used for paid registrations, verifying anonymous registrations, etc.

Comments

dpi’s picture

dpi
Location Perth, Australia
commented

When a user adds other account/email. What should default Registation status be?

Does this mean #1525252: Allow anonymous users to unregister from entities should also cover verifying a Registration's status? specifically from PENDING to COMPLETE?

levelos’s picture

levelos commented

I was going to start out with 3 states, pending, complete, and canceled. Maybe providing a hook so the list can be altered.

When a user adds other account/email. What should default Registation status be?

Other account likely complete, other email, depends if we have an email based verification system, in which case pending then complete when verified.

Yep, I was thinking #1525252: Allow anonymous users to unregister from entities should definitely coordinate with this change. I'm in progress on it now and will commit today most likely.

dpi’s picture

dpi
Location Perth, Australia
commented
Component: Code » Registration Core

Why wouldn't optionally/requiring an admin to add a status field to Registration bundles work out?

E.g: a core 'list' field with hook-able allowed_values.

Would be great to inherit all the fun and good times of the field system.

levelos’s picture

levelos commented
Status: Active » Fixed

Good idea, but I haven't been thrilled with create new field instances when a bundle is created and then basing a bunch of logic around it. Just committed a first pass, including a hook for adding additional types. Feedback welcome.

Status: Fixed » Closed (fixed)

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

  • levelos committed 1497d36 on 7.x-1.x, panels, any-entity, slots, integrations, hold_state 
    #1526232: Add state field for registrations, including hooks for...