Is there a way to control/limit access to the registration states field? Currently, it looks like anyone can change their own registration state when given "edit own registration" permissions, which seems by design, but counter to what I thought registration states was meant for.

Use case scenario:

Content owner creates node with registration enabled. Registrants should start as "Pending" and then be moved to "Registered" by Owner only, providing a means for owners to control who registers for their content. Content owners could also move registrants to a "rejected" state.

Comments

seanberto’s picture

For reference, see duplicate ticket: #1772746: Roles access to Registration states

lklimek’s picture

+1 - I need it too.

See related issue: #1670210: How to Use Registration States for workarounds.

lklimek’s picture

Title: Control access to registration states? » Control access to registration states
Component: Registration Entity Access » Registration Core
Category: support » feature
Status: Active » Needs review
StatusFileSize
new2.56 KB

I've implemented mechanism that adds additional permission "edit state" for each registration type.

Please see attached patch (rolled against latest dev).

MichaelP’s picture

Tested patch at #3. OK.

Tks @lklimek

levelos’s picture

Status: Needs review » Fixed

Thanks, nice patch.

Status: Fixed » Closed (fixed)

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

  • levelos committed a365b71 on 7.x-1.x, panels, any-entity, slots, integrations, hold_state authored by lklimek
    #1770852 by lklimek: Control access to registration states.
    
MaximHigh’s picture

Issue summary: View changes

Hi,

i am new on drupal, and need this patch for my site! :) I tried to patch the registration_entity_acess.module with Netbeans with Tools->Apply Diff patch but he shows me "the patch cannot be applied in the selected context". I saved the patch with right click and then save, what i do wrong? >.< I work with drupal commons and acquia dev desktop control panel