Chrome Cookies Disabled

2 posts by 2 authors in: Forums > CMS Builder
Last Post: December 14   (RSS)

By KennyH - December 14 - edited: December 14

My Google Chrome has updated (Version 120.0.6099.109) and is now blocking all third-party cookies by default. When I am in the CMSB admin area, it says it is actively blocking cookies. I clicked on that notification and it allowed me to enable them for *this site for 90 days*

I didn't notice any problems with the software, but it makes me wonder what the impact would/could be in the future. See https://developers.google.com/privacy-sandbox/3pcd

On a website where I didn't enable cookies for another 90 days, and when I have an error show up in the developer console, this error also shows up:

Fatal error: setPrefixedCookie: Can't set cookie(loginsession, 9lTNyk...c1Jye), headers already sent! Output started in /home/cliweb/domains/clientwebsite.com/public_html/includes/nav.php line 93.
/home/cliweb/domains/clientwebsite.com/public_html/webadmin/lib/http_functions.php on line 313
https://www.clientwebsite.com/about/index.php

Any error causes it. In this case, I had left off a letter off in "contact_usRecords" (contact_uRecords) causing an undefined variable error. 

Is this something that will need an update to the software or is everything fine as is?

Thanks,

Kenny

By Dave - December 14

Hi Kenny, 

I can't reproduce this locally, are you able to determine which cookies it's blocking or send me some details so I can reproduce it (either via email or 2nd level support form)?

We shouldn't be using any 3rd party cookies in CMSB, although we may be stripping the www off the domain so the CMSB login cookie works on multiple versions of the same domain.  We'll need a test case to determine that.  I toggled the 3rd party cookie setting in Chrome but couldn't get any warnings locally.

For the "Fatal error: setPrefixedCookie:", I think that might be unrelated.  Cookies need to be sent before any HTML content so if an error is output before the cookie you'll get those "headers already sent" errors.  Sometimes PHP is configured to buffer output and it will work anyways, but the long term solution is to re-arrange the code so the cookie code comes first.  

Hope that helps, feel free to send me details on that page as well and I could give you better feedback once I see the code.

Dave Edis - Senior Developer
interactivetools.com