Registerd user cancels a registration

Possible. We'd need to figure out UX, but definitely something we'll look into!

The user cancelation feature is huge for our project, so I figured to do a little bullet pointed list of requested user cancellation features.

1. When a user is registered their should be a simple text message on the registration tab view that says, "You are registered for this event".
2. When registered and you visit the register tab, the register button should be changed from register to "cancel registration" and there should be no other link visible except for the cancel registration button.
3. Once the cancel registration has been selected, the message should say "Your registration has been canceled".
4. Button Changes back to "register".
5. Automated email should be sent to both the participant and the organizer. (this could be a check box in the register settings).

Thanks again for your hard work !!

+1.

Let us know if you need assistance with making this happen.

I've created a custom field formatter for this 'toggle registration link'. It checks if the user already has registered - if yes, the button says 'cancel registration' . Now, this was done a while back, and i haven't checked this still works with the latest codebase...

How does it look? Any news about canceling of the registration?
And the message "You are registered to this event"?

I find it kind of strange and confusing that the user can still see the e-mail field and send the form several times for one event, even when he is already registered.

Some of the code in the access issues grant the author to delete their own registrations. I think the issue here is when the registration email != author, or anonymous user.

Today I installed alpha4 and some patches found in the issues (http://drupal.org/node/1462796).

Now the registered user can view he has already registered and can access the list with his registration. But when he clicks on Delete it says: "You are not authorized to access this page".
And yep, I checked the permissions and he can "Delete own registrations."

Current alpha requires 'administer registration' and 'delete own registrations'.

The issues I was referring to was in #1472250: View and edit own registration permissions.

Sorry, but I am kinda lost right now.
What do you mean by

Current alpha requires 'administer registration' and 'delete own registrations'

If these are patches, can you point me to them please?

I installed the new alpha, applied some patches found in the issues queue. Users were able to see a list with their registrations, but when they clicked on Delete there was the access restriction page.
The I applied patch from your last link (http://drupal.org/node/1472250) and now the users doesn't even see the form or tab where they can register. I feel something is wrong in here and I have to start from scratch, but dunno which patches are needed and which are not to make this work.

Any help will be appreciated :)

What I mean is, you can use existing code without patches, but you need to grant users both 'administer registration' and 'delete own registrations' permissions.

Alternatively, you can try the patch in #1472250: View and edit own registration permissions -- comment #7. The only permission you will need to grant is 'delete own XXX_type registration'.

OK, thanks. But when I grant users 'Administer registration' they can delete other users registrations (as a test user I deleted my admin registration). And when I grant only 'Delete own registration', they are not able to delete it.

Another thing is that when I delete the registration, it goes to page "Page not found" (for example /registration/2).

Yeh, its kind-of a broken design. I'm trying to change it in that issue. If #1472250: View and edit own registration permissions works out for you, let us know.

Users with proper perms can now delete their own registrations. If there's a consensus that we need a 'canceled' registration status, we can put that in the queue.

Anonymous user still needs to cancel

@dpi, that's now what this issue is about ("Registerd user cancels a registration"), and I'm not even convinced that should be part of this core module. But happy to explore and chat about it.

cancel and unregister - in my opinion are different behaviours:

• "cancel" means delete - the whole data entry gets deleted. Can be done any time and by selected roles.
• "ungregister" should be usable only until registration is closed

For "unregister" we could have one separate permission for "normal" roles.
And if unregistering had a configurable closing date, relative to registering closing date, the process of unregistering would be perfect.

What do you think?