Who Replied 2.4.0

[Xon]

Xon updated Who Replied with a new update entry:

2.3.0 - Feature update

This add-on is now available on atelieraphelion.com

• Require StandardLib v1.20.0+
• Require php 7.2+
• Add "Allowed "Users per page" choices" option
  • Lets users select from a admin populated list for number of items per page. Default is 25 & 50
• Add "Who replied pagination features" option
  • Standard pagination
  • AJAX...

Read the rest of this update entry...

 

[Anacleto]

This is a beautiful addon that many users asked to us. Can you try to implement a "sort by alphabet"? Actually the only sorting option is by number of messages inside the thread. So we can see users from the first that write more messages to the user that write less messages.
But a sorting option would be very nice and let bring perfection to this addon.

 

[Stuart Wright]

@Xon do you have an ETA for the 2.3 release yet please?
Thanks

 

[HappyWorld]

@Xon do you have an ETA for the 2.3 release yet please?
Thanks

It doesn't work? I haven't upgraded to 2.3 yet.

 

[Xon]

Xon updated Who Replied with a new update entry:

2.4.0 - XenForo 2.3 support

• Require StandardLib v1.21.0+
• XF2.3 support

Read the rest of this update entry...

 

[TrevC2]

This looks great! Any chance the who replied objects could be made available to thread_view template too? (to list avatars of members who participated in the thread).

 

[Anacleto]

Hi and thanks for this grate addon.
I have to nitice that the filter "per name" is working bad since last update.
If you use Who Replied and then use the filter per name, it do not show you in order, but keep you in a strange position, in my case in page 5:



i have 25 user per page to show.
if i put 100 user per page it show less pages but anyway the user do not show up in the first page.

 

[Xon]

This will likely require a StandardLib update to fix, I'm hopeful I'll have time later next week to look into this

 

[Anacleto]

This will likely require a StandardLib update to fix, I'm hopeful I'll have time later next week to look into this

yeah, thanks for support.
we will patiently await any news from you...

 

[Anacleto]

This will likely require a StandardLib update to fix, I'm hopeful I'll have time later next week to look into this

Hi Xon, i think that the update 1.21.11 of the standard lib does not contain the fix to the #87 behaviour, isn't it?

 

[Xon]

Not yet, v1.21.11 was an urgent bugfix to fix XF2.3.5 support.

 

[lazy llama]

Hi and thanks for this grate addon.
I have to nitice that the filter "per name" is working bad since last update.
If you use Who Replied and then use the filter per name, it do not show you in order, but keep you in a strange position, in my case in page 5:

View attachment 317815

i have 25 user per page to show.
if i put 100 user per page it show less pages but anyway the user do not show up in the first page.

I can confirm this too. If a user isn’t on the first page, the filter never finds them, even if you filter on the page where they do appear, the filter goes back to page 1.

 

[Xon]

I've got a fix for this for the next StandardLib version, just working on some other bugfixes to bundle into it

 

[Xon]

Hi and thanks for this grate addon.
I have to nitice that the filter "per name" is working bad since last update.
If you use Who Replied and then use the filter per name, it do not show you in order, but keep you in a strange position, in my case in page 5:

View attachment 317815

i have 25 user per page to show.
if i put 100 user per page it show less pages but anyway the user do not show up in the first page.

I can confirm this too. If a user isn’t on the first page, the filter never finds them, even if you filter on the page where they do appear, the filter goes back to page 1.

Fixed in StandardLib v1.21.12 update

 

[Anacleto]

Fixed in StandardLib v1.21.12 update

yes it Work correctly now, You are the man!

 

[Mendalla]

I had a burst of errors citing "Method canViewWhoReplied" on Tuesday. It is not the first time but is the first time in a while. I'll post full details below. @Xon is this related to this add-on? I have disabled temporarily (doesn't get used much anyhow) to monitor but maybe you can at least confirm if it is the source and any thoughts you have on the cause. I am on Who Replied 2.4.0 (I did a pass on updating all my add-ons around the time you released it) and Xenforo 2.3.6.

-------
Server error log

ErrorException: Template error: [E_USER_WARNING] Method canViewWhoReplied is not callable on the given object (XF\Entity\Thread) src/XF/Template/Templater.php:1277

Generated by: Unknown account Mar 11, 2025 at 3:34 PM

Stack trace

#0 [internal function]: XF\Template\Templater->handleTemplateError(512, '[E_USER_WARNING...', '/home/wonderca/...', 1277)
#1 src/XF/Template/Templater.php(1277): trigger_error('Method canViewW...', 512)
#2 internal_data/code_cache/templates/l1/s7/public/thread_list_macros_whoreplied.php(10): XF\Template\Templater->method(Object(XF\Entity\Thread), 'canViewWhoRepli...', Array)
#3 src/XF/Template/Templater.php(1799): XF\Template\Templater->{closure}(Object(XF\Template\Templater), Array, NULL)
#4 src/XF/Template/Templater.php(1873): XF\Template\Templater->renderTemplate('thread_list_mac...', Array)
#5 internal_data/code_cache/templates/l1/s7/public/thread_list_macros.php(453): XF\Template\Templater->includeTemplate('public:thread_l...', Array)
#6 src/XF/Template/Templater.php(1092): XF\Template\Templater->{closure}(Object(XF\Template\Templater), Array, Object(XF\Template\ExtensionSet))
#7 src/XF/Template/Templater.php(1028): XF\Template\Templater->renderExtensionInternal('meta_cell', Array, Array, Object(XF\Template\ExtensionSet))
#8 internal_data/code_cache/templates/l1/s7/public/thread_list_macros.php(541): XF\Template\Templater->renderExtension('meta_cell', Array, Object(XF\Template\ExtensionSet))
#9 src/XF/Template/Templater.php(921): XF\Template\Templater->{closure}(Object(XF\Template\Templater), Array, Object(XF\Template\ExtensionSet))
#10 internal_data/code_cache/templates/l1/s7/public/whats_new_posts.php(228): XF\Template\Templater->callMacro('thread_list_mac...', 'item', Array, Array)
#11 src/XF/Template/Templater.php(921): XF\Template\Templater->{closure}(Object(XF\Template\Templater), Array, NULL)
#12 internal_data/code_cache/templates/l1/s7/public/whats_new_posts.php(351): XF\Template\Templater->callMacro('whats_new_posts', 'results', Array, Array)
#13 src/XF/Template/Templater.php(1799): XF\Template\Templater->{closure}(Object(XF\Template\Templater), Array, NULL)
#14 src/XF/Template/Template.php(24): XF\Template\Templater->renderTemplate('whats_new_posts', Array)
#15 src/XF/Mvc/Renderer/Html.php(50): XF\Template\Template->render()
#16 src/XF/Mvc/Dispatcher.php(471): XF\Mvc\Renderer\Html->renderView('XF:WhatsNew\\Pos...', 'public:whats_ne...', Array)
#17 src/XF/Mvc/Dispatcher.php(453): XF\Mvc\Dispatcher->renderView(Object(XF\Mvc\Renderer\Html), Object(XF\Mvc\Reply\View))
#18 src/XF/Mvc/Dispatcher.php(412): XF\Mvc\Dispatcher->renderReply(Object(XF\Mvc\Renderer\Html), Object(XF\Mvc\Reply\View))
#19 src/XF/Mvc/Dispatcher.php(66): XF\Mvc\Dispatcher->render(Object(XF\Mvc\Reply\View), 'html')
#20 src/XF/App.php(2826): XF\Mvc\Dispatcher->run()
#21 src/XF.php(806): XF\App->run()
#22 index.php(23): XF::runApp('XF\\Pub\\App')
#23 {main}

Request state

array(4) {
["url"] => string(25) "/whats-new/posts/1320489/"
["referrer"] => string(51) "https://www.wondercafe2.ca/whats-new/posts/1320489/"
["_GET"] => array(0) {
}
["_POST"] => array(0) {
}
}

 

[Xon]

had a burst of errors citing "Method canViewWhoReplied" on Tuesday. It is not the first time but is the first time in a while. I'll post full details below. @Xon is this related to this add-on? I have disabled temporarily (doesn't get used much anyhow) to monitor but maybe you can at least confirm if it is the source and any thoughts you have on the cause. I am on Who Replied 2.4.0 (I did a pass on updating all my add-ons around the time you released it) and Xenforo 2.3.6.

Disabling the add-on will cause a brief period where the template modification still applies but the backing code isn't there which will cause those sorts of errors.