Problem with filter – empty fields

OK, well the problem is, the plugin doesn’t save values to fields that are not in the form…it does not fill in the record with default values. (Perhaps it should, I’ll think about that) Anyway this means that when using the list filter in the backend…or in the shortcode…you need to filter for records that do not contain a value:

[pdb_list filter="accepted!yes|accepted!no" display_count = "true"]

Thank you for your quick reply, XNAU!!
However.. this won’t work.. the filter just ignores the records with the empty accepted field. If I have a simple pdb_list, they will be visible, the issue is when I’m adding a filter..

I think the correct way of filtering would be [pdb_list filter=”accepted!yes&accepted!no” display_count = “true”], meaning “&” instead of “|” (if I want to make sure I exclude all the records, the Yes and the No ones), but as mentioned.. it’s not working.(I tried both ways – the one suggested by you, and the one with & instead of |).
Somehow filter statement ignores the record if nothing is found in that field. Any idea where i could see the code for this, to try to fix it?

Thanks a lot!

OK, the “&” would work, sure. But what do you mean by “ignored”? Which records are showing in the list?

You could also try:

[pdb_list filter="accepted=" display_count = "true"]

Which will give you all the records with a blank “accepted” value.

The [pdb_list filter=”accepted=” display_count = “true”] doesn’t show anything…

What I meant by ignoring:
– if i put only [pdb_list], the result will show me 19 records (5 having accepted as Yes, 1 No, 1 Waiting List, 12 Unprocessed
– if I start adding filters (having ! as an operator) I’m “loosing” 7 records (out of the 12 records that have Unprocessed as a value, 5 of those I have updated in the Admin page, therefore the value is in the DB, the other 7 only show Unprocessed because is the Default value, but the field is probably empty in the DB). For example add [pdb_list filter=”accepted!Yes”], the result is only giving me 7 records (5 Unprocessed, 1 No, 1 Waiting List). The other 7 records having blank in accepted are not at all taken into consideration… I think there is a bug in the way the select is done, but not sure where to check.
I hope it’s more clear now?

Thanks!!

Your example (“accepted!Yes”) is giving the correct result, so I don’t see that there is a problem. (it’s showing all the records that do not have a value of “yes”) The filter I gave you for showing records with an empty field value does work, so there may be something stored in the fields you presume are blank.

It’s a good idea when solving this kind of problem to look at the database directly so you know exactly what is in there.

Which records do you want to see in your list?

Thank you again for your reply.
However I have to disagree – the query “accepted!Yes” is not showing the correct results – because it doesn’t show as well the records having no value in the field (which respect the condition – do not have a value of “yes”).
And yes – I have checked now the values in the database – no value at all stored in those fields.
I have also removed the Default value.

The pdb_list works fine, it shows all records – the issue comes when adding filter… What I’m thinking now – is there any DISTINCT in the SELECT done for the filter that would thus ignore the empty fields?

Thanks!!

No there is no DISTINCT. I’m not sure what we’re seeing here because I have tested this and it works as expected. I didn’t understand that you weren’t seeing record with blank entries…those should be included.

I would like to know what result you are looking for in your list, so we can focus on that.

Hello, I’m still facing the same issue, trying to figure out what’s wrong.
I deleted all the records in the database, plus the accepted field and created a new one.
What I noticed: the filter “=” ([pdb_list filter=”phone=’]) works find for the text fields, not having any value, but it doesn’t show any result for the fields defined as radio-buttons, having values defined (Yes, No, Unprocessed), even if there are 3 records that don’t have anything in that field…
I tried with filtering with fields shown and not shown in he Signup form, and the same conclusion apply – doesn’t work for Radio-Button fields. Being part or not of the Signup page doesn’t influence anything.

Don’t know what to do know.. tempted to create a custom SQL and table to display the records, and drop the list shortcode..

What do you think?

Thanks!

I see, you’re right, this doesn’t work as it should. This is because the column is filled with “null” values, which aren’t the same as an empty value. This is something I need to fix in the next release.

But for now, I offer this fix. You’ll need to run this query on your database to convert all the nulls to blanks. Then your filter will work. You may need to change this if the prefix of your table is different or if you want to run it on another column.

UPDATE wp_participants_database p SET p.approved = '' WHERE p.approved IS NULL

Before doing this, backup your database (just in case!) then run the query using PHPMyAdmin or another database editing tool.

Thanks for the answer and the temporary fix.
However :), this will fix my issue for the existing records.. I would need to come up with something for the new records being created as well (probably an update on the DB after record is inserted).

Ah, yes…well, what you can do is alter the “approved” column so it doesn’t store a NULL in undefined fields. in PHPMyAdmin, where the column properties are defined, make sure default is set to “none” or blank and “Null” is set to “no”

Now, when a new record is created the ‘approved’ column will be blank, not NULL.

Thank you very much!! It did worked like this.
My list shows the correct results now.
Thanks for your help.

Hi, Am having exactly the same issue but with a dropdown list. First value in the list is ‘New’ as in ‘new member’ and the default value is ‘New’ but the pdb_list will not select them. I definitely vote for storing default values to the record! You cant use them if they are not saved so not sure what purpose they could have. You cant even select them in the admin nor select empty/null.Thanks

yes, you’re right, and you can do both of those things in the new release.

did you attempt the fix I recommended above? It would work in your case too.