Opt in doesn't start analytics
When a user clicks to accept cookies, the script for Google analytics isn't started. This script is added in concrete5 > Dashboard > SEO > tracking codes while your description implies that when someone consents to the use of cookies all tracking should continue. I use concrete 5 8.1.0.
Comments (8)
-
repo owner -
repo owner Hi Julia, i was not able to reproduce with a fresh installation of 8.1.0
Here is a screencast: https://www.dropbox.com/s/js3d6ab63az0k24/810.mov?dl=0
Maybe there a conflicts with other add-ons or custom application.
If you want i can refund you the purcahse.
Fabian
-
reporter Hi Fabian, thanks for your reply. I did find the problem, just not the solution. It's because the function getServiceUrl() in cookiedisclosure doesn't get the right url of the page on sasmabv.com:
So the optIn function wants to get something from domain.com/?cID=/optIn instead of domain.com/en/eu_cookie_law/optIn Can it be because we have a multilingual concrete5 installation?
-
repo owner Hi Julia, yes. That seems to be the problem. I will test it, fix it (when i am able to reproduce) and give you feedback here. Fabian
-
repo owner Hey Julia,
I have tested it. Unfortunately i am not able to reproduce.
See here:
But i have a assumption. Could you change one line of code and then uninstall + reinstall the add-on?
Please change packages/eu_cookie_law/controller.php, line 107 from:
$singlePage = SinglePage::add($path, $pkg);
to
$singlePage = SinglePage::addGlobal($path, $pkg);
After change the file please uninstall + install again.
Let me now if that solves the problem that i will fix it.
Thank you Fabian
-
reporter That fixed it, thanks a lot for your quick replies and solution! This solution has only one tiny thing; somehow the cookie settings disappeared in the dashboard. I can access it by going to Single Pages and clicking the eu cookie law dashboard page so it's not a problem for me, but just so you know :)
-
repo owner Thank you for you feedback now this is official fixed.
-
repo owner - changed status to resolved
Fixed in v1.0.1.3
- Log in to comment
Thank you for the issue report. I will check this and give you my feedback.