##// END OF EJS Templates
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.

File last commit:

r1282:90601d74 default
r1673:e3526633 default
Show More
settings.mako
52 lines | 1.1 KiB | application/x-mako | MakoHtmlLexer
## -*- coding: utf-8 -*-
<%inherit file="/base/base.mako"/>
<%def name="title()">
${_('Settings administration')}
%if c.rhodecode_name:
&middot; ${h.branding(c.rhodecode_name)}
%endif
</%def>
<%def name="breadcrumbs_links()">
${h.link_to(_('Admin'),h.url('admin_home'))}
&raquo;
${_('Settings')}
</%def>
<%def name="menu_bar_nav()">
${self.menu_items(active='admin')}
</%def>
<%def name="side_bar_nav()">
% for navitem in c.navlist:
<li class="${'active' if c.active==navitem.key else ''}">
<a href="${navitem.url}">${navitem.name}</a>
</li>
% endfor
</%def>
<%def name="main_content()">
<%include file="/admin/settings/settings_${c.active}.mako"/>
</%def>
<%def name="main()">
<div class="box">
<div class="title">
${self.breadcrumbs()}
</div>
##main
<div class='sidebar-col-wrapper'>
<div class="sidebar">
<ul class="nav nav-pills nav-stacked">
${self.side_bar_nav()}
</ul>
</div>
<div class="main-content-full-width">
${self.main_content()}
</div>
</div>
</div>
</%def>