• Resolved gizmocaldwell

    (@gizmocaldwell)


    When using PDB for our high school band registration for the coming school year, we deleted the registrations from last year and requested that users start a new registration.
    At least one parent used their Private Link from the previous year to try to update their student’s record, which happened to match the private link for a new registration this year for a different student. Do you have any suggestions on how we can prevent this from happening?
    Thanks for the great program! This is a huge improvement over the multiple forms we had been using to accomplish the same thing!
    Sincerely,
    Craig

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author xnau webdesign

    (@xnau)

    I’m pretty surprised this happened, and it’s even more unlikely to happen more than once…the private id is assigned at random, and there’s no way to ensure it isn’t a value that was assigned before since the previous values no longer exist.

    You won’t be able to change it for private ids that were already assigned, but it is possible to set a longer private id length, which would prevent any new praivate ids from matching old records.

    Take a look at this simple plugin that changes the length of all new private ids to 9 characters:

    https://gist.github.com/xnau/a65fc753d0101736b6739101f2a4982c

    Thread Starter gizmocaldwell

    (@gizmocaldwell)

    Terrific! I will try the plugin. Thank you for the help!
    Craig

    Thread Starter gizmocaldwell

    (@gizmocaldwell)

    Guess it was too soon to claim success. We had another user receive the same private ID today. This was a new registration created today, but the email with their private link was the same as the problem link from yesterday. Each user received:
    https://lassiterbands.org/pdb_record/?pid=T9ZKP9H
    So, perhaps instead of one parent using an recycled PID, it appears that PDB has assigned this PID to three different registrants. Any idea what could be causing this?
    Thanks!

    Plugin Author xnau webdesign

    (@xnau)

    My apologies, I failed to mention that you need to make sure the registration page and “thanks” page are not cached. Page caching can cause duplicate registration info to be sent out because it’s using the cached data instead of the fresh data.

    I should have known this was happening because of the unlikeliness of a duplicate code getting randomly chosen.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Duplicate Private Links’ is closed to new replies.