Hi, you have a few JavaScript errors on the page caused by other plugins which you should solve first. The error message shown by Cookie Law Info indicates that one of your scripts is messing with the JSON.parse method – this is a standard feature that is required for the plugin and many other features in your theme and plugins.
Hi, I just checked your site again and the main error has disappeared so I’m guessing you fixed that specific JavaScript issue on your website. I’ll mark this topic as ‘resolved’ but if you have any other issues please open another topic. All the best, Richard
Hi Richard,
We’re facing a similar situation. In Safari 5.0.5 on Snow Leopard clicking the Accept link does not do anything. Here’s your code.
<a href="#" id="cookie_action_close_header" class="medium cli-plugin-button cli-plugin-main-button" >Accept</a>
Could you please add a hard link for those browsers which can’t parse your javascript to cookie the browser and get rid of the notification?
Thanks!
Making the web work for you, Alec
Sure I’ll add that to a future version. No specific version number or time frame promised for release but it is on the product backlog.
As an aside- the issue that TheMic had was a different issue. Although it seemed so, on checking it wasn’t actually browser related.
Thread Starter
TheMic
(@themic)
Hi,
forgive me for my reply delay…
I fixed the problem changing other codes.
Now all works perfect! Thanks for the support!
Hi Richard,
Thanks for the rapid reply. Still you are offering us the worst of all possible worlds here. There are two good answers.
1. Yes, I’ll fix this for you now.
2. No, I can’t be bothered.
In the case of yes we will get our fix. In the case of no, we can either fix your plugin and fork it/contribute back (if it were on GitHub, anything else is too much hassle).
In this case of maybe we can’t take any action.
So please give us a date when you’ll make these improvements or tell us we are better to fork CookieLaw (which is the last thing on earth we want to do). There’s another deal breaker: logged in users get CookieLaw multiple times which really shouldn’t happen. The simplest thing in this case to avoid extra database calls, is logged in users just don’t get cookies at all (they are logged in!). All of this is an hour and a half of coding. It will take you more time to make excuses and deal with support queries than to fix these core issues.
Thanks for your time putting together CookieLaw. I don’t mind making a donation but I do expect the software to work in that case.
Making the web work for you, Alec
