template blocks cookie confirm component

Hi,

I updated the template to the latest version (Gavern v.3.12) and notices that the cookie confirm setting where you have to choose to accept or refuse cookies does not work any-more: the buttons do not trigger anything any-more.

This is the website with this problem:
http://www.each-for-sick-children.org/

I had this problem before and talked to the maker of the cookie conform component who advised me to set Javascript compression to Disabled: this solved the issue. Now I find it came back - while I still have Javascript inside the template at disabled.

Any advice on how to solve this issue much appreciated!

Thank you.

Greetings,
Paul

Hi

Can You tell me the correct url ? The one You mentioned is leading to "No server found" screen.

Hi,

Sorry that for you the link did not work: it is the live site, and for me it works okay.
However: I made a staging site to test possible solutions.
This is the link to this site:
http://www.staging-site.each-for-sick-children.org/

I checked lots of things - more or less at random, this is beyond my expertise - and found some things:
1. I had changed settings from the jQuery Easy plugin I use to get the yootheme Widget kit to work inside the template.
I changed the settings from loading on all pages to loading only on the pages that I use Widget kit on. This however made cookie confirm stop working: the buttons are shown but are dead.

After changing that to all pages I now have only one problem left:
after logging in I get an erroe messahe.
This is the error-message:
"You have succesfully logged in
JFILE: :read: Unable to open file: https://ajax.googleapis.com/ajax/libs/j ... ery-ui.css"

(I am using jquey version 1.11.1 for the jQuery Easy plugin. In the global configuration of the website I have Error reporting set to None.)

Can you tell me where this error message is coming from? And what I have to do to stop it.

Thank you.

Greetings,
Paul

Hi

Now both links are working fine. This has to be some connection problem. But I cannot see the error anywhere ;/ and plugin looks to be working now, so I'm guessing whatever You did did the trick.