Bug 19969 - Adding a manual restriction in memberentrypl with a date does not restrict the patron
Summary: Adding a manual restriction in memberentrypl with a date does not restrict th...
Status: RESOLVED MOVED
Alias: None
Product: Koha
Classification: Unclassified
Component: Patrons (show other bugs)
Version: 17.05
Hardware: All All
: P5 - low enhancement
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-12 20:50 UTC by Kelly McElligott
Modified: 2018-01-18 05:55 UTC (History)
2 users (show)

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: ---
Comma delimited list of Sponsors:
Crowdfunding goal: 0
Crowdfunding committed: 0
Crowdfunding contact:
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 Kelly McElligott 2018-01-12 20:50:31 UTC
When entering a patron manual restriction with a specific date in the memberentry.pl page- the restriction is not carried over into the checkout page and patron is not restricted.  Entering a manual restriction on the memberentry.pl page without a date will carry over the restriction and not allow patron to checkout. 

This is seen in Koha Version 17.05.07.
Comment 1 Katrin Fischer 2018-01-13 08:31:41 UTC
Hi Kelly, I just tested on master and it seems to work ok. Which date did you try?
Comment 2 Kelly McElligott 2018-01-16 17:25:13 UTC
Katrin,
I tried Jan 26th, but now am trying it on another site and not finding that I can replicate it.  Let me dig further into this.  

Kelly
Comment 3 Katrin Fischer 2018-01-16 18:11:15 UTC
If you accidentally picked a date in the past that could explain - but not sure if that's possible.
Comment 4 Kelly McElligott 2018-01-17 21:53:13 UTC
Katrin,
Kyle found that this was a separate issue and also created a bug: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20008

Can I delete or clear this bug?  Or do you need to?
Comment 5 Katrin Fischer 2018-01-18 05:55:25 UTC
Hi Kelly, you can change it to either RESOLVED INVALID or RESOLVED WORKSFORME usually, I think MOVED works ok here too. Changing it, but anyone can do.