Bug 36077 - Create separate cookie options for the staff interface
Summary: Create separate cookie options for the staff interface
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Staff interface (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on: 35348
Blocks:
  Show dependency treegraph
 
Reported: 2024-02-13 10:09 UTC by Aude Charillon
Modified: 2024-04-24 10:17 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aude Charillon 2024-02-13 10:09:27 UTC
Bug 27378 created HTML customizations for CookieConsentBar and CookieConsentPopup. Despite being listed under the OPAC section of the list of display locations when creating the customizations, these are displayed in both the Opac and the staff interface. This is an issue as the staff interface uses different essential cookies and could have different optional ones.

We need two separate sets of cookie-related system preferences and HTML customizations: one for the Opac and one for the staff interface.
Comment 1 Aude Charillon 2024-02-13 10:17:16 UTC
Note: this issue was also discussed in bug 34793 (comments 20 to 23 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34793#c20)

I imagine we would need system preferences like: OpacCookieConsent and StaffCookieConsent, OpacCookieConsentedJS and StaffCookieConsentedJS; plus HTML customizations OpacCookieConsentBar and StaffCookieConsentBar, OpacCookieConsentPopup and StaffCookieConsentPopup.
Comment 2 Mirjam Vantieghem 2024-03-12 10:24:25 UTC
+1
Comment 3 Mirjam Vantieghem 2024-03-12 10:32:49 UTC
Not sure if this belongs here or in a separate bug:
When the CookieConsent system preference is set to require, the CookieConsent also comes in the pop-up window of the Z39.50/SRU search from the cataloguing module on the Staff client, even after confirming consent in the staff client. 
That seems unnecessary, unless there are other cookies in the Z39.50/SRU pop-up window.
Comment 4 Katrin Fischer 2024-03-12 20:58:21 UTC
(In reply to Mirjam Vantieghem from comment #3)
> Not sure if this belongs here or in a separate bug:
> When the CookieConsent system preference is set to require, the
> CookieConsent also comes in the pop-up window of the Z39.50/SRU search from
> the cataloguing module on the Staff client, even after confirming consent in
> the staff client. 
> That seems unnecessary, unless there are other cookies in the Z39.50/SRU
> pop-up window.

Can you please report a separate bug as "bug"?
Comment 5 Mirjam Vantieghem 2024-03-14 10:17:37 UTC
(In reply to Katrin Fischer from comment #4)
> (In reply to Mirjam Vantieghem from comment #3)
> > Not sure if this belongs here or in a separate bug:
> > When the CookieConsent system preference is set to require, the
> > CookieConsent also comes in the pop-up window of the Z39.50/SRU search from
> > the cataloguing module on the Staff client, even after confirming consent in
> > the staff client. 
> > That seems unnecessary, unless there are other cookies in the Z39.50/SRU
> > pop-up window.
> 
> Can you please report a separate bug as "bug"?

Bug #36316 created.
Comment 6 Katrin Fischer 2024-03-14 21:49:02 UTC
(In reply to Mirjam Vantieghem from comment #5)
> (In reply to Katrin Fischer from comment #4)
> > (In reply to Mirjam Vantieghem from comment #3)
> > > Not sure if this belongs here or in a separate bug:
> > > When the CookieConsent system preference is set to require, the
> > > CookieConsent also comes in the pop-up window of the Z39.50/SRU search from
> > > the cataloguing module on the Staff client, even after confirming consent in
> > > the staff client. 
> > > That seems unnecessary, unless there are other cookies in the Z39.50/SRU
> > > pop-up window.
> > 
> > Can you please report a separate bug as "bug"?
> 
> Bug #36316 created.

Thank you, Mirjam!
Comment 7 gclg 2024-04-24 10:17:16 UTC
Where access to the Staff client is non-public/limited by IP range etc this would negate most cookie settings, so the option to select OPAC/Staff Client as a single option, or opt for both would be welcome.