Just like the static pages plugin the external PHP plugin overrides the 404 error handling. The content from the external PHP script is displayed as expected but above this content the error message from the language constant URL_NOT_FOUND is shown. The static pages plugin resets this error message to get rid of the error message. The change in this commit does exactly the same thing for the external PHP plugin.
The cookie consent banner is a notice to inform
users about our usage of cookies - it's not a
way to get consent, because cookies are used
whether you click "accepted" or not. The click
will just dismiss the banner.
As we do not really ask for consent - if we did,
we had to refrain from setting cookies unless
and until the users has accepted -, we shouldn't
make it sound like we do. Anything else would IMO
violate the GDPR requirement of "information
[...] in a concise, transparent, intelligible
and easily accessible form, using clear and plain
language" (Art. 12).
So, "I understand" (or "dismiss") instead of
"I accept".
Incidentally, I do not think that we need explicit
consent for the usage of cookies to the extent
that we do so. However, if we should need consent
for legal reasons, then we must implement this in
such a way that no cookies are set without consent.
Signed-off-by: Thomas Hochstein <thh@inter.net>
- If it does not have a legend, it should not be a fieldset
- Fix typos in German translation
- German translations for GDPR_BACKEND_* constants
- Bump version, document changes
This version uses locally hosted webfonts. In order to save space
and bandwith, we'll only bundle .ttf, woff and .woff2. That means
no support for legacy iOS (.svg) or IE < 9 (.eot).
References s9y/Serendipity#553
