##// END OF EJS Templates
u » pc » rhodecode-enterprise-ce-fork-pc
RSS

Fork of rhodecode-enterprise-ce

comments: remove helper to render a comment object....
comments: remove helper to render a comment object. - we always use helper renderer, and for consistency we should stick with that. It makes refactoring, and general use much harder. DB objects should have least possible logic inside.
marcink - - Load All Authors

File last commit:

r1:854a839a default
r1673:e3526633 default
Show More
pylons_context.dbtmako
24 lines | 641 B | text/plain | TextLexer
/ rhodecode / utils / templates / pylons_context.dbtmako
History | Annotation | Raw |Copy content |Copy permalink
% if pylons_context:
<table class="table table-striped table-condensed">
<thead>
<th>Key</th>
<th>Value</th>
</thead>
<tbody>
% for key in sorted(pylons_context.keys()):
<tr>
<td>${key}</td>
<td>${repr(pylons_context[key])}</td>
</tr>
% endfor
</tbody>
</table>
% else:
<p>No context information found.</p>
<p>The integrated Pylons application has to be abjusted to make the context object available.
It should check for <code>environ['debugtoolbar.wants_pylons_context'] == True</code> and set
<code>environ['debugtoolbar.pylons_context'] = tmpl_context._current_obj()</code>.</p>
% endif