Mercurial > p > roundup > code
view website/issues/html/msg.index.html @ 5095:d3ba0b254dbb
The patch to implement:
Validate properties specified for sorting and grouping in index
views. Original patch from martin.v.loewis via:
https://hg.python.org/tracker/roundup/rev/439bd3060df2
Applied by John Rouillard with some modification to properly
identify if the bad property is a sort or grouping property. Tests
added.
has an issue with the current code base. Apparently sometime it can be
entered without self.classname being defined. As a result the property
lookup fails. So guard it by checking for self.classname in a couple
of spots and if self.classname is not set just append the property
and let the target action sort it out.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Wed, 22 Jun 2016 21:29:14 -0400 |
| parents | c2d0d3e9099d |
| children |
line wrap: on
line source
<tal:block metal:use-macro="templates/page/macros/icing"> <title metal:fill-slot="head_title" i18n:translate="" >List of messages - <span tal:replace="config/TRACKER_NAME" i18n:name="tracker"/></title> <span metal:fill-slot="body_title" tal:omit-tag="python:1" i18n:translate="">Message listing</span> <td class="content" metal:fill-slot="content"> <table tal:define="batch request/batch" class="messages"> <tr><th colspan=3 class="header" i18n:translate="">Messages</th></tr> <tal:block tal:repeat="msg batch"> <tr> <th><a tal:attributes="href string:msg${msg/id}"><tal:x replace="msg/id"/></a></th> <th tal:content="string:Author: ${msg/author}">author</th> <th tal:content="string:Date: ${msg/date}">date</th> </tr> <tr> <td colspan="3"><pre tal:content="msg/content">content</pre></td> </tr> </tal:block> <metal:block use-macro="templates/issue.index/macros/batch-footer" /> </table> </td> </tal:block>
