Summary: | Clean up borrower.textmessaging leftover code | ||
---|---|---|---|
Product: | Koha | Reporter: | Ian Walls <koha.sekjal> |
Component: | Patrons | Assignee: | Ian Walls <koha.sekjal> |
Status: | CLOSED FIXED | QA Contact: | Marcel de Rooy <m.de.rooy> |
Severity: | trivial | ||
Priority: | P5 - low | CC: | gmcharlt, jcamins, paul.poulain |
Version: | 3.8 | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: | ||
Attachments: |
Bug 7697: Remove unused textmessaging parameter from OPAC main/user
Bug 7697: Remove unused textmessaging parameter from OPAC main/user |
Description
Ian Walls
2012-03-10 17:02:35 UTC
Created attachment 8147 [details] [review] Bug 7697: Remove unused textmessaging parameter from OPAC main/user Removes the textmessaging parameter from opac/opac-main.pl and opac/opac-user.pl, since it's not utilized anywhere in the templates, and is sourced from a field that no longer exists in the borrower table (textmessaging). This also removes a dependency on C4/Members.pm from opac-main.pl To Test: Login to the OPAC, and view both opac-user.pl and opac-main.pl. Both pages should still render properly. Created attachment 8149 [details] [review] Bug 7697: Remove unused textmessaging parameter from OPAC main/user Removes the textmessaging parameter from opac/opac-main.pl and opac/opac-user.pl, since it's not utilized anywhere in the templates, and is sourced from a field that no longer exists in the borrower table (textmessaging). This also removes a dependency on C4/Members.pm from opac-main.pl To Test: Login to the OPAC, and view both opac-user.pl and opac-main.pl. Both pages should still render properly. Signed-off-by: Jared Camins-Esakov <jcamins@cpbibliography.com> Looks good to me. Marking as Passed QA. Patch pushed I also have checked that opac note & patron message are still here, they are There have been no further reports of problems so I am marking this bug resolved. |