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
Allow force disable cookies #16258
Comments
We'd likely need to have this feature on a "per site" basis and "overall" basis. By default the feature is "managed overall" but could be changed to configure it on a "per site" basis. Then we would use the measurable settings. The custom public function shouldAddTrackerFile(&$shouldAdd, $pluginName)
{
if ($pluginName === 'PrivacyManager') {
$config = new Settings();
$shouldAdd = !$config->hasCookiesDisabledGlobally();
}
} |
We would also want to add an "Informational" diagnostic check for this eg in Not sure how it can be printed in the diagnostic check though when it is configured on a per site basis. Maybe then we can't show it since there could be many sites. Maybe we'd then rather show a summary: Number of sites having cookies disabled enforced: X, number of sites having cookies disabled not enforced: Y |
@tsteur I've already implemented #16259 with new SystemSettings / MeasurableSettings classes, and here is another feature that should be available on a global and per site base. I'm wondering if it might maybe make sense to introduce a new class structure for that. E.g. each plugin could define |
Generally it sounds good but thinking we might not have enough time before the release to do this. Also would need to think this through a bit more as it might not only be |
When you want to make sure that across all sites cookies should never be used. It's otherwise incredibly difficult to ensure all sites implement it correctly.
What this feature would do is
tracker.js
in the plugin that makes ideally sure that cookies cannot be enabled in the client (eg we can overwrite some tracker methods liketracker.setCookieConsentGiven=function(){}
etc and we can automatically call tracker.disableCookies())Tracker/Request
never return anyvisitorId
. So even if the client did send a visitorId, we would ignore it and rely on fingerprint.Out of scope for now be removing metrics like Unique visitors that wouldn't be correct anymore.
The text was updated successfully, but these errors were encountered: