##// END OF EJS Templates
Switched order of actions when doing repo rescan....
Switched order of actions when doing repo rescan. doing invalidation after repository scan is not optimal. In case of big repository we first create an instance then invalidate cache that we don't actually need. Reversing this order prevents that

File last commit:

r3198:c20adbaf beta
r3953:fc63a1d9 beta
Show More
admin_log.html
64 lines | 1.8 KiB | text/html | HtmlLexer
## -*- coding: utf-8 -*-
%if c.users_log:
<table>
<tr>
<th class="left">${_('Username')}</th>
<th class="left">${_('Action')}</th>
<th class="left">${_('Repository')}</th>
<th class="left">${_('Date')}</th>
<th class="left">${_('From IP')}</th>
</tr>
%for cnt,l in enumerate(c.users_log):
<tr class="parity${cnt%2}">
<td>
%if l.user is not None:
${h.link_to(l.user.username,h.url('edit_user', id=l.user.user_id))}
%else:
${l.username}
%endif
</td>
<td>${h.action_parser(l)[0]()}
<div class="journal_action_params">
${h.literal(h.action_parser(l)[1]())}
</div>
</td>
<td>
%if l.repository is not None:
${h.link_to(l.repository.repo_name,h.url('summary_home',repo_name=l.repository.repo_name))}
%else:
${l.repository_name}
%endif
</td>
<td>${h.fmt_date(l.action_date)}</td>
<td>${l.user_ip}</td>
</tr>
%endfor
</table>
<script type="text/javascript">
YUE.onDOMReady(function(){
YUE.delegate("user_log","click",function(e, matchedEl, container){
ypjax(e.target.href,"user_log",function(){
show_more_event();
tooltip_activate();
show_changeset_tooltip();
});
YUE.preventDefault(e);
},'.pager_link');
YUE.delegate("user_log","click",function(e,matchedEl,container){
var el = e.target;
YUD.setStyle(YUD.get(el.id.substring(1)),'display','');
YUD.setStyle(el.parentNode,'display','none');
},'.show_more');
});
</script>
<div class="pagination-wh pagination-left">
${c.users_log.pager('$link_previous ~2~ $link_next')}
</div>
%else:
${_('No actions yet')}
%endif