[Andrew] Moderator Panel 2.0.9

[Kirby]

The options

andrewModeratorPanelDashboardFirstPosition
andrewModeratorPanelDashboardSecondPosition
andrewModeratorPanelDashboardThirdPosition
andrewModeratorPanelDashboardFourthPosition
ndrewModeratorPanelDashboardFifthPosition
andrewModeratorPanelDashboardSixthPosition
andrewModeratorPanelChartOneStatOne
andrewModeratorPanelChartOneStatTwo
andrewModeratorPanelChartTwoStatOne
andrewModeratorPanelChartTwoStatTwo

use hardcoded text for the choices.

Could this be changed to use phrases so they can be translated?

 

[Alpha1]

I tried to force ignore a banned member, because its the condition to allow the banned member back. I got this error:
Oops! We ran into some problems.
You are already ignoring this member.
What does this mean? Is it not possible to force ignore two members if one or both of them are already ignoring? Or if one of them is banned?

Wow! This is a great addon @AndrewSimm

 

[Phaedrus]

I tried to force ignore a banned member, because its the condition to allow the banned member back. I got this error:
Oops! We ran into some problems.
You are already ignoring this member.
What does this mean? Is it not possible to force ignore two members if one or both of them are already ignoring? Or if one of them is banned?

Wow! This is a great addon @AndrewSimm

You would need to remove the member from his ignored user list and then add it back on using the forced ignore feature. Basically, the user already had them on the ignore list, but this would make it so they would have it there and could not remove it.

I would also modify the board so that the "read this post" link is gone for users on ignore otherwise ignore is not effective.

 

[Mendalla]

I keep getting runs of server log errors from this add-on and a couple others. Thought I would start with this one since the others are ones I don't mind keeping disabled for now. Any thoughts on what this might be? I am on the latest build. I have disabled and re-enabled a couple times, which confirmed this is the cause. They go away with it disabled. I don't think the mods are really using it much right now so that weirds me out a little, too.

Error:

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

Generated by: Unknown account Dec 26, 2025 at 6:33 PM

Stack Trace:

[internal function]: XF\Template\Templater->handleTemplateError(512, '[E_USER_WARNING...', '/home/wonderca/...', 1277)
#1 src/XF/Template/Templater.php(1277): trigger_error('Method canViewM...', 512)
#2 internal_data/code_cache/templates/l1/s7/public/andrew_moderatorpanel_macros.php(269): XF\Template\Templater->method(Object(XF\Entity\User), 'canViewModerato...', Array)
#3 src/XF/Template/Templater.php(921): XF\Template\Templater->{closure}(Object(XF\Template\Templater), Array, NULL)
#4 internal_data/code_cache/templates/l1/s7/public/PAGE_CONTAINER.php(1672): XF\Template\Templater->callMacro('andrew_moderato...', 'andrew_moderato...', Array, Array)
#5 src/XF/Template/Templater.php(1799): XF\Template\Templater->{closure}(Object(XF\Template\Templater), Array, NULL)
#6 src/XF/Pub/App.php(612): XF\Template\Templater->renderTemplate('PAGE_CONTAINER', Array)
#7 src/XF/App.php(2571): XF\Pub\App->renderPageHtml('












...', Array, Object(XF\Mvc\Reply\View), Object(XF\Mvc\Renderer\Html))
#8 src/XF/Mvc/Dispatcher.php(414): XF\App->renderPage('









[internal function]: XF\Template\Templater->handleTemplateError(512, '[E_USER_WARNING...', '/home/wonderca/...', 1277)
#1 src/XF/Template/Templater.php(1277): trigger_error('Method canViewM...', 512)
#2 internal_data/code_cache/templates/l1/s7/public/andrew_moderatorpanel_macros.php(269): XF\Template\Templater->method(Object(XF\Entity\User), 'canViewModerato...', Array)
#3 src/XF/Template/Templater.php(921): XF\Template\Templater->{closure}(Object(XF\Template\Templater), Array, NULL)
#4 internal_data/code_cache/templates/l1/s7/public/PAGE_CONTAINER.php(1672): XF\Template\Templater->callMacro('andrew_moderato...', 'andrew_moderato...', Array, Array)
#5 src/XF/Template/Templater.php(1799): XF\Template\Templater->{closure}(Object(XF\Template\Templater), Array, NULL)
#6 src/XF/Pub/App.php(612): XF\Template\Templater->renderTemplate('PAGE_CONTAINER', Array)
#7 src/XF/App.php(2571): XF\Pub\App->renderPageHtml('












...', Array, Object(XF\Mvc\Reply\View), Object(XF\Mvc\Renderer\Html))
#8 src/XF/Mvc/Dispatcher.php(414): XF\App->renderPage('












...', Object(XF\Mvc\Reply\View), Object(XF\Mvc\Renderer\Html))
#9 src/XF/Mvc/Dispatcher.php(66): XF\Mvc\Dispatcher->render(Object(XF\Mvc\Reply\View), 'html')
#10 src/XF/App.php(2824): XF\Mvc\Dispatcher->run()
#11 src/XF.php(806): XF\App->run()
#12 index.php(23): XF::runApp('XF\\Pub\\App')
#13 {main}



...', Object(XF\Mvc\Reply\View), Object(XF\Mvc\Renderer\Html))
#9 src/XF/Mvc/Dispatcher.php(66): XF\Mvc\Dispatcher->render(Object(XF\Mvc\Reply\View), 'html')
#10 src/XF/App.php(2824): XF\Mvc\Dispatcher->run()
#11 src/XF.php(806): XF\App->run()
#12 index.php(23): XF::runApp('XF\\Pub\\App')
#13 {main}

Request State:

array(4) {
["url"] => string(40) "/threads/christmas-memories.10115/page-3"
["referrer"] => bool(false)
["_GET"] => array(0) {
}
["_POST"] => array(0) {
}
}

 

[Alpha1]

Its quite useful to see the flags on avatars and IP lists. But it only shows for newly posted content.
Is it possible to rebuild it so it also shows on older posts? We have a few million posts. Would this incur costs or reach limits somehow?

 

[Phaedrus]

I keep getting runs of server log errors from this add-on and a couple others. Thought I would start with this one since the others are ones I don't mind keeping disabled for now. Any thoughts on what this might be? I am on the latest build. I have disabled and re-enabled a couple times, which confirmed this is the cause. They go away with it disabled. I don't think the mods are really using it much right now so that weirds me out a little, too.

Error:


Stack Trace:

Request State:

I get that same error...

 

[dutchbb]

Error when going to the 'thread reply ban' page.

ErrorException: Template error: [E_USER_WARNING] Cannot call method canReplyBan on a non-object (NULL) src/XF/Template/Templater.php:1282

Stack trace
#0 [internal function]: XF\Template\Templater->handleTemplateError(512, '[E_USER_WARNING...', '/home/...', 1282)
#1 src/XF/Template/Templater.php(1282): trigger_error('Cannot call met...', 512)
#2 internal_data/code_cache/templates/l17/s100/public/andrew_moderatorpanel_macros.php(540): XF\Template\Templater->method(NULL, 'canReplyBan', Array)
#3 src/XF/Template/Templater.php(930): XF\Template\Templater->{closure:internal_data/code_cache/templates/l17/s100/public/andrew_moderatorpanel_macros.php:496}(Object(SV\StandardLib\XF\Template\Templater), Array, NULL)
#4 internal_data/code_cache/templates/l17/s100/public/andrew_moderatorpanel_threadbanlist_view.php(39): XF\Template\Templater->callMacro('andrew_moderato...', 'andrew_moderato...', Array, Array)
#5 src/XF/Template/Templater.php(1815): XF\Template\Templater->{closure:internal_data/code_cache/templates/l17/s100/public/andrew_moderatorpanel_threadbanlist_view.php:4}(Object(SV\StandardLib\XF\Template\Templater), Array, NULL)
#6 src/XF/Template/Template.php(24): XF\Template\Templater->renderTemplate('andrew_moderato...', Array)
#7 src/XF/Mvc/Renderer/Html.php(50): XF\Template\Template->render()
#8 src/XF/Mvc/Dispatcher.php(471): XF\Mvc\Renderer\Html->renderView('Andrew\\Moderato...', 'public:andrew_m...', Array)
#9 src/XF/Mvc/Dispatcher.php(453): XF\Mvc\Dispatcher->renderView(Object(XF\Mvc\Renderer\Html), Object(XF\Mvc\Reply\View))
#10 src/XF/Mvc/Dispatcher.php(412): XF\Mvc\Dispatcher->renderReply(Object(XF\Mvc\Renderer\Html), Object(XF\Mvc\Reply\View))
#11 src/XF/Mvc/Dispatcher.php(66): XF\Mvc\Dispatcher->render(Object(XF\Mvc\Reply\View), 'html')
#12 src/XF/App.php(2824): XF\Mvc\Dispatcher->run()
#13 src/XF.php(814): XF\App->run()
#14 index.php(23): XF::runApp('XF\\Pub\\App')
#15 {main}

Request state
array(4) {
  ["url"] => string(34) "/moderatorpanel/thread-reply-bans/"
  ["referrer"] => string(45) "/moderatorpanel/"
  ["_GET"] => array(0) {

}
["_POST"] => array(0) {
}
}
[/code]

 

[El Porcharo]

Just got the File health check notice pointing to the Setup.php file.



So I've opened it with the text editor and I realized that the file is empty. Not a single character in it.

Is it supposed to be like that?

 

[hkymre]

Just got the File health check notice pointing to the Setup.php file.

View attachment 338978

So I've opened it with the text editor and I realized that the file is empty. Not a single character in it.

Is it supposed to be like that?

I had the same issue last week.

It was due to Immunify detecting it was a dodgy file. My host (Krystal) whitelisted the path to fix it

 

[dutchbb]

I did a scan with Immunify a few weeks back but the file was not detected.

 

[Rhody]

I had the same happen with the setup for both of my forums 2 days ago, and a month earlier too.

I temporarily removed the moderator panel for now, until whatever is triggering it is resolved.

 

[Enes3078]

@AndrewSimm maybe you can fix that thing and add some new improvements for us huh?

 

[dutchbb]

I did a scan with Immunify a few weeks back but the file was not detected.

I did a new scan and now it was detected as a threat.

 

[modified]

Having the same issue with the alert for setup.php

 

[Rhody]

The virus scanner made it empty. The real file is not empty

 

[El Porcharo]

The virus scanner made it empty. The real file is not empty

I know, that's why I posted

I wanted to look into the original file in the addon ZIP archive just after realizing mine was empty. But I suppose that setup.php is only used for first install and might get gleared afterward, despite is a strange behavior anyway (it's easier to just delete the not needed files).

Let's hope Andrew could clarify this soon!

 

[smallwheels]

I had the same issue last week.

It was due to Immunify detecting it was a dodgy file. My host (Krystal) whitelisted the path to fix it

I did a scan with Immunify a few weeks back but the file was not detected.

I had the same happen with the setup for both of my forums 2 days ago, and a month earlier too.

I temporarily removed the moderator panel for now, until whatever is triggering it is resolved.

I did a new scan and now it was detected as a threat.

@AndrewSimm maybe you can fix that thing and add some new improvements for us huh?

Why should he? There is nothing to fix on his side as it seems. It seems quite clear that this is a false positive, caused by the virus scanner. So you should rather open a case with whoever does provide this "Immunify" thing.

Let's hope Andrew could clarify this soon!

What should he clarify and why? The add on has not been updated in ages and worked and works flawlessly. A "virus scanner" suddenly considers it dangerous (which it did not do only a couple of weeks ago with the same file). So obviously it seems rather an issue with this virus scanner. Why would one use one anyway? And why would one complain at Andrew here as the root cause seems clearly not to be caused by him?

 

[El Porcharo]

What should he clarify and why?

Chill down mate... No one's complaining about the add-on, we're just seeking for advice (I would not uninstall it anyway) from the person who developed it.

The add on has not been updated in ages

He might know why, as it might be some parts of the code that has been deprecated or something else.

But anyway, while writing this reply I decided to stop for a moment and submit the code to Claude (I'm not a dev).

And this was the reply:

Looking at the original file, the most likely trigger is the hardcoded HTML string with an external link (ipsearch.io) passed directly into insertBulk() on xf_notice. That pattern — inline HTML with an anchor tag inserted via bulk DB write — is a common false positive trigger for Imunify360's OSSEC/malware scanner rules.

Possible fix: move that notice message to a language phrase instead of hardcoding the HTML string directly in Setup.php. That would likely avoid the signature match entirely.

So, it looks like we need an update here, don't you think?

Of course is not that urgent.
Andrew made this huge add-on and is giving it away for free, despite we all agree that it should be a paid add-on!

 

[smallwheels]

So, it looks like we need an update here, don't you think?

Yes, obviously with the "virus scanner", to stop throwing false positives. If it is not able to detect correctly but breaking harmless code it is not only useless but harmful. If we force developers to follow what some AI demands to avoid the misbehavior that another tool (that is intended to help, not to destroy) has something seems deeply wrong.

 

[El Porcharo]

force developers to follow what some AI demands to avoid the misbehavior that another tool

That's not what I wrote.

I said that, since I'm not a developer but curious to go a bit deeper, I've asked Claude to check the file, and it gave me an answer. You might agree or not, but that's it.

So from the dev's point of view could be a completely different approach, and I'm sure Andrew will know what (and IF) to do about.