| Summary: | Account expiration should not be displayed when login counts as activity and membership_expiry is configured to renew card | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Lari Taskula <lari.taskula> |
| Component: | OPAC | Assignee: | Owen Leonard <oleonard> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
Lari Taskula
2026-01-20 09:17:14 UTC
The question is how can we know, in the TT templates, if -renew is used in the membership_expiry.pl cronjob? (In reply to Lari Taskula from comment #1) > The question is how can we know, in the TT templates, if -renew is used in > the membership_expiry.pl cronjob? Correction, -renew -active n One option would be to renew the expiring patron account simply as they login. But this would require another system preference. |