Hey Kyle!

The Business Directory can be used as a "business hub" without using it on the front end. This way, you can associate Calendar events with venues, and businesses with banner ads, and so forth. Personally though, I would look into the Calendar upsell functionality - it's a great reason to get the full directory.

The venue library in Calendar is meant to be a "quick list" of your most commonly used businesses. You can have more than 10 - 15... there is not a physical limit it's just more that at some point it becomes unwieldy. It does put listings in alphabetical order and allows for type-ahead. But it isn't meant to be a database of listings.

But in general, I would use the Business Directory for most listings, and then the venue library for the ones you're using like every day to save you a few clicks. The venue library is useful for when you're entering things in manually.

Hope this helps!

This fix is now available.

Hi guys!

Thanks for reporting this. Yes, we've confirmed this is an issue and it is fixed in the next upcoming release.

We'll have a fix for this next week.

I created a ticket to have a dev look into this.

Hi guys! We are still working with our legal team on a solution. There are a lot of moving parts here!

We did issue a potential fix today that will help (we hope) the situation where a Facebook scraper comes from EU and you end up sharing the GDPR error message to Facebook (even though you and the article is in the US). Yuck! And, I'm very sorry if that happened to you. We added article meta data to the error page in hopes of preventing this issue. Let me know if you experience this again with articles posted after 12 pm today or so.

In terms of upcoming changes, we are working on several different scenarios and we hope to have at least our next phase done in a few weeks. Hopefully!

For the time being, you may want to get a head start by identifying any scripts, third parties or widgets that you use on your site and determine if they are GDPR compliant.

We are working on a new method that will allow individual items that likely require consent (i.e. some ads or widgets) to be blocked while allowing the full page to be read by EU/EEA users. This will be optional per site after you have determined your own compliance levels with your legal staff. We are working to have this available in the next week or so.

Separately, we are looking at consent tools and other options which can provide more fine-grained compliance other than blocking or widget blocking. This is still being investigated.

We are definitely looking at some different options. There were huge industry changes being made even up through May 25 itself! As we said in the announcement:

"Until more clarity regarding methods of offering compliance is understood across the industry, our initial and necessary step is to block persons we recognize as coming from the EEA and EU to both preserve the rights of their citizens and ensure that our customers’ sites are not in violation."

Anyway, we are having another meeting this afternoon and I will try to share more details after that.

Thanks Kevin! I've also spoken with some people behind the scenes as well and that seems to be pretty universal right now. Thanks!