I am having an issue sometimes with registered drivers for events where I am unable to edit them from the registration screen. I can go into the "checkin" screen and it works but if i want to reclass a driver i cant do that. is there a way to fix this "orphan"?
Orphan Drivers in events
What do you mean by unable to edit them? What happens?
On the checkin screen, what works and what doesn't? Do you mean you can change anything except class?
In the registration screen I click on the driver and nothin happens at all. It should open the reg screen for that person but it doesn't
On the checkin I can edit and do as I please
Please do the following;
- In Chrome, go to the registration screen
- Shit + Control + i (windows) or Command + Option + i (osx)
- Click the Console label of the new Developer tools panel that opened
- Reload/refresh the registration screen (Ctrl + R or Command + R (osx))
- click on a driver
- look in the Developer tools panel, is there any red text? If so, copy and paste in a reply here.
Here you go Chris.
I can't tell exactly, but I'm thinking that the registered driver either has no member record or somehow the member ID is wrong or missing.
Did you by chance delete any members? Did you merge members? Or perhaps receive an error when creating these registrations? Were these registrations imported via CSV or MSR?
Could you do a back up and email it to me? Or do a cloud backup and I can grab it from the server.
I believe I know where in the code it is happening, and I can fix the error, but it should never get to that point, so something else happened.
Sorry I didnt respond sooner I have been traveling for the past two weeks solid, I dont recall the exact circumstances of the creation. I imported the registrations from MSR and I seem to recall when i went to check in the driver that there was a message about driver number/class being a conflict. I believe the data is backed up to the cloud but I will do it again when i get home at 3pm PST
backup completed and posted to the cloud