I was directed here by customer service to submit to the Idea Box a request for functionality that would allow us (and YM) to comply with GDPR. Unfortunately, the Idea Box is not working—trying to access it results in the page with the band-aid and "an error occurred on the page." Here is the content of my idea box post: It's currently not possible to allow members to opt out of the directory search. At the same time, under the GDPR, members can make a request that we not process their data in this way. There are amazingly cumbersome workarounds for this problem, such as creating a corresponding private member type for all of our current member types and assigning these as needed, but having two member types for each member type would make managing them difficult and error-prone. ​It is possible, of course, to completely do away with the directory feature, but this would truly be an instance of throwing the baby out with the bathwater. Please make it easy to allow members to opt out of directory searches.

I received an error message a number of times yesterday when in Unity, as well as, when in the YM system.

I, too, am frustrated that the GDPR modifications were not released by the deadline. We were counting on them as part of our compliance plan.  However, I think I have a suggestion that may help you.  Add a custom field to "opt-in to your directory" then use that field as part of your directory search set up criteria.  It should be a fairly easy fix. 

Christina, that's a great idea. 

Thanks, Christina. I'll give that a try.

I must be doing something wrong. I created a custom field (single-select drop-down) and used a batch import to give all members a Yes in this field. I then used the Directory Search Configuration to restrict search results to those that match this criteria: Yes. I then edited the profile of a member to change the value of the new field to No. But this member still shows up in the directory results in the site search. At the same time, requiring either a Yes or a No in the new field causes zero results to be returned if specifically using the directory search. Using the administrative backend directory search, if I search for those with No, I see the member for whom I changed the field to No. Similarly, if I search for those with Yes in this field, the admin backend directory search returns everyone except the member with No in this field. So the field is working and is correctly populated. It's just the directory search filtering that is not working properly.

Sorry for the slow reply, I was on vacation last week.  Did you put a ticket in about the directory search filtering?