Allow configuration of callback methods for onInit, onAccept and onDecline for services

BREAKING: Release aka version 5.0.0 only works with Neos 9

It is now possible to configure javascript code to be executed on init, accept or decline of a service.
See Examples/Settings.CookiePunch.FullServiceConfig.yaml for an example.

• onInit is called once per page load
• onAccept is called when the user consents to the service and also once per page load
• onDecline is called when the user does not consent to the service and also once per page load

Prevent Array from being passed to ConfigurationHelper

we need to prevent an array to be passed to the TranslationHelper
this can happen when we e.g. try to translate "Sandstorm", which will
return the corresponding yaml config

v4.4.1

Changelog

• Fix #18 by setting purposes and services to empty arrays in Settings.yaml

Feature: Contextual consent only for all services without modal or banner

4.4.0

Merge pull request #20 from sandstorm/19-feature-inline-consent-only-…

Support Neos 8.0

4.3.0

support neos 8.0

Bugfix: Pass remaining services via context to the Config fusion object

This fixes a breaking change that was introduced in version 4.2.0 by changing the type of Sandstorm.CookiePunch:Config to Neos.Fusion:Component. The keys for overriding configuration as described in the README did not work anymore because there was a new intermediate key "renderer".

Feature: Conditional Rendering of Services in Consent Modal

Now eel expressions are available for detecting at runtime if a consent switch is needed at all.

You can evaluate if a switch in the cookie modal should be rendered at runtime. This is useful for multi-site setups and to prevent unnecessary consent switches from being rendered if e.g. no youtube video has ever been added to the content.

support japanese translations

Merge pull request #15 from paavo/patch-1

feat: Added Japanese Translations

Minor Bugfixing

4.0.1

BUGFIX: addContextualConsent needs to be more robust

Adding more tags for blocking -> <audio>, <video>, <source>, ...

Now other tags can be blocked that could potentially send the visitors IP to a third party server.
The Eel helpers are more generalized.

    @process.blockTags = ${CookiePunch.blockTags(["iframe", "script"],value, !node.context.inBackend)}
    @process.neverBlockTags = ${CookiePunch.neverBlockTags(["iframe", "script"],value, !node.context.inBackend)}