<xen:if hascontent="true">
<div class="avatarList">
<ul>
<xen:contentcheck>
<xen:foreach loop="$threads" value="$thread">
<xen:include template="wf_widget_threads_thread_sidebar">
<xen:set var="$_threadLink">{xen:if '{$visitor.user_id} > 0', {xen:link threads/unread, $thread}, {xen:link posts, {xen:array 'post_id={$thread.last_post_id}'}}}</xen:set>
<xen:set var="$_secondRow">
{xen:phrase wf_x_posted, 'user=<a href="{xen:link 'members', $thread}" class="username">{$thread.username}</a>'} <xen:datetime time="{$thread.last_post_date}" />
</xen:set>
</xen:include>
</xen:foreach>
</xen:contentcheck>
</ul>
</div>
<xen:include template="preview_tooltip" />
</xen:if>
.sidebar .AVForums_TrendingTopics_Widget_TrendingTopics .avatarList .username {
display: inline;
font-size: inherit;
margin: 0;
}
Fixes a bug with user permissions in both the widget and on the trending topics page.
I'll look into this when I get back on Monday.Is there any sort of workaround for this?
I'm not entirely sure what you're showing me..
Looks like the same thread was posted in two forums.
This is resolved. It was because of the thread being moved and leaving a redirect in the original node.Weird - if you hover over them they have different id numbers but if you follow the links you end up in the same thread. The second link is wrong but I'm not sure why. I do believe the thread was moved from one forum to another, but that shouldn't cause a problem, should it?
What's New?
- A bug fix involving thread redirects causing duplicate content in the widget and on the trending topics page.
What's New:
- Ability to show threads based on last post date instead of thread start date (both for the full page and for widgets)
- Fixes the title for the trending topics page
I am wondering whether this is working correctly or not now... I have my settings to thread date, yet they order on last post, and even all over the place at times. I have my minimum reply count at 20 and views 250, yet you can see trending topics with 17 replies or less, and less views now. It worked great until I updated recently...
We use essential cookies to make this site work, and optional cookies to enhance your experience.