Empty private ID (PID) when new user signs up

You need to completely configure the “Participant Record Page” if you scan through the “Setup Guide” you’ll see how that’s done.

Thank you very much for the prompt reply.

I have verified step-by-step my configuration, following the “Participants Database Quick Setup Guide” available on your web site. In particular, in the “Participant Record Page”, I have properly configured the page where the participant record is shown.

We actually use your plugin without referring participants to a separate records page. Instead, we ask subscribers to directly enter all their information on the sign-up form. Could this be at the cause of the problem? For instance, does this omit the generation of a PID?

As a side note, I actually do use the participant record page, but only to implement the front-end editor described in one of your tutorials. This front-end editor works perfectly with participant entries created from the backend (which do have a PID), but not with entries generated from the normal sign-up form.

Thanks a lot again. I really appreciate.

OK, sorry, I’m confused. I thought you wanted to include a link to the record edit page in your email.

A private ID is generated for all new records no matter how they are created. Why do you say it is blank? Where are seeing a “blank” private id?

Thanks a lot again for the reply.

In the list of participants in the WP Admin Panel, those entries that have been generated using the [pdb_signup]-form do not show a Private ID, whereas those generated through the back-end do.

For me, this is a bit difficult to understand as well.

Here’s a screenshot (I’m using Spanish as default language).

<img src=”https://www.gloriamolio.es/wp-content/pdb_missing-pid.png”&gt;

Thanks again for your help and patience.

I am also experiencing the same issue. I am using a sign up form and no Private ID is being generated.

Here is a screenshot https://db.tt/17h4hbTi

It seems indeed we’re having the same issue. I’m using the most recent version of the plug-in by the way. I’ve noticed that some entries in the database also have an empty “Date Recorded” field (strangely only some, and there seems to be no obvious pattern). Maybe this information helps in tracking down the issue.

Thanks a lot for all the help in advance.

I am using Participants Database version 1.7.0.2.

OK, not able to reproduce this here, but I have one idea how this might happen. Can you take a look at the HTML of your signup form…see if there is a form field of any kind with the name “private_id” let me know what you find.

Thanks a lot for the reply. On our site, there does not seem to be any form field with the name “private_id”, nor any other variable in the HTML code containing that string.

Here’s to the sign-up form (front-end).

Thanks for all your inquiries.

OK, what are your duplicate record preferences?

By the way, you may not want to use a “numeric” field for your telephone numbers because it only accepts numbers: no spaces, plus signs, dashes, etc. that people may want to type in for a telephone number.

Confirmed here as well. Past two have been blank.

Duplicate preferences are set to overwrite – check by email.

Missing ID Screenshot

Settings Screenshot

Thanks a lot for your responsiveness. I highly appreciate.

I have the same duplicate record preferences as the previous poster (overwrite & check by email).

Thanks also for the comment regarding the field type “numeric.” I use it to force iOS devices to show a keyboard with numbers. I’ll be happy to check if there’s another way to do so.

Hey Flurinus – what version of PHP are you using? The plugin was working great prior to this weekend, and we upgraded to PHP 5.6 – which required some updates to our custom PHP code (due to changes in syntax requirements). I’m wondering if you have the same, perhaps the upgrade was what caused it, and it’s just a syntax issue with the code that generates the id…

Can you confirm your current PHP version on the server you’re having the issue on?

We’re using PHP Version 5.6.22 (I have no experience running the plug-in on a previous version).

Thanks to all of you for your efforts in getting this issue resolved!