Bug 31612 - koha-z3950-responder breaks if it's run in a Koha that was created before bug 28364 was applied
Summary: koha-z3950-responder breaks if it's run in a Koha that was created before bug...
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Z39.50 / SRU / OpenSearch Servers (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on: 28364
Blocks:
  Show dependency tree / graph
 
Reported: 2022-09-23 02:29 UTC by David Cook
Modified: 2023-01-25 00:01 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
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Cook 2022-09-23 02:29:43 UTC 
The problem is the same as Bug 28364 but that it affects upgraded Koha instances rather than new Koha instances.
Comment 1 Martin Renvoize (ashimema) 2022-10-05 11:10:36 UTC 
We find lots of issues with permissions at upgrades.. mostly for 'standard' type installs though.
Comment 2 David Cook 2022-10-09 22:59:18 UTC 
(In reply to Martin Renvoize from comment #1)
> We find lots of issues with permissions at upgrades.. mostly for 'standard'
> type installs though.

I think that's probably a separate issue although an interesting one.
Comment 3 Katrin Fischer 2022-11-14 21:53:10 UTC 
Is there something we can do about this one, at least documentation wise/info for sysadmins?
Comment 4 David Cook 2022-11-14 22:24:07 UTC 
(In reply to Katrin Fischer from comment #3)
> Is there something we can do about this one, at least documentation
> wise/info for sysadmins?

I think this is one of those ones that is easy to fix once you know about it, so it's tough to devote resources to a more robust automated fix...

Not sure what documentation we'd update for this one?
Comment 5 Katrin Fischer 2022-11-14 22:30:01 UTC 
(In reply to David Cook from comment #4)
> (In reply to Katrin Fischer from comment #3)
> > Is there something we can do about this one, at least documentation
> > wise/info for sysadmins?
> 
> I think this is one of those ones that is easy to fix once you know about
> it, so it's tough to devote resources to a more robust automated fix...
> 
> Not sure what documentation we'd update for this one?

We could have updated the release notes note on bug 28346 - but it might be a little late for that one :)

Maybe a note here and then close this?
https://wiki.koha-community.org/wiki/Setting_up_the_Z39.50_and_SRU_Server
Comment 6 David Cook 2022-11-14 22:33:35 UTC 
(In reply to Katrin Fischer from comment #5)
> We could have updated the release notes note on bug 28346 - but it might be
> a little late for that one :)
> 
> Maybe a note here and then close this?
> https://wiki.koha-community.org/wiki/Setting_up_the_Z39.50_and_SRU_Server

I like the idea of adding a note there.

Although I don't think we need to close this one. I still like the idea of an audit script to check for problematic permissions and stuff like that... (although I have no idea when I'd ever do it...)
Comment 8 Katrin Fischer 2022-11-14 22:41:13 UTC 
(In reply to David Cook from comment #7)
> https://wiki.koha-community.org/wiki/Setting_up_the_Z39.
> 50_and_SRU_Server#Troubleshooting

Awesome, thx!
Comment 9 David Cook 2023-01-25 00:01:12 UTC 
Ha! Got bitten by this again. Fortunately, I remembered this bug report...