Bug 34892 - Convert RestrictedPageContent system preference to HTML customization
Summary: Convert RestrictedPageContent system preference to HTML customization
Status: In Discussion
Alias: None
Product: Koha
Classification: Unclassified
Component: OPAC (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement
Assignee: Owen Leonard
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks: 26050
  Show dependency treegraph
 
Reported: 2023-09-22 16:55 UTC by Owen Leonard
Modified: 2023-09-25 17:34 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Owen Leonard 2023-09-22 16:55:23 UTC
Building on 22318, the RestrictedPageContent system preference should be converted to an HTML customization.
Comment 1 Owen Leonard 2023-09-22 17:47:40 UTC
This one presents a unique problem because we can replace two system preferences, RestrictedPageTitle and RestrictedPageContent.

The HTML customizations system can display more than one entry, so someone could create multiple entries to be displayed on the page, each with their own title. But we can only show one page title (in the <title> and the breadcrumb navigation).

How do we pick which title to show?
Comment 2 Owen Leonard 2023-09-22 18:17:58 UTC
Okay of course I could also be talking about a page, not an HTML customization. 

But with HTML customizations we can define the regions which are available. In the Pages system there isn't that option.

If we added the option to define available "regions" for a page, how would we prevent the user from creating more than one page for the same "region" ?
Comment 3 Caroline Cyr La Rose 2023-09-22 18:53:45 UTC
Is there a reason to limit the number of restricted pages? Right now we have one, but could it be possible to have more?
Comment 4 Owen Leonard 2023-09-25 13:55:22 UTC
We would have to build some kind of flag into the additional_contents system to allow it, but I don't see why not. In fact such a setting could be used to show or hide any kind of content, html_customization, news, or page.