Compatibility above 4.2.5?

Hi Jurgen, I believe that this may be related to another issue. I am currently running the plugin (with billing city working) on WordPress 4.4.1 and WooCommerce 2.4.10.

Do you by chance have Admin Columns Pro installed and activated? This is currently the only known plugin compatibility issue.

Out of curiosity, could you please tell me a few billing cities that you have searched for that are NOT working? I will run these on my end to see if I can replicate the issue.

Thank you!

Hi Dale,

I have this installed on WP 4.4.1 and latest Advanced Custom Fields to add two text area custom fields. I’ve included both fields in Better User Search settings, but my search does not produce the desired results. i.e. searching for a term in the ACF custom fields, but nothing comes up.

Also, another question is about scale/performance. Would it work fast enough for a site with more than 10,000 users, where each user account has about 20 custom fields attached?

Thank you,
Bowo

Hi Bowo,
I will install Advanced Custom Fields and take a look to see if I can figure out the issue.

As for scale/performance, my primary installation has over 16,000 users with about 50 meta fields each, and the query averages about 2.8sec. It does take noticeably more time to search when there are more users, but I have minimized it as much as I could at the current time. I am constantly trying to figure out more ways to optimize, and would be open to any suggestions anyone would like to provide!

I will let you know what I find out about Advanced Custom Fields.

Kindest regards,
Dale Higgs

Thank you for the rapid response Dale. Much appreciated.

There is only one plugin in the repository that I know of, that automatically includes all user meta in search… WP CRM… even ajax powered. Maybe there’s something in its codebase you can learn from?… Obviously, being able to define which custom fields to include in search is still a good thing to have.

Good to know about performance. I wonder what your hosting/server specifications are? Curious to see how far hardware power I can throw at this to push performance at larger userbase.

Many thanks!
Bowo

Bowo, could you please confirm whether you added the “field_name” or the “_field_name” meta keys on the options page?

I setup two custom fields, “test_field_1” and “test_field_2” and added both “test_field_1” and “test_field_2” to the searchable meta fields in the plugin options, and the search returned the expected results.

Please note that I performed this test on a very basic installation, using the latest version (1.0.4) of Better User Search, which I published just hours ago.

I hope to hear from you soon.

Ah… that might have been the cause. When I select the field names without the underscore, it works correctly now (v1.0.4). I did not realize there are two versions of the field names. Thanks Dale!

On an unrelated note, upon deleting v1.0.2 and activating v1.0.4, I got this error: “The plugin does not have a valid header”. But if I go to “Installed plugins” page and activate from there, it was OK.

Now, let me try to mark this compatible with WP 4.4.1 and leave a nice review. ??

Done. ??

https://www.ads-software.com/support/topic/nice-and-simple-performant-too?replies=0

I’m glad that worked out for you Bowo!

I will see what I can do about auto-detecting the Advanced Custom Fields plugin and hiding the accompanying underscored meta keys. I cannot hide all underscored meta keys as a lot of plugins use them in a meaningful manner.

Also, thank you for letting me know about the valid header error. I have never heard of this before, but I am guessing that it is likely due to the extra text I have contained in it. I’ll look into it.

Lastly, thank you for the 5-star review, it is greatly appreciated!!!

The least I can do for this nice plugin you’ve built, maintain and support. ??

As for auto-detection and hiding, maybe you also want to check if other custom field creator type-of-plugins do the same things as well, and limit your auto detection to custom fields produced by those plugins, thus, leaving custom fields produced by all the other plugins intact.

Or, maybe there could be a simple algorithm to it?
1. Detect all custom fields with underscore prefix and remove the prefix.
2. See if there are duplicate custom field names
3. If there are duplicates, remove the ones with underscore from the list in settings

Hi Dale,

I just updated to WP 4.4.1, WooCommerce 2.5.1 & Better User Search 1.0.5 and I can search for users billing & shipping address. Thanks!

Best regards,
Jurgen

That is wonderful news, Jurgen! Thank you for reporting back that the update was a succes for you. Again, I sincerely apologize for the delay in getting this resolved for you.

If you ever come across any further issues or have any feature requests, please do not hesitate to create a new support topic.

Thank you again,
Dale Higgs