Bug 14261 - Switch 'ask for a discharge' to 'download discharge confirmation' when patron was discharge in OPAC user account
Summary: Switch 'ask for a discharge' to 'download discharge confirmation' when patron...
Status: Patch doesn't apply
Alias: None
Product: Koha
Classification: Unclassified
Component: OPAC (show other bugs)
Version: Main
Hardware: All All
: P5 - low trivial
Assignee: Katrin Fischer
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-24 00:05 UTC by Indranil Das Gupta
Modified: 2023-05-18 10:59 UTC (History)
1 user (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
Bug 14262: [DOES NOT WORK] Change discharge tab heading in OPAC depending on if patron was discharged (2.25 KB, patch)
2020-04-18 10:38 UTC, Katrin Fischer
Details | Diff | Splinter Review
Bug 14261: [DOES NOT WORK] Change discharge tab heading in OPAC depending on if patron was discharged (2.25 KB, patch)
2020-04-18 12:14 UTC, Katrin Fischer
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Indranil Das Gupta 2015-05-24 00:05:53 UTC
A few issues have cropped up on the OPAC side after bug 8007 was pushed into master.

1/ a 'discharged' user on login into OPAC account sees the following in the summary - "Please note: Your account has been frozen. Usually the reason for freezing an account is old overdues or damage fees. If your account page shows your account to be clear, please contact the library."

It should clearly mention that user was 'discharged', the above message is confusing and ambiguous for in this case.

2/ A discharged user is still able to submit 'purchase suggestions' - this should be disallowed or at least introduction of a configurable syspref - DischargedPatronSuggestion to "do not allow" by default

3/ "ask for a discharge" should preferably read "download discharge certificate" or something like that.
Comment 1 Owen Leonard 2016-05-31 15:00:01 UTC
(In reply to Indranil Das Gupta from comment #0)
> It should clearly mention that user was 'discharged', the above message is
> confusing and ambiguous for in this case.

Having not seen this bug report, I submitted the above as a separate bug: Bug 16464.

> 3/ "ask for a discharge" should preferably read "download discharge
> certificate" or something like that.

In order for the link text to change based on whether a discharge was or wasn't requested or approved we would have to pull discharge data on every page in the OPAC where the user menu is displayed.

I think a more efficient solution might be to:

1. Change the text of the link to "discharge requests" or something like that.
2. Fix Bug 16464 so that it is clear from looking at the user's account page that they have an approved discharge available.
Comment 2 Katrin Fischer 2020-04-18 10:34:05 UTC
Hm, as we have the Patron object on the page, I think it should not be too bad to implement something like is_discharged. I'd be happy to try if someone could give me some pointers.
Comment 3 Katrin Fischer 2020-04-18 10:38:42 UTC
Created attachment 103201 [details] [review]
Bug 14262: [DOES NOT WORK] Change discharge tab heading in OPAC depending on if patron was discharged
Comment 4 Katrin Fischer 2020-04-18 10:40:58 UTC
The attached patch does not work - it's probably something very silly I am doing there:

Template process failed: undef error - Can't use string ("Koha::Patron::Discharge") as a HASH ref while "strict refs" in use at /home/vagrant/kohaclone/Koha/Patron/Discharge.pm line 47.
 at /home/vagrant/kohaclone/C4/Templates.pm line 122
Comment 5 Katrin Fischer 2020-04-18 12:14:22 UTC
Created attachment 103203 [details] [review]
Bug 14261: [DOES NOT WORK] Change discharge tab heading in OPAC depending on if patron was discharged
Comment 6 Katrin Fischer 2020-08-14 12:57:09 UTC
Would still love some help with fixing my patch!
Comment 7 Katrin Fischer 2021-06-04 10:25:06 UTC
(In reply to Katrin Fischer from comment #6)
> Would still love some help with fixing my patch!

Still looking for someone to help me out here :)
Comment 8 Pedro Amorim 2023-05-18 10:59:11 UTC
Can you rebase please Katrin and I'll take a look