| Summary: | Convert RestrictedPageContent system preference to HTML customization | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Owen Leonard <oleonard> |
| Component: | OPAC | Assignee: | Owen Leonard <oleonard> |
| Status: | In Discussion --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | caroline.cyr-la-rose, testopia |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: |
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23650 https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32957 |
||
| Change sponsored?: | --- | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
| Bug Depends on: | |||
| Bug Blocks: | 26050 | ||
|
Description
Owen Leonard
2023-09-22 16:55:23 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? 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" ? Is there a reason to limit the number of restricted pages? Right now we have one, but could it be possible to have more? 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. |