From bugzilla-daemon@bugs.koha-community.org Tue Mar 22 13:31:54 2022 From: bugzilla-daemon@bugs.koha-community.org To: koha-bugs@lists.koha-community.org Subject: [Koha-bugs] [Bug 30330] New: Bad fields within comments in a HTML notice still cause a crash Date: Tue, 22 Mar 2022 12:31:54 +0000 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7439166002146261846==" --===============7439166002146261846== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30330 Bug ID: 30330 Summary: Bad fields within comments in a HTML notice still cause a crash Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Notices Assignee: koha-bugs@lists.koha-community.org Reporter: m.de.rooy@rijksmuseum.nl QA Contact: testopia@bugs.koha-community.org I had something like this in a notice: The table is linked to a valid Koha object. The field is wrong. Running Print slip from within circ/article-requests caused a crash like: ERROR PROCESSING TEMPLATE: undef error - The method Koha::<>-><> is not covered by tests! While this is within a comment, I did not hope to see that. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. --===============7439166002146261846==-- From bugzilla-daemon@bugs.koha-community.org Tue Mar 22 13:32:38 2022 From: bugzilla-daemon@bugs.koha-community.org To: koha-bugs@lists.koha-community.org Subject: [Koha-bugs] [Bug 30330] Bad fields within comments in a HTML notice still cause a crash Date: Tue, 22 Mar 2022 12:32:37 +0000 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0220228606649300448==" --===============0220228606649300448== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30330 --- Comment #1 from Marcel de Rooy --- (In reply to Marcel de Rooy from comment #0) > Running Print slip from within circ/article-requests caused a crash like: Yes it was article_requests.toc_request :) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. --===============0220228606649300448==-- From bugzilla-daemon@bugs.koha-community.org Tue Mar 22 13:33:40 2022 From: bugzilla-daemon@bugs.koha-community.org To: koha-bugs@lists.koha-community.org Subject: [Koha-bugs] [Bug 30330] Bad fields within comments in a HTML notice still cause a crash Date: Tue, 22 Mar 2022 12:33:36 +0000 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3621141774857965814==" --===============3621141774857965814== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30330 --- Comment #2 from Marcel de Rooy --- (In reply to Marcel de Rooy from comment #1) > (In reply to Marcel de Rooy from comment #0) > > Running Print slip from within circ/article-requests caused a crash like: > > Yes it was article_requests.toc_request :) And not present in that database. But it just serves as an example that fields within comments are evaluated. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. --===============3621141774857965814==-- From bugzilla-daemon@bugs.koha-community.org Tue Mar 22 14:48:41 2022 From: bugzilla-daemon@bugs.koha-community.org To: koha-bugs@lists.koha-community.org Subject: [Koha-bugs] [Bug 30330] Bad fields within comments in a HTML notice still cause a crash Date: Tue, 22 Mar 2022 13:48:40 +0000 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6581671265790514815==" --===============6581671265790514815== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30330 --- Comment #3 from Marcel de Rooy --- As a side note (lowering the severity a bit): You could also try [%# bad stuff %], this works at least partially as long as the bad stuff does not contain %] which would end the comment. And for fun, as a crazy workaround, you could replace an ending %] by %][%# resulting in for instance: [%#

TOC: [% IF article_request.toc_request %][%#Include TOC[% ELSE %][%#No[% END %] It works, but serves as a 'good' example of a bad workaround. Should we call this a Template Toolkit bug or what? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. --===============6581671265790514815==-- From bugzilla-daemon@bugs.koha-community.org Sat Jun 17 21:03:34 2023 From: bugzilla-daemon@bugs.koha-community.org To: koha-bugs@lists.koha-community.org Subject: [Koha-bugs] [Bug 30330] Bad fields within comments in a HTML notice still cause a crash Date: Sat, 17 Jun 2023 19:03:33 +0000 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============2566803382818700718==" --===============2566803382818700718== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30330 Katrin Fischer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #4 from Katrin Fischer --- I think if you use HTML comments, it will still get parsed by TT and that is intentional. It allows you to put things into the templates that are only visible in source, like maybe our TEMPLATE FILE comment in the OPAC. You would have to use a TT comment if you didn't want it to show up in the code/being parsed at all. I believe this is not a bug, but working as intended. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. --===============2566803382818700718==--