Bug 39378 - No way to hide and disable "Offline circulation"
Summary: No way to hide and disable "Offline circulation"
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: Main
Hardware: All All
: P5 - low minor
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-03-19 03:47 UTC by David Cook
Modified: 2025-03-20 23:55 UTC (History)
2 users (show)

See Also:
GIT URL:
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 David Cook 2025-03-19 03:47:43 UTC
Currently, there's no way to hide and disable "Offline circulation".

I think we should add a system preference to hide this.
Comment 1 Katrin Fischer 2025-03-19 08:58:05 UTC
Which one do you mean, the link on the circulation page to upload files?
Comment 2 David Cook 2025-03-19 23:41:58 UTC
(In reply to Katrin Fischer from comment #1)
> Which one do you mean, the link on the circulation page to upload files?

More or less, yes. I mean the whole "Offline circulation" section:

"Upload offline circulation file (.koc)" process_koc.pl
"Pending offline circulation actions" list.pl
"Get desktop application" external_link
"Get Firefox add-on" external_link

And then disabling those .pl scripts in the "offline_circ" path.
Comment 3 Katrin Fischer 2025-03-20 11:07:45 UTC
Hm, maybe also a permission would also make sense here (not sure if we have one yet??
Comment 4 David Cook 2025-03-20 23:55:57 UTC
(In reply to Katrin Fischer from comment #3)
> Hm, maybe also a permission would also make sense here (not sure if we have
> one yet??

That's a good idea. Probably the better way to go. I think I have a number of other recent bug reports where I'm going to propose adding permissions I think.

(I need to action a lot of these bug reports locally quite quickly, so I might locally use a system preference, but submit a patch that adds a permission. Although then I won't be able to phase out the syspref without a database change as well. Tricky...)