Nifty

Hi Andrea,

You’re right about it being complex!
Thanks for your help and the link though; we really appreciate it. ??

Hi Andrea,

Thanks for your response and the information; do you know if this is a fix BuddyPress are already planning to implement?

No worries, Andrea! ??

Hi Andrea,

Thanks so much; this worked perfectly! ??

Hi,

OK, thank you. ??

Hi,

Thanks for your reply. ??

We won’t be using Page Caching. In this case, should we keep the single define('WP_CACHE', true); that we added to the wp-config.php file? Essentially, the question then becomes, do we need the above line in the wp-config.php file for Hummingbird to correctly interact with Redis?

Thanks.

Hi Andrea,

You’ve completely got us there! Somehow we missed the obvious solution staring us in the face. ??

Thanks again for your help.

Hi Andrea,

Here’s the site we’ve been testing it on.

The profile field we’re testing is “Connection”; it’s the first drop down select box on the home page search. We’re creating a dating site; our hope is that a visitor who comes to the site and doesn’t have a preference over connection type (e.g. long term dating, short term dating, etc.) could search for “Anything” and the search results would show all users, whilst also still respecting the selections made from other fields within the same search (such as gender).

Thanks.

Hi Andrea,

We haven’t had any luck with this code either, we’re afraid; it doesn’t seem to be altering the displayed results of any searches.

Thanks again for your help. ??

Hi Andrea,

Thanks for getting back to us so quickly!

We’ve tried the code, but only users who have chosen “All” are shown, rather than every user. Is there anything else we could try? ??

Thanks for your help.

Hi,

Thanks for getting back to us. We’ve been able to turn that feature off and all is well now!

Thank you for your help. ??

Hi,

Thanks for your reply and suggestion! We will test this out some time. ??

Thanks again.

Hi Andrea,

That’s really helpful information, thank you! ??

We’ve notified the Gwangi/Grimlock team of the issue; no solutions from them yet, but we can let you know the outcome, if you’re interested.

Thanks.

Hi Andrea,

Thanks for your ongoing help.

When we don’t run a search, the user cards only show the user’s name and gender; age isn’t shown unless a specific search for this is done. We are using [bps_directory] shortcode in our member directories.

We’ve been able to replicate the issue on both our main site, and on a clean install that doesn’t have any customisation, so don’t believe there’s any custom code that’s causing this.

Through further testing on our main site and a clean install, we think the issue is caused by the Grimlock plugin that comes with the Gwangi theme; when Grimlock is turned off, the user card will only show age. The issue can be replicated through the following steps on a Gwangi demo site here: https://dating.gwangi-theme.com/
1. Complete search on home page for age range only – user cards will show ages.
2. Sort results by “Age” – user cards will now show exact dates of birth, instead of age.

Thanks.

• This reply was modified 3 years, 7 months ago by Nifty.

Hi Andrea,

We’ve done a bit more testing, and we think we have worked out what’s causing this.

When the persistent search is set to “No” on the profile search form being used, the user’s full birthday will be displayed on their user card when search results are sorted by Age. If persistent search is set to “Yes”, only their age will be displayed.

Thanks.