[Bug 23650] New: Multiple opac-restrictedpage.pl pages
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23650 Bug ID: 23650 Summary: Multiple opac-restrictedpage.pl pages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard@myacpl.org Reporter: cbrannon@cdalibrary.org QA Contact: testopia@bugs.koha-community.org Would like there to be the option to create multiple opac-restrictedpage.pl pages so that depending on patron or library, this information could be custom. Would need: * A way to identify and code for each page * A way to specify which patron types or branches could access each page. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23650 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Patch complexity|--- |Trivial patch Status|NEW |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23650 --- Comment #1 from Nick Clemens <nick@bywatersolutions.com> --- Created attachment 93010 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=93010&action=edit Bug 23650 - Add address of restricted page to syspref description To test: 1 - Look at the restricted page syspref 2 - Check that the url is listed 3 - Add some content to the page 4 - Save the prefs 5 - Verify the address listed takes you to the page on the opac -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23650 Nick Clemens <nick@bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nick@bywatersolutions.com Attachment #93010|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23650 John Andrews <jandrews@washoecounty.us> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jandrews@washoecounty.us --- Comment #2 from John Andrews <jandrews@washoecounty.us> --- This would be incredibly helpful for libraries (like ours) who have users that can access some electronic resources but not all. Aside from branch ID or patron type (which would likely satisfy our needs), ZIP code could be useful for some libraries as a tool to differentiate patrons. -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23650 Christopher Brannon <cbrannon@cdalibrary.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |In Discussion -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23650 Owen Leonard <oleonard@myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|In Discussion |ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23650 Owen Leonard <oleonard@myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEW -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23650 Owen Leonard <oleonard@myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|oleonard@myacpl.org |koha-bugs@lists.koha-commun | |ity.org -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23650 Patrick Robitaille <patrick.robitaille@collecto.ca> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |patrick.robitaille@collecto | |.ca -- You are receiving this mail because: You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23650 --- Comment #3 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- Maybe instead of building this on top of the restrictedpage setting, the new Pages could be used here. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23650 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Multiple |Restrict access to pages by |opac-restrictedpage.pl |home library or patron |pages |category -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23650 Caroline Cyr La Rose <caroline.cyr-la-rose@inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |caroline.cyr-la-rose@inlibr | |o.com --- Comment #4 from Caroline Cyr La Rose <caroline.cyr-la-rose@inlibro.com> --- I was discussing something similar with Owen on IRC today. We were talking about the opac-restrictedpage page, how this is one page that is only accessible to logged in users. I thought it would be interesting to move this functionality to the pages and add an "logged in users only" flag for OPAC pages. This way we could have more than one restricted page. We could add a limit by patron category, as asked in this bug. Here are some thoughts off the top of my head... - Find away to move the current content of the restricted page to an entry in the additional_contents table (move RestrictedPageContent to to additional_contents.content and RestrictedPageTitle to additional_contents.title) - How do we change the link that users would have added to an html customisation to point to the opac-restrictedpage page? - Getting patron category or home library necessitates that the user be logged in (unless there is something in apache or something like that I guess?) - We could add a check box "logged in patrons only" to OPAC pages - If checked, it could open to a multi-select of patron categories where only the selected categories would be able to access this page. - There is already a library limit per page, but it would be nice that this be multi-select to prevent having to create and maintain a page per library - I don't think we'd need to specify RestrictedPageLocalIPs per page, I think this could stay in the system preferences What else? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23650 Caroline Cyr La Rose <caroline.cyr-la-rose@inlibro.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.koha-community | |.org/bugzilla3/show_bug.cgi | |?id=34892 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23650 David Cook <dcook@prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook@prosentient.com.au -- You are receiving this mail because: You are watching all bug changes.
participants (1)
-
bugzilla-daemon@bugs.koha-community.org