https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31642

--- Comment #17 from Marcel de Rooy <[email protected]> ---
Point [C]
Actually two reasons:
[1] To illustrate the need for this change, please look at this part of
opac-patron-consent.tt (see also bug 31503)
                            [% IF consent_type == 'GDPR_PROCESSING' %]
                                <legend><h2>Privacy policy
consent</h2></legend>
                                [% rma_privacy_url = { en =>
'https://www.rijksmuseum.nl/en/privacy-policy', 'nl-NL' =>
'https://www.rijksmuseum.nl/nl/privacybeleid' } %]
                                <div class="alert alert-warning">
                                    <p>In order to keep you logged in, we need
your consent to process personal data as specified in the privacy policy linked
below.</p>
                                    <p>If you choose to withdraw your consent
we will <strong>remove your account</strong> within a reasonable time and you
should log out now.</p>
                                </div>
                                <p>I have read the <a target="_blank" href="[%
rma_privacy_url.$lang | url %]">privacy policy</a> of Stichting Het Rijksmuseum
and the <a target="_blank" href="[% Koha.Preference('PrivacyPolicyURL')
%]">additional explanation</a> for the library catalog, and agree with your
processing of my personal data as outlined therein.</p>
                            [% ELSIF consent_types.$consent_type %]
                                [% SET consent_title = (
consent_types.$consent_type.title.$lang || consent_types.$consent_type.title.en
) %]
                                [% SET consent_desc  = (
consent_types.$consent_type.description.$lang ||
consent_types.$consent_type.description.en )  %]
                                <legend><h2>[% consent_title | html
%]</h2></legend>
                                <p>[% consent_desc | html %]</p>
                                <p>Do you agree?</p>
                            [% ELSE %]
                                <legend><h2>Consent for [% consent_type | html
%]</h2></legend>
                                <p>Do you agree?</p>
                            [% END %]
Being fed by:
foreach my $consent_type ( sort keys %$consent_types) {
    push @consents, $patron->consent($consent_type);
}
=> We could move a lot of this to additional contents. Currently I provide
those texts for a custom newsletter consent from the consent plugin itself.

[2] As second reason, an architectural one. Instead of keeping the growing list
of names for available html blocks in the template, we control it via
Authorised values. No need to adjust additional-contents.tt anymore for adding
a new standard or custom html block.

-- 
You are receiving this mail because:
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to