Nifty

Hi Andrea,

We’re using the “date selector” field type, with the date format being set as “Age” (since the BP 8.0 update); we don’t think there’s anything custom.

Thanks for your ongoing assistance! ??

Hi Andrea,

Thanks for the clarification and extra information. ??

We’ve also noticed that without the code you supplied, a users exact birthday will be displayed on user cards when an age range search is done and then sorted by “Aged”, instead of only displaying their age as it does before the sorting is applied.

We know we can disable this sorting feature through the code on the dontdream.it link you provided, and remove the field value as you outlined, but it seems like a privacy issue for full birthdays to be displayed if this code isn’t used?

Thanks.

Hi Nithin,

Thank you for your reply and looking into this.

Yes, I can confirm this also happens when using the plugin you have linked above. Good to know that this is not a Hummingbird issue. I know this may be out of your scope but, in your opinion, would you say that BuddyPress is not reliable enough to be used with Redis at the moment?

Thanks.

Hi Andrea,

Thanks for the URL and the information; the search mode works with the URL you’ve provided.

I just don’t understand why the URL I was previously using wouldn’t work when the profile field type was a check box, but it would work when I changed the type to a drop down box?

The new URL you provided also adds the name of field 80 below the user card after the search is completed, when the other searches I have (with the old URL, but all drop down box types) don’t do this. I’d prefer the field name to not be there, if possible?

Thank you.

Just to clarify, the new setup we have is running BuddyPress and Hummingbird plugins only, on the default WordPress theme. All versions are the latest, including WordPress.

Thanks.

Hi Adam,

Thanks for your reply.

No, there are no other plugins involved. We’ve also tried this with a new setup and still face the issue. Once Redis in Hummingbird is disconnected (while Hummingbird stays active), the fields all appear in the “Signup Fields” tab. There is no CDN or server-side cache active, either.

Yes, Redis is confirmed to be working fine. The new BuddyPress brought in the ability to add fields to the signup form, while keeping them in separate tabs. Based on that, I can say it was working fine before the new BuddyPress update (as there was no adding fields to the signup area feature).

Thanks for your continued assistance.

Hi Andrea,

OK, thank you. Will do!

Hi,

Thanks for your reply and suggestions.

After some further investigation, it seems this issue is related to Cloudflare APO and it doesn’t seem like it can be resolved. Because of this, I will mark this thread as Resolved.

Thank you.

Hi Nicu,

Thank you. Will be keen to hear back from you.

Hi Nicu,

Thank you very much for looking into this and coming up with a fix :).

We are happy to wait in the meantime and we will report back and let you know how it goes once the update comes through. We had also added the subscriber role to the AUTH Codes prior to this thread and still experienced the issue of no role being assigned. Are you able to test this on your end also?

Thanks!

Hi t-p,

Thanks for your reply. Unfortunately, the checkbox reappears when I place the above code.

Hi Andrea,

I appreciate your efforts. I had suspected that may have been the case, but thought it was worth asking for some clarification. Perhaps you’re able to add the code above as an option in the plugin so others can enjoy the same feature?

Thank you.

Hi Andrea,

Thank you very much, it works! :D. Am I able to place this code in the functions.php file of my child theme instead?

Is there a way to also exclude the logged in user from the search results when an empty search is run (no options are selected and the search is submitted) and from the members directory?

Thanks again, really appreciate your help!

Hi,

Thank you for the prompt response and update!

From my initial impressions, it seems the newest update has fixed the issue. If it appears again, I’ll let you know.

Thanks again!