What has changed from Version 3.0 onwards

UI revamp of CookieYes plugin:

We have done a significant UI revamp for the plugin. Almost all of the features that were available in the old version are also available in the new version. You can now connect to the CookieYes web app (optional) to access additional features such as a cookie scanner and consent log. We have received feedback from our users, and we will continue to improve the plugin based on this feedback.

How do I manage/block scripts in the new version?

Due to a notice we received from the WordPress review team, we removed the feature to add scripts via the plugin. 

In connected state: If the plugin is connected to the CookieYes web app, go to the Cookie Manager on the web app dashboard and scan your site. The script will be automatically blocked by the plugin using the script URL pattern. (For a few third-party cookies that are not in our directory, you might need to block them manually by adding the script URL pattern as explained in the paragraph below) 

In non-connected state: You can still add scripts to the theme and block it prior to consent using the plugin dashboards’ Cookie Manager-> Add Cookie-> Advanced settings. You only need to add the pattern that identifies the script to the ‘Script URL Pattern’ field.

Some of the Shortcodes are not working anymore.

Support for some of the Shortcodes has been removed because they affect compatibility between the ‘plugin only’ and ‘web app connected’ modes. We are working on bringing back these Shortcodes based on feedback from users.

Does the plugin work without connecting to the CookieYes web app?

Yes, you can use the plugin without connecting to the Web app.

Does connecting to the web app sends user data to you?

We do not store any personally identifiable information about website visitors. We only store their masked IP addresses for websites with consent logs enabled. You can disable this feature if you wish.

Can we update the old plugins to the new interface? Is there a way to do that without losing configurations?

You can migrate from the legacy interface to the new interface without affecting the configurations. First, update to the latest version (v3.0.7 and higher) and follow the instructions in this link.

*DO NOT POST ANYTHING UNDER THIS POST*

The page I need help with: [log in to see the link]