V
vVv
Guest
Hmm...
Yes!! Love it!
Hmm...
I had this but was due to APC caching the old files, and not the new ones. Just cleared the cache and updated perfectly.Error
Please enter a valid callback method.
When attempting to upgrade to 1.1
- Watchers icon now floated to the right (consistent with other thread alerts).
- Watchers list now has "noindex" so will not be indexed by search bots.
- Text based link no longer placed into position using javascript
- Watchers alert now above the Thread Tools.
Chris Deeming updated Thread Watchers with a new update entry:
Tweaks and fixes
Read the rest of this update entry...
No.You added an alert? Like it tells you who watches your thread?
Maybe there's no one watching the thread? I doubt it's a conflict as I have both those add-ons installed (you can probably see that in some of the screenshots) and it works fine.Wonderful idea. I just added this. However, it's not showing up as either a bar or text. I thought it might need to be a new thread but no luck there either.
The "add a poll" is there so wonder if there might be some kind of conflict.
Chris Deeming updated Thread Watchers with a new update entry:
Tweaks and fixes
Read the rest of this update entry...
Very nice update Chris, upgraded and it worked nicely. Thank you very muchChris Deeming updated Thread Watchers with a new update entry:
Tweaks and fixes
Read the rest of this update entry...
Considering that by default people automatically watch threads when replying I'm not sure it's a good idea to annoy people with a buck load of pointless alerts.You added an alert? Like it tells you who watches your thread?
I had this but was due to APC caching the old files, and not the new ones. Just cleared the cache and updated perfectly.
What a great add-on, Chris! Is is possible to implement some sort of permission control for this feature? I rather not show this information to non-members.
I often use TMS to create some sort of permission control. That wouldn't really be a problem for me. But it always great to get features into the core code.You could likely wrap it in some conditionals. I wouldn't know for certain what to use though, I have seen the code posted around the forums tons of times though.
Because it is a basic conditional, I'd be inclined not to introduce any sort of permission control for it.I often use TMS to create some sort of permission control. That wouldn't really be a problem for me. But it always great to get features into the core code.
<xen:require css="thread_view_watchers.css" />
<xen:if is="{$watchers} AND {$visitor.user_id}">
<xen:if is="!{$xenOptions.threadWatchersTextOnly}">
<dl class="threadAlerts secondaryContent">
<span class="alertIcon"></span>
<dt>{xen:phrase threadwatchers_watchers}:</dt>
<xen:if is="{xen:number $watchers} > 1">
<dd>{xen:phrase threadwatchers_this_thread_has_x_watchers, 'count={xen:number $watchers}', 'link={xen:link threads/watchers, $thread}'}.</dd>
<xen:else />
<dd>{xen:phrase threadwatchers_this_thread_has_x_watcher, 'count={xen:number $watchers}', 'link={xen:link threads/watchers, $thread}'}.</dd>
</xen:if>
</dl>
</xen:if>
</xen:if>
<xen:if is="{$watchers} AND {$visitor.user_id}">
<xen:if is="{$xenOptions.threadWatchersTextOnly}">
<a href="{xen:link threads/watchers, $thread}" class="OverlayTrigger">{xen:phrase threadwatchers_watchers}: {xen:number $watchers}</a>
</xen:if>
</xen:if>
We use essential cookies to make this site work, and optional cookies to enhance your experience.