- This topic has 22 replies, 3 voices, and was last updated 2 years, 7 months ago by
.
-
Posts
-
Hello,
Grimlock appears to be causing a privacy issue when sorting users by age after an age range search is completed; instead of a user’s age being displayed on their user card, their full date of birth is displayed instead.
The issue can be replicated through the following steps on the demo site here: https://dating.gwangi-theme.com/
1. Complete a user search on the 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.We’ve tested this on both our main site and a clean install that has no customisation; the issue stops occurring when Grimlock is deactivated, but will reoccur once Grimlock is activated again.
Thanks.
Hi Nifty,
Thank you for bringing this issue to our attention.
We will investigate and be back to you as soon as possible. 🙂
Best,
Hi Manathan,
We’ll look forward to hearing back from you. 🙂
Thanks.
Hi Nifty,
We’re experiencing a much larger number of requests than usual so our wait times are longer than expected. We’re working hard to get back to you as quickly as we can and we really appreciate your patience!
Thank you for understanding.
Hi Nifty,
We’re still investigating this issue to find out how we can help you.
We will be back to you ASAP.
Thank you for your patience.
Regards,
Hi Olivier,
No worries; thanks for keeping us updated.
Hi Nifty,
Thank you for your patiente.
Can you please go to Dashboard > Users > Profile Search and make sure that the Persistent Search is set on Yes? Once this option is correctly set, can you please make sure this issue still appearing?
We’re waiting for your feedback. 🙂
Best,
Hi Manathan,
When persistent search is set to “yes”, the users full date of birth does not display (their age is displayed); this is how we’ve gotten around the issue whilst awaiting a fix.
We still feel that this is potentially quite a significant privacy issue, and needs to be resolved ASAP. It’s also worth noting that this issue is causing the users full date of birth to display even though the date format for the profile field is set to “Age”; so in theory, users should therefore never be able to see the date of birth of other users because it’s set to “Age”, but it becomes publicly visible when Grimlock is activated and search results are sorted by the date selector profile field.
Thanks.
Hi Nifty,
Thank you for your feedback.
I’m glad to read that this quick solution solves temporarily this issue. We’ll investigate to find out how we can fix that in the next update.
We’ll be back to you as soon as the update is available.
Thank you for your patience.
Best,
Thanks, Manathan. We’ll look forward to the update. 🙂
Hi Nifty, 🙂
Waiting the update, simply add the following code snippet to your website:
/** * Hide meta results in cards to hide the date of birth */ .card-body-members-item .item-meta[class*="_details"] { display: none !important; }To add this code snippet to your site, we recommend that you paste it to the Custom CSS panel of your WordPress Customizer. Just go to your dashboard and navigate to “Appearance > Customize > Additional CSS”.
Regards,
Hi Manathan, 🙂
Thanks for the code; the only issue is that it removes all user card info. That is, if a user conducts a search for an age range, they will no longer see the age of other users that they have searched for. Is it possible to still show the user’s age whilst still always concealing the date of birth under the above circumstances?
Thanks.
Hi Nifty,
Can you please make sure that Birthdate is activated in Customize > BuddyPress > Directory? Please find the attached screenshot.
Best,
Nifty, I think there is something I missing. 🤔
I though activating the Persistent Search solved this issue. Does this option create another issue? On our end, we can reproduce this issue, but it was indeed related to the Persistent Search. Activating this option solved this and there was no other issue to our knowledge.
In that case, this issue should be solved. Am I correct?
Best,
Hi Manathan,
Birthdate being activated via the customise menu doesn’t seem to change anything from what we can see on our end.
You’re correct that turning persistent search to “Yes” does stop the user’s full date of birth being displayed as a workaround, however we don’t necessarily want to have persistent search set to “Yes”. Is there any way to still have persistent search set to “No” without this issue?
Thanks again for your help. 🙂
Hi Nifty,
This issue seems to be related to the association of Kirki plugin and BP Profile Search plugin. Unfortunately, Grimlock needs Kirki to work perfectly. At this point, the best solution is to set the Persistent Search on Yes.
Be sure we’ll investigate further to find out how we can solve this. We added this in our to do list, but we have a lot to work on so no release date can be disclosed.
We thank you for you comprehension.
Sincerely,
Hi Manathan,
We appreciate you getting back to us and will look forward to any future updates. 🙂
Thanks.
Thank you for your understanding Nifty. Be sure we do our best.
We’ll be back to you as soon as the update is available. 🙂
Cheers,
Hi Nifty,
Thank you for your patience.
We have investigated and analyzed all possible solutions. However, it seems that each solution has its limitations and some could cause a different issue elsewhere. This issue is a limitation between Kirki and BuddyPress Profile Search.
To fix this, I’m afraid the best solution is to set the Persistent Search on Yes.
If you really want to solve this issue in another way, we recommend that you hire a freelancer to do this work for you. In this case, come back to us and we will provide you with an explanation to give to your developer to help him find another solution, even though it may cause other issues.
If you’re on a tight budget, we recommend you to require the services from Envato Studio freelancers (https://studio.envato.com/explore/websites-programming). This web platform gives you access to developers who have already experience with theme customizations, and for very competitive prices.
Best,
Hi Manathan,
Thanks for investigating this further and following up; we appreciate it. 🙂
Are you able to post more details about the issue in a private reply so that we can follow-up with a developer?
Thank you.
This reply has been marked as private.
Thanks, Manathan.
You’re welcome Nifty!
We hope this will help you.
Cheers,
Hi there,
This topic has been inactive for a while now so we will be closing it to keep the forum tidy. Don't hesitate to create a new topic if you still need help and we'll be glad to help you!
Best regards,
The Themosaurus team.
The topic ‘Grimlock showing user’s full date of birth – privacy issue.’ is closed to new replies.
