XF Bot Guard

XF Bot Guard 1.4.1

No permission to download
I was all for this, but hearing some of the code is AI and seeing 14 updates in under a week has made me a little skeptical lol
 
I was all for this, but hearing some of the code is AI and seeing 14 updates in under a week has made me a little skeptical lol

I don’t hide the fact that I code with AI. I’ve worked in tech and software engineering for over 20 years, and my last 5 years have been as Head of Generative AI R&D. I’m an AI power-user.

But don’t mistake that for me blindly accepting whatever AI outputs. I write code myself, correct plenty of it myself, review what goes in, and test the add-on on my own production forum.

So... yeah, I get the concern, though I’d argue active maintenance is a feature, not a warning sign.

Older versions remain available, so if the pace of updates makes anyone uncomfortable, they can simply stay on a version they trust and update when they’re ready.

From my side, I’m going to keep fixing issues, tightening edge cases, and improving the add-on when I see opportunities to do so.
 
Last edited:
alright that makes more sense. Sorry if i was rude

No need to apologise. If 5 years in that specific role taught me anything, its that AI (and maybe more often, the human asking it things) is not so reliable. But the bad rap goes to the AI, whereas IMO it should go to the human. Kind of like hating on a car for someone misusing the car... or something like that.
 
lol yea i just have a stigma against it for some reason,

Well, it can/will replace a lot of software engineers, amongst many other roles... so hey, I totally get it! But it's kind of here now, resisting is like saying no to the automobile and sticking with the horse and carriage.

I don't like it. Probably not many of us do. I even worked in the field and the goal was to automate away the annoying things. Funny how it becomes a prime tool to just remove us from the equation as much as possible.

Anyway, this would be a serious digression from the topic / add-on... so I am going to leave it there... but just know, I totally feel you.
 
zeeb0t updated XF Bot Guard with a new update entry:

Minor Release: v.1.1.5

Minor update to the Members Online feature.

  • Visitors currently being challenged or validated by XF Bot Guard are now kept out of XenForo’s robot classification, keeping the online list and Bot Guard counts better aligned.
  • Trusted or explicitly allowed bot traffic are now marked as robots in XenForo’s online activity where appropriate.

This update was added because XenForo’s robot detection is primarily based on User-Agent values, which can be easily spoofed. XF Bot...

Read the rest of this update entry...
 
@Feline Forums one bit of feedback I took from your comments was that you don’t want to feel like you have to install updates five times in a day, which is completely fair.

That’s on me. I haven’t been clearly separating minor updates from major or important ones.

From now on, I’ll label releases as minor or major so each of you can make a more informed call about when to update. For example, you may choose to hold off on minor updates and only apply major ones more promptly.

When a major update is released, I’ll also explain why I consider it major.

This latest update is minor, so there’s no urgency to install it immediately if you’d rather wait.
 
After updating from 1.1.4 to 1.1.5 my forum ended up spitting out a blank screen, even for logged in visitors. Firefox said "Error 500". ACP access still worked. Rebuilding the add on did not help. Disabling the add on brought things back to normal.

Which version of XenForo are you using?
 
Can you share the stacktrace from the logs in ACP?
Seems to be a compatibility issue with Xon's "user activity" add on

Code:
ErrorException: Fatal Error: Declaration of
SV\UserActivity\XF\Repository\SessionActivity::updateSessionActivity($userId, $ip, $controller, $action, array $params, $viewState, $robotKey)
must be compatible with
Zee\BotGuard\XF\Repository\SessionActivity::updateSessionActivity($userId, $ip, $controller, $action, array $params = [], $viewState = 'valid', $robotKey = '') src/addons/SV/UserActivity/XF/Repository/SessionActivity.php:19
Generated by: llk Jun 4, 2026 at 8:40 AM
Stack trace
#0 [internal function]: XF::handleFatalError()
#1 {main}
 
It manages the identify of robots in XenForo and looks as though that addon is trying to do the same thing.
Not really. It displays who is currently seeing a given thread, not actively managing identities.

Displays user activity below content.
It names logged in users and counts guests.

As this add on has been around since 2017, is made by Xon (clearly one of the top notch devs for XF add ons) and actively maintained (latest release dating from 2026) and has been running flawlessly since I installed it I'd assume whatever you did with 1.1.5 was possibly not the best way how to do it.
 
Not really. It displays who is currently seeing a given thread, not actively managing identities.


It names logged in users and counts guests.

As this add on has been around since 2017, is made by Xon (clearly one of the top notch devs for XF add ons) and actively maintained (latest release dating from 2026) and has been running flawlessly since I installed it I'd assume whatever you did with 1.1.5 was possibly not the best way how to do it.

Yes, it is a bug in my function declaration. I am fixing it right now and will replace the 1.1.5 with the fix. Won't be long... they will play nice together shortly.
 
Not really. It displays who is currently seeing a given thread, not actively managing identities.


It names logged in users and counts guests.

As this add on has been around since 2017, is made by Xon (clearly one of the top notch devs for XF add ons) and actively maintained (latest release dating from 2026) and has been running flawlessly since I installed it I'd assume whatever you did with 1.1.5 was possibly not the best way how to do it.

Here you go! I have also replaced the 1.1.5 package with this one. It corrects the error. It was my bad.

I defined the method as:

PHP:
public function updateSessionActivity($userId, $ip, $controller, $action, array $params = [], $viewState = 'valid', $robotKey = '')

But I checked against the XenForo vendor files and that was wrong, it should match:

PHP:
public function updateSessionActivity($userId, $ip, $controller, $action, array $params, $viewState, $robotKey)

This re-release fixes that and should then play nicely with the other add-on.

Apologies.
 

Attachments

From now on, I’ll label releases as minor or major so each of you can make a more informed call about when to update. For example, you may choose to hold off on minor updates and only apply major ones more promptly.
Thank you, that would actually help a lot!
 
One thing that I see which makes me wonder: Since upgrading from 1.1.2 to 1.1.4 this morning (leaving out 1.1.3) I do not see a single challenge / challenge required in the event log. Before that, it was popping up quite frequently. So it seems, that singe 1.1.4 (or possibly 1.1.3) bots are bypassing to content unchallenged. Not having any bots since 8 this morning seems somewhat unplausible.

Be aware that due to my pre filtering more or less the only bots that can hit BotGuard on my forums are coming through residential proxies from limited countries as almost everything else is filtered out before.
 
Back
Top Bottom