On this demo page you can find some examples of how to configure Arsors.Cookie. I have created five cookies that are managed by Arsors.Cookie. The first one is the main cookie that is essential for each setup. Further I have created three different map/iFrame cookies: The first map cookie is initialized as an ID, the second and third are initialized as a Class. As examples I have also provided some different looks/contents for the error messages. Lastly there is also one video/iFrame cookie. For more detailed information check out the documentation. Everything the plugin can do will be explained there.
This cookie is the main cookie. It must always be specified and has 3 required options. Any type of content can be hidden by a cookie error message.
If you can see this container you have accepted the main cookie. Remember to delete your cookies if you want to see the cookie message when you reload the page.
Here in the demo you see three different cookie error messages for the same map cookie. You can create as many different error messages as you want.
Another Map Cookie
You can create the wrapper as ID or Class and use it accordingly. If you like, you can also create two different cookie elements for maps. So the user has to agree to two different map cookies to see both map contents.
And another Map Cookie
Whether iFrame, text, image or video: any content can be blocked. All you have to do is pack your element into a wrapper and give it an ID or a Class.
Main Cookie, again
If you create the cookie name as a Class you can use the error message repeatedly.
Maybe this text container can read your private data? I don't think so.