The ssl socket transport needs at least 4.3.0.
It's moot due to higher requirements for s9y
itself, but why not update it anyway?
Signed-off-by: Thomas Hochstein <thh@inter.net>
Currently supports:
* Show cookie consent layer
* Create footer link to privacy statement (internal, or also a staticpage allowed)
* Allow to enforce visitors need to confirm a checkbox when submitting comments
* Shows information about what s9y does in regards of DSGVO/GPDR
* Shows information about what s9y plugins do in regard of DSGVO/GPDR (new 'legal' property bag)
TODO:
* See todo.txt file.
* Most important: Go through EVERY plugin and add the legal property bag to any plugin that operates on user data.
* Allow to prevent session_start on frontend, allow to patch REMOTE_ADDR
* Warnings when plugin is not installed
+++++ HELP NEEDED +++++
* Remove documentation links to board.s9y.org
The 'website' property of plugins is used to
link to external documentation. board.s9y.org
does not contain such documentation, at least
not on its frontpage.
Signed-off-by: Thomas Hochstein <thh@inter.net>
* Remove dead documentation link.
c.seo-mobile.de does not exist any more.
According to
http://www.mobile-seo.de/archiv/21-serendipity-mobile-output-plugin.html
all documentation has been posted (only) there,
so is gone now.
Signed-off-by: Thomas Hochstein <thh@inter.net>
* [s9y_event_markdown] Update German translation.
Signed-off-by: Thomas Hochstein <thh@inter.net>
* [s9y_event_markdown] Add documentation.
German and English language documentation added.
Signed-off-by: Thomas Hochstein <thh@inter.net>
* [s9y_event_markdown] Update/change language files.
* Add an explicit SmartyPants option instead
of a simple "yes".
* Change (English and German) language files
accordingly.
* Change URLs to https to avoid redirects.
* Bump version to 1.26
* Update ChangeLog.
Signed-off-by: Thomas Hochstein <thh@inter.net>
The declaration of uninstall() didn't match
serendipity_plugin::uninstall, making PHP
spew warnings to the log.
Signed-off-by: Thomas Hochstein <thh@inter.net>
German language only, as there will be very
little need to link to German law and
decisions in a foreign language blog.
Signed-off-by: Thomas Hochstein <thh@inter.net>
* Bump version, add me as author.
Signed-off-by: Thomas Hochstein <thh@inter.net>
* Normalize whitespace.
Replace mix of spaces and tabs by spaces.
Signed-off-by: Thomas Hochstein <thh@inter.net>
* Add option for linking to buzer.de
Signed-off-by: Thomas Hochstein <thh@inter.net>
* Add Changelog.
Signed-off-by: Thomas Hochstein <thh@inter.net>
* Reformat and rephrase plugin configuration screen.
Remove HTML added in 88e58798af05a79543e89aa87705e85a325cc164
as it was not parsed.
Move link style description to info text.
Improve some phrases.
Signed-off-by: Thomas Hochstein <thh@inter.net>
* Add option to exclude headings from linking.
Signed-off-by: Thomas Hochstein <thh@inter.net>
* Update dejure-plugin to version 1.6 from upstream.
v1.6 was not yet published.
Improve fsockopen, switch to SSL, add user agent.
Signed-off-by: Thomas Hochstein <thh@inter.net>
* Bugfix: Don't cache results after errors.
djo_vernetzen_ueber_dejure_org() will return FALSE
instead of an output text if the API call fails
or results in any error.
But the "master" function djo_vernetzen() will call
integritaetskontrolle() anyway. The latter function
checks whether input and output texts match after
removing all added links. If the check succeeds, it
will return the output text; if the check fails, the
input text. So the result will always be TRUE.
And only after this will cache the output text if
it's not FALSE - which it can't be, ever. So if the
API call fails, the unmodified input text will be
cached.
But if we don't call integritaetskontrolle() after
API failures - which isn't necessary as the output
text is just FALSE anyway -, the FALSE will carry
through so nothing is cached.
Signed-off-by: Thomas Hochstein <thh@inter.net>
