https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13895
--- Comment #46 from Lari Taskula <[email protected]> --- (In reply to Lari Taskula from comment #45) > (In reply to Katrin Fischer from comment #43) > > > > We also need to resolve the question of taking opacuserlogin into > > > > account. > > > Yes I think this should be discussed, for example, could it make sense for > > > somebody to disable opacuserlogin but still wanting to have API access to > > > own objects? Or simply control both of these under the same preference, > > > opacuserlogin? > > > > I can imagine both happening: > > - libraries wanting to shut down any OPAC account functionality, but still > > be able to renew in staff, so the circulation conditions are set up this > > way. In this case, there should be a way to lock the API (opacuserlogin > > might be a way) > > - libraries shutting down the OPAC, because they use something else like an > > external discovery layer. In this case they'd still want to use the API, but > > might turn off the OPAC as far as possible. > > > > Should we just make a separate switch? > Yeah, I think it will be useful. I will open a new bug for it. I opened Bug 17424 for discussing this & added an example patch. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://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/
