alanorth/hugo-theme-bootstrap4-blog
1
0
Fork 0
mirror of https://github.com/alanorth/hugo-theme-bootstrap4-blog.git synced 2024-11-18 02:07:05 +01:00
Code Releases Activity
08ae262312
hugo-theme-bootstrap4-blog/layouts/partials/cookie-consent.html

41 lines
1.2 KiB
HTML
Raw Normal View History

Use haven for GDPR popup instead of cookieconsent Haven is newer and more well maintained (and also it is actually open source instead of open core with an upsell to a paid subscrip- tion). Haven is configured to be 100% *opt-in* for Google Analytics, which means it does not load or send a hit until the user agrees. This is mostly a drop-in replacement, but translations need to make sure the following strings are updated: - cookieAccept - cookieDecline
2020-05-13 12:19:41 +02:00
{{ $cookieConsentScript := resources.Get "js/haven.umd.min.js" | resources.Fingerprint }}
<script src="{{ $cookieConsentScript.Permalink }}"{{ if not .Site.Params.disable_sri }} integrity="{{ $cookieConsentScript.Data.Integrity }}" crossorigin="anonymous"{{ end }}></script>
Add plumbing for cookie consent Set the cookie_consent_info_url parameter in your site's config to display a message about cookie usage to your users. See the config in `exampleSite/config.toml` for more info.
2016-11-13 13:13:17 +01:00
<script>
Use haven for GDPR popup instead of cookieconsent Haven is newer and more well maintained (and also it is actually open source instead of open core with an upsell to a paid subscrip- tion). Haven is configured to be 100% *opt-in* for Google Analytics, which means it does not load or send a hit until the user agrees. This is mostly a drop-in replacement, but translations need to make sure the following strings are updated: - cookieAccept - cookieDecline
2020-05-13 12:19:41 +02:00
Haven.create({
notification: {
layouts: Fix error in Haven invocation
2020-05-17 21:45:23 +02:00
{{ with .Site.Params.cookie_consent_info_url -}}
policyUrl: {{ . | absURL }},
layouts: Update Haven invocation If the user has configured a cookie consent information URL we will show it in the banner.
2020-05-17 21:42:56 +02:00
{{- end }}
Use haven for GDPR popup instead of cookieconsent Haven is newer and more well maintained (and also it is actually open source instead of open core with an upsell to a paid subscrip- tion). Haven is configured to be 100% *opt-in* for Google Analytics, which means it does not load or send a hit until the user agrees. This is mostly a drop-in replacement, but translations need to make sure the following strings are updated: - cookieAccept - cookieDecline
2020-05-13 12:19:41 +02:00
styles: {
background: '#428bca',
textColor: '#ffffff',
buttonBackgroundColor: '#f71559',
buttonTextColor: '#ffffff',
},
Add plumbing for cookie consent Set the cookie_consent_info_url parameter in your site's config to display a message about cookie usage to your users. See the config in `exampleSite/config.toml` for more info.
2016-11-13 13:13:17 +01:00
},
Use haven for GDPR popup instead of cookieconsent Haven is newer and more well maintained (and also it is actually open source instead of open core with an upsell to a paid subscrip- tion). Haven is configured to be 100% *opt-in* for Google Analytics, which means it does not load or send a hit until the user agrees. This is mostly a drop-in replacement, but translations need to make sure the following strings are updated: - cookieAccept - cookieDecline
2020-05-13 12:19:41 +02:00
translations: {
{{ .Lang }}: {
notification: {
policy: '{{ i18n "cookieLink" }}',
message: '{{ i18n "cookieMessage" }}',
accept: '{{ i18n "cookieAccept" }}',
decline: '{{ i18n "cookieDecline" }}',
}
},
layouts: retab after addition of modelines Done in vim using `gg=G` and then `:retab`.
2016-11-24 13:39:39 +01:00
},
Use haven for GDPR popup instead of cookieconsent Haven is newer and more well maintained (and also it is actually open source instead of open core with an upsell to a paid subscrip- tion). Haven is configured to be 100% *opt-in* for Google Analytics, which means it does not load or send a hit until the user agrees. This is mostly a drop-in replacement, but translations need to make sure the following strings are updated: - cookieAccept - cookieDecline
2020-05-13 12:19:41 +02:00
services: [
{
name: 'google-analytics',
options: {
layouts: Test for existence of Google Analytics ID Previously we showed the Cookie Usage banner if the site's config had a cookie consent URL specified. As of 2018-05 (GDPR) it makes more sense to only display this banner if the site has a Google Analytics ID set. Because we are using Haven for consent manage- ment we can now inject Google Analytics automatically after the user has agreed, so we no longer need to use Hugo's internal te- mplate.
2020-05-17 21:32:12 +02:00
id: {{ .Site.GoogleAnalytics }},
Use haven for GDPR popup instead of cookieconsent Haven is newer and more well maintained (and also it is actually open source instead of open core with an upsell to a paid subscrip- tion). Haven is configured to be 100% *opt-in* for Google Analytics, which means it does not load or send a hit until the user agrees. This is mostly a drop-in replacement, but translations need to make sure the following strings are updated: - cookieAccept - cookieDecline
2020-05-13 12:19:41 +02:00
},
purposes: ['analytics'],
inject: true,
}
]
});
Add plumbing for cookie consent Set the cookie_consent_info_url parameter in your site's config to display a message about cookie usage to your users. See the config in `exampleSite/config.toml` for more info.
2016-11-13 13:13:17 +01:00
</script>
Add Vim Modeline Comments to Files (#18) * Add Vim modeline comments to all relevent template files. * Add Vim modeline comments to a few other files. * Move modeline comments inside the template definitions in list and single. For some odd reason, putting them outside breaks the page generation. * Use template comments for modeline comments in templates. * Fix form 2 modelines.
2016-11-24 13:33:56 +01:00
{{- /* vim: set ts=2 sw=2 et: */}}
Copy Permalink