Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chrome secure-by-default cookie policy #459

Closed
bagofarms opened this issue Jan 10, 2020 · 5 comments
Closed

Chrome secure-by-default cookie policy #459

bagofarms opened this issue Jan 10, 2020 · 5 comments
Assignees
Milestone

Comments

@bagofarms
Copy link
Member

Users have reported that the cookie settings in Chrome 80.0 (launching February 3rd) causes issues with UDOIT. More info: https://blog.chromium.org/2019/10/developers-get-ready-for-new.html

Here's an example in PHP of how to implement this change: https://github.com/GoogleChromeLabs/samesite-examples/blob/master/php.md

@bagofarms bagofarms added this to the v2.6.0 milestone Jan 10, 2020
@bagofarms bagofarms self-assigned this Jan 10, 2020
@bagofarms
Copy link
Member Author

Some more details in #460

@cidilabs

This comment has been minimized.

@bagofarms
Copy link
Member Author

It looks like that patch file removes an input button. Did you mean to attach a different file?

@bagofarms
Copy link
Member Author

Nevermind, I have the code in my email notification. It looks like the best place for this is in config/settings.php. It shouldn't be too bad (famous last words).

@cidilabs
Copy link
Contributor

Sorry, not sure where that file came from. Here's the intended patch.
udoit_459.patch.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants