macwinson

Hi!

Thanks for the clarification!

After checking the demo at 🔗 Participants Database I can definitely see the improvement with the inline spinner to the right of the pagination. That’s great progress!

However, from my context (and theme), the main issue is that the entire pagination control has become too small, making it difficult for users to click comfortably.

I’m wondering if there’s a way—maybe with a bit of CSS magic—to restore the previous layout while keeping the inline spinner. I’ll experiment with it and let you know how it goes.

In any case, the workaround I mentioned earlier is still a reliable fallback.

Best regards,

Hi, tested with Siteground hosting, with no issues so far:

MySQL version 8.0.36-28
WordPress 6.5.2
Participants Database 2.5.7

Thanks for the feedback!

Hi!

Updated to 2.1.11 and tested… seems to be working fine now.

By the way, the update says:

"fixed issue with blank “allowed” attribute in upload field"

The fix was applied to “Image Upload Field” too?

Many thanks for the urgent update. Glad to help!

Can I, at least, know if it is possible before buying the Pro version?
1) Is it possible? (please see the topic question).
2) Using the Pro version, the customization requires an extra charge?
Thanks!

By the moment I don’t use any add-on, because the people that use PDb are just starting to use the database and familiarizing with how it works. It seems simple, but is very powerful “as is” and complex in some ways. I’m planning to include Combo Multisearch and Directory Tools (Proxy Posts).

Just an update, I was able to recreate the error:

1) go to List Participants

2) change dropdown: Show only records with: “Multi-Field: Any Field”
*the same situation “Multi-Field: Any Text Field”
that – contains – *no need to enter anything to search*

3) click on “Filter”

4) you will get the error:

using: “Multi-Field: Any Field”

Fatal error: Uncaught Error: Call to undefined method PDb_admin_list\all_fields::is_numeric() in \wp-content\plugins\participants-database\classes\PDb_admin_list\query.php:326 Stack trace: 
#0 \wp-content\plugins\participants-database\classes\PDb_admin_list\query.php(310): PDb_admin_list\query->empty_value_phrase(Object(PDb_admin_list\all_fields), false) 
#1 \wp-content\plugins\participants-database\classes\PDb_admin_list\query.php(276): PDb_admin_list\query->empty_value_where_clause('LIKE', Object(PDb_admin_list\all_fields)) 
#2 \wp-content\plugins\participants-database\classes\PDb_admin_list\query.php(119): PDb_admin_list\query->_add_where_clause(Array) 
#3 \wp-content\plugins\participants-database\classes\PDb_admin_list\query.php(46): PDb_admin_list\query->_process_search() 
#4 \wp-content\plugins\participants-database\classes\PD in \wp-content\plugins\participants-database\classes\PDb_admin_list\query.php on line 326

using “Multi-Field: Any Text Field”

Fatal error: Uncaught Error: Call to undefined method PDb_admin_list\text_fields::is_numeric() in \wp-content\plugins\participants-database\classes\PDb_admin_list\query.php:326 Stack trace: 
#0 \wp-content\plugins\participants-database\classes\PDb_admin_list\query.php(310): PDb_admin_list\query->empty_value_phrase(Object(PDb_admin_list\text_fields), false) 
#1 \wp-content\plugins\participants-database\classes\PDb_admin_list\query.php(276): PDb_admin_list\query->empty_value_where_clause('LIKE', Object(PDb_admin_list\text_fields)) 
#2 \wp-content\plugins\participants-database\classes\PDb_admin_list\query.php(119): PDb_admin_list\query->_add_where_clause(Array) 
#3 \wp-content\plugins\participants-database\classes\PDb_admin_list\query.php(46): PDb_admin_list\query->_process_search() 
#4 \wp-content\plugins\participants-database\classes in \wp-content\plugins\participants-database\classes\PDb_admin_list\query.php on line 326

By now, I can reset the user options this way: go to phpmyadmin, table wp_options, and delete:

pdb-admin-user-settings-(ID of the user)
pdb-admin_list_filter-(ID of the user)

The ID of the user is “2”, so I guess these are the records that matter?

"387","pdb-admin_list_filter-2","a:4:{s:6:""sortBy"";s:13:""date_recorded"";s:7:""ascdesc"";s:4:""desc"";s:17:""list_filter_count"";s:1:""1"";s:6:""search"";a:1:{i:0;a:4:{s:12:""search_field"";s:14:""pdb_all_fields"";s:5:""value"";s:0:"""";s:8:""operator"";s:1:""="";s:5:""logic"";s:3:""AND"";}}}","yes"

"386","pdb-admin-user-settings-2","a:2:{s:10:""list_limit"";i:10;s:13:""with_selected"";s:6:""delete"";}","yes"

What should I do? copy a working “option_value” (from user ID 4 for instance) for user ID 2 ? In pdb-admin-user-settings ?

Works perfectly, thanks!!

In the PDb Documentation maybe you can include something about this?

https://xnau.com/work/wordpress-plugins/participants-database/participants-database-documentation/field-types/#rich-text-form-element

Thanks again! Cheers!!!