Overview

Cookies-Notice widget is content-glass widget that notify Website visitors about usage of Cookies in a website, when CG is installed. This specific widget is available only to managed-app admin users (users that installed Content-Glass on their websites), from the "Advanced" widgets gallery.You can see an example of this widget when visiting this website. The popup on the bottom is cookies-Notice widget.

Step 1 - Login as managed-app admin

Step 2 - Create The Widget

Before you create the widget, it is recomanded to move to home page of your website and do it there. The reason for doing this will be clarified later.

Open again CG Menu by clicking the button -> click Widgets -> select 'Advanced' library -> click ONCE on the Cookies-Notice widget icon

A widget is created on the bottom of your website.

Step 3 - Starting the edit mode

You may want (this is optional!) to edit the widget. For example you may want to change the cookies-notice text, change the label of the button or change colors and style of major widget elements. you can do all of these, as will be explained in the next step, but first you need to get into edit mode of widget.

Move the mouse on the top-right corner of widget area, and when you see the menu icon click it. Then select Edit.

Step 4 - Edit the widget

Editing on Cookies-Notice widget is handled inline, on widget itself. When you turned on the edit mode some areas of the widget has become editable. In addition you will use the Developer console of chrome to edit style of major elements. These are the things you can edit:

a. Text on cookies notice - Touch the text and you will see it is editable.

b. Label of accept button - Touch the accept button and you will see it is editable.

c. CSS class and style attributes of the following elements:

'cg-CookiesNotice' - the top level container element of the widget

'cookies-notice-text' - the container of the text
'cookies-notice-button' - the button
'cg-cookies-read-more-link' - the 'Read More' link for reading more details

To edit CSS class and style attributes you will have to open the developer console of chrome. The easiest way to do that is to right-click when standing on the widget area, select "Inspect" menu and the console will be open. Search for "Elements" tab, and use text search to search for the names shown above. Once an element is selected, you can edit its style. Your changes, made to elements mention above will be saved, when you will save the the widget.

If you wanto to change the 'href' attrinbute of the 'Read More' link, you can also do that by editing the HTML in chrome developer console, and then saving the widget. When saved, new href will be stored and apply for next time widget is loaded.

When you done with editing, click the same button on the top-right corner of the widget. If you are planing to change color to 100% black you will not see the button well, so make sure to remember where it is so you can click it after changing background color.

Step 5 - Moving the widget to public layer

Finally, when widget is ready, after making all changes, you can move the widget to public layer. Moving a widget to public layer is permitted only for managed-app admin user and it means that all the visitors of your websites will be able to view the widget, also without having to login to Content Glass. In other words, the widget is becoming a content that publicly presented on your website. Note that you can always move the widget back to private layer, you can always make changes to widget, also when in public layer, and if you like you can always delete the widget (if you logged-in).

You will see that you have few public layers to choose from:

a. Public page - meaning share the widget only on this page (this is why you was asked to move to home page prior to creating the widget).

b. Public domain - share the widget on all pages of your domain.

c. Public TLD - share the widget on top level domains (all pages) , which is less relevant to this cases.

d. TLD Page - share the widget on the same page across all top-level-domain websites, which is also less relevant in this case.

Note: There is no need to be in edit mode for moving the widget to different layer. So, altough picture below was taken when widget was in edit mode, in your case, you should not do that because it may cause some confusion of when data is saved. So, no edit-mode when changing layers!

How is this widget working?

Cookies-Notice is very simple widget with very basic logic. The widget shows a popup on the bottom of the page with a notice about using cookies and accept button. When the user click the button the operation is stored on the browser cache. So next time the user get into your website, this record is detected and the widget will not be presented. And since the record is saved on client-side, widget state is kept per individual user. That all this widget do!

Important note! using tis widget does not imply anything about your privacy policy and/or service-terms and/or a compliance with such and such regulations. It is only a friendly tool you can setup in minutes.

The state of the widget, indicating user clicked on "Accept" button, is stored as part of Content glass, and can be deleted if the user clear the cache from content-glass menu. If you (the admin) need to clean the cache it is adviced to logout first and then clean the cache. Then re-login.

Note: when admin click accept, the widget is first shown as disapear, but if you refresh the page it will apear again with added text saying: "*widget was accepted but it presented to admin" to allow admin to edit and manage the widget.

Finally - do you need more of this widget?

I consider this first version of the widget as experimental. If you need more of this widget, for example the ability to control when to locate the widget, and ability to call some callback function when user click accept and things like these, adding link to text and more, let me know. I would love to consider more features based no your feedback.

Also, found some problem? Need some help? feel free to open a ticket. Note that since this is a free tool, online support is provided only via tickets, and according to capacity and company considerations.