sg_cookie_optin issueshttps://gitlab.sgalinski.de/typo3/sg_cookie_optin/-/issues2021-04-28T06:38:14Zhttps://gitlab.sgalinski.de/typo3/sg_cookie_optin/-/issues/167save_history_webhook does not work, if default language entry point is not "/"2021-04-28T06:38:14ZManfred Eggersave_history_webhook does not work, if default language entry point is not "/"We have a multi language site. The entry point of the default language is "/de/". If the website is opened without any language path, the `\TYPO3\CMS\Frontend\Middleware\SiteBaseRedirectResolver` redirects the url to the default language...We have a multi language site. The entry point of the default language is "/de/". If the website is opened without any language path, the `\TYPO3\CMS\Frontend\Middleware\SiteBaseRedirectResolver` redirects the url to the default language entry point. E.g. `http://test.com/` is redirected to `http://test.com/de/`. This is also true for any additional parameters. So `http://test.com/?saveOptinHistory` is also recirected to `http://test.com/de/` without any parameters.
One solution would be to change the contents of `Configuration/RequestMiddlewares.php` to
```
return [
'frontend' => [
'SGalinski/SgCookieOptin/saveOptinHistory' => [
'target' => \SGalinski\SgCookieOptin\Middlewares\SaveOptinHistory::class,
'after' => [
'typo3/cms-frontend/site-resolver',
],
'before' => [
'typo3/cms-frontend/base-redirect-resolver'
]
],
],
];
```
So the Middleware is executed before the SiteBaseRedirectResolver.4.1.0GeorgiGeorgihttps://gitlab.sgalinski.de/typo3/sg_cookie_optin/-/issues/165Symfony command that forces the recreation of the script files based on a giv...2021-04-28T06:39:50ZStefan Galinskistefan@sgalinski.deSymfony command that forces the recreation of the script files based on a given site ids.t.s.t.4.1.0GeorgiGeorgihttps://gitlab.sgalinski.de/typo3/sg_cookie_optin/-/issues/160Spelling "essenziell"2021-04-09T11:29:44ZChristian RichterSpelling "essenziell"
A very "resourceful" customer of ours asked us to correct all occurrences of the word **essentiell** to **essenziell**.
We looked it up ourselves and unfortunately the customer was right. The Duden itself recommends the spelling with `...
A very "resourceful" customer of ours asked us to correct all occurrences of the word **essentiell** to **essenziell**.
We looked it up ourselves and unfortunately the customer was right. The Duden itself recommends the spelling with `z`.
https://www.duden.de/rechtschreibung/essenziell4.1.0GeorgiGeorgihttps://gitlab.sgalinski.de/typo3/sg_cookie_optin/-/issues/159Add option to make CSS and JS inline2021-04-26T11:43:25ZManfred EggerAdd option to make CSS and JS inlineGoogle PageSpeed Insights claims the generated CSS and JS in `<head>` as render blocking. Please add an option to output the contents of those files directly into `<head>`. This will make the resulting HTML larger of course but the warni...Google PageSpeed Insights claims the generated CSS and JS in `<head>` as render blocking. Please add an option to output the contents of those files directly into `<head>`. This will make the resulting HTML larger of course but the warning in Google PSI is gone and more points are gained.4.1.0GeorgiGeorgihttps://gitlab.sgalinski.de/typo3/sg_cookie_optin/-/issues/157Remove multiple slashes at the beginning of the generated footer urls2021-03-29T12:06:02ZStefan Galinskistefan@sgalinski.deRemove multiple slashes at the beginning of the generated footer urls```
$url = '/' . $this->removeCHashFromUrl(
$contentObject->getTypoLink_URL($uid, '&disableOptIn=1&L=' . $languageUid)
);
```
Probably a simplye ltrim(/) should do the trick.```
$url = '/' . $this->removeCHashFromUrl(
$contentObject->getTypoLink_URL($uid, '&disableOptIn=1&L=' . $languageUid)
);
```
Probably a simplye ltrim(/) should do the trick.4.1.0https://gitlab.sgalinski.de/typo3/sg_cookie_optin/-/issues/156Do Not Track - keep it optional2021-04-09T11:31:29ZStefan Galinskistefan@sgalinski.deDo Not Track - keep it optionalCurrently we have an active hardcoded check for this settings. Add an option to be able to activate the behaviour (disable by default). If enabled and DoNotTrack ist set, also log this into the console like: "Cookie Consent: DoNotTrack d...Currently we have an active hardcoded check for this settings. Add an option to be able to activate the behaviour (disable by default). If enabled and DoNotTrack ist set, also log this into the console like: "Cookie Consent: DoNotTrack detected - Auto-OptOut".4.1.0GeorgiGeorgihttps://gitlab.sgalinski.de/typo3/sg_cookie_optin/-/issues/155Cookie - Set "SameSite: None" to allow third party contexts (iframe context)2021-03-29T12:06:46ZStefan Galinskistefan@sgalinski.deCookie - Set "SameSite: None" to allow third party contexts (iframe context)Wir verwenden Ihre Extension für Typo3 auf einer unserer Kunden-Webseiten und ist folgendes aufgefallen: Wenn unsere Kunden-Webseite über iframe eingebunden wird, kommt die Cookie-Abfrage bei jedem Neuaufruf bzw. Seitenwechsel (innerhalb...Wir verwenden Ihre Extension für Typo3 auf einer unserer Kunden-Webseiten und ist folgendes aufgefallen: Wenn unsere Kunden-Webseite über iframe eingebunden wird, kommt die Cookie-Abfrage bei jedem Neuaufruf bzw. Seitenwechsel (innerhalb des iframes). Gibt es hier eine Möglichkeit, dies zu unterbinden/anzupassen? Oder ist das ein bekanntes Problem der Erweiterung?
Laut unserer Recherche sollte dies ja über das SameSite-Attribut (SameSite: None) funktionieren: https://web.dev/samesite-cookie-recipes/4.1.0GeorgiGeorgihttps://gitlab.sgalinski.de/typo3/sg_cookie_optin/-/issues/154Set Cookie for more Domains2021-04-12T17:49:10ZOliver KrammerSet Cookie for more DomainsHi,
We have an T3 Installation with 50+ Domains. But we want to show the Cookiebanner only at the first Time.
If the User navigate thought the Domains, we don't want to show it anymore.
I think i can do this with set_cookie_for...Hi,
We have an T3 Installation with 50+ Domains. But we want to show the Cookiebanner only at the first Time.
If the User navigate thought the Domains, we don't want to show it anymore.
I think i can do this with set_cookie_for_domain field. Is this right ?
Is it possible to use a function there ? Because if we add or remove a Domain we have to change all Domains by hand.
Do you have an idea how we can manage this ?
Thanks Oliver4.1.0https://gitlab.sgalinski.de/typo3/sg_cookie_optin/-/issues/153Accessbility Issues2021-04-26T12:04:06ZStefan Galinskistefan@sgalinski.deAccessbility IssuesAfter calling a page with the optin window overlaying the page, the keyboard focus is not in the
keyboard focus is not in the optin window, but in the page behind it. The
means that you can't enter the optin window without the mouse an...After calling a page with the optin window overlaying the page, the keyboard focus is not in the
keyboard focus is not in the optin window, but in the page behind it. The
means that you can't enter the optin window without the mouse and you can't enter the
cannot enter the page.
The checkboxes in the optin window
cannot be operated by keyboard (e.g. by people who cannot use a
mouse). However, this is required for barrier-free
necessary. Maybe you can make the checkboxes keyboard
keyboard - if necessary, you can (optionally) replace them with the standard browser checkboxes.
checkboxes of the browser.4.1.0GeorgiGeorgihttps://gitlab.sgalinski.de/typo3/sg_cookie_optin/-/issues/151close button behaviour2021-03-31T19:50:04ZThomas Jiraskoclose button behaviourHi,
the data protection officer of a client has pointed out to me that the close button should not set any cookies, not even the "cookie_optin" cookier.
Can this be changed?
Regards, TJHi,
the data protection officer of a client has pointed out to me that the close button should not set any cookies, not even the "cookie_optin" cookier.
Can this be changed?
Regards, TJ4.1.0https://gitlab.sgalinski.de/typo3/sg_cookie_optin/-/issues/100Support for Do not Track setting of browsers2021-03-26T13:23:23ZPeter KraumeSupport for Do not Track setting of browsersAre there any plans to support the "Do not Track" setting of browsers?Are there any plans to support the "Do not Track" setting of browsers?4.1.0