Users can't delete their own registrations

I'm debugging this as well for a project I'm on. Where the form should be displaying a "Delete" option, it fails here-

http://drupalcode.org/project/registration.git/blob/refs/heads/7.x-1.x:/...

Which is called from here-

http://drupalcode.org/project/registration.git/blob/refs/heads/7.x-1.x:/...

I am unsure as to why a user who has "create" access to generate the initial registration, but not here.

I am having the same problem, only admin users can delete an event registration, no matter the permissions I set.

Same problem for me. In " Permission" j've checked "Administer own settings" for autenticated users, but it doesn't work.

I'm having this problem also, it would really make my life easier if there was a fix, or some alternative for this issue.

Subscribing

I've created a Views block which we can show in the left(as "Edit/Delete Registration") and it shows only for nodes for which a user has registered herself.

When creating Views Block select "Registration" types and add the block in the left sidebar.

If you want you can embed the block within the node too.

This is the same issue as this one: https://www.drupal.org/node/2320171

I've made a patch that seems to fix the issue, though someone with more knowledge of the project might best review it.

The fix is to make a separate access_callback for the 'Manage Registrations' callback. I also changed this link to 'Registrations', because a normal user will only be able to see the registrations and edit his/her own. An admin can still edit all registrations, access the Settings, and mail the registrants.

Mailing the registrations should probably have its own access logic, but that's another feature/patch.

Tried the patch in #11, didn't change anything, even after cache clear.

So I set up a workaround. It's very simple and won't work for every case, but thought it my be worth sharing :

function nmrz_entity_view_alter(&$build, $type) {
  if ($type == 'node') { // Could test bundle also here
    global $user;
    
    // Basically, we look if there is a registration for this user on this entity ...
    $result = db_select('registration', 'r')
      ->fields('r', array('registration_id', 'user_uid', 'entity_id'))
      ->condition('user_uid', $user->uid)
      ->condition('entity_id', $build['#node']->nid)
      ->execute()
      ->fetchAssoc();
    
    // ... if yes, we output a link to the deletion page
    if ($result) {
      $build['deregister'] = array(
        '#type' => 'markup',
        '#markup' => "<a href='/registration/" . $result['registration_id'] . "/delete'>Annuler ma participation</a>",    
        // The sentence more or less means "Cancel my registration" in french.
        '#weight' => -100,
      );
    }
  }
}

I also tried applying the patch from #11, but it didn't work and I got the white screen of death. I am not sure about the workaround in #13- I'm a bit of a newbie so not that familiar with how registration works.

Permissions with registrations are admittedly complex. A user can view/edit/delete their own registration so long as they're the author of the registration. In other words, if they register themselves. If another user registers them, then they, by design, cannot manage their own registration. Take a look at registration_access() to see how all this works.

That seems like a bad design to me. I somebody tells me they want to join I can register them, but then if they see they won't make it they can't cancel the registration, even it is for their account?
So they have to call me to edit the registration? That is strange in the least.

There was a patch for this issue with additional permissions posted here: #2512982: Add permission to manage own registrations created by another account.