Thread Starter
ljmac
(@ljmac)
I just wanted to add that logging for my other plug-ins is working fine (e.g. Bad Behavior), so this issue appears to be specific to your plug-in. I also tried tripping up the GASP login protection myself, but nothing was logged. It used to log many bad login attempts per day.
Plugin Author
Paul
(@paultgoodchild)
Hi,
The best way here is to look at the site in question. Would you be able to provide me access to it, and ideally some FTP?
The new feature doesn’t clean out the logs, it cleans out entries used by the GASP feature, and the login feature. It wont automatically clean logs for you. I may provide that as an option later.
Thanks,
Paul.
Thread Starter
ljmac
(@ljmac)
Hi,
Unfortunately this is difficult due to the multiple levels of security I have (IP restriction, Apache password protection etc.).
Can you tell me exactly where the logs are stored? If so I can probably diagnose the problem myself.
Also, there’s no chance that the GASP login protection has stopped working, is there? If I try to login myself without the checkbox ticked, I can’t log in, so I assume it must be working okay.
Plugin Author
Paul
(@paultgoodchild)
My feeling would be the login protection is working fine, it’s just the logging has probably got a quirk in it, but I can’t replicate on my side, so it’s hard to know.
The logs are stored in a database table dedicated to logs, which is created when the plugin is installed and features that use the logging are enabled.
Perhaps silly, but could you check your settings to ensure that the logging for the login protect section is definitely enabled. Try disabling if it is, and re-enabling it. It could be a quirk with the stored settings for example.
I’ll take another look and see if there’s perhaps something I can do with the “Clear/Fix” buttons to ensure that the logging table is definitely created – perhaps even display some notices if logging is enabled, but there’s a DB issue with writing them for example.
Thanks for any digging you can do here.
Paul.
Thread Starter
ljmac
(@ljmac)
Hi Paul,
I can see all the tables related to your plug-in are empty. I have only the Firewall and login protection enabled – is this how it should be?
In the past, logging was always on, but *detailed* logging could be switched on and off. Are you saying that in newer versions, the *detailed* logging needs to be switched on to log the GASP attempts? (Once again, these were logged even without detailed login protection logging enabled in earlier versions.)
Plugin Author
Paul
(@paultgoodchild)
Hey,
If it was logging before and the logging option was disabled, then that was a bug. In order to allow you to finely tune the plugin for performance vs functionality depending on your load, we make logging an option.
Logging should need to be switched on for either / both firewall and login protection, depending on your needs.
Does that make sense?
Thread Starter
ljmac
(@ljmac)
Hi Paul,
Yep, that does make sense. So I tried switching on the login logs, then tried to log in myself without ticking the GASP check box. Still nothing!
So it seems that with older versions, the login logs worked whether they were switched on or not (I only saw GASP attempts in the logs, so it appears the firewall was not being logged). But with newer versions, it seems they don’t work whether they’re switched on or not!
Thread Starter
ljmac
(@ljmac)
Oops, I spoke too soon! It seems my own attempt to to trip up the logs was not recorded for some reason, but since I switched it on, it has started recording real bot attempts.
So it seems this is a kind of retrograde bug report: logs worked when they shouldn’t in earlier versions, but now work as they should. So I guess you can mark this resolved. 🙂
Plugin Author
Paul
(@paultgoodchild)
Heheh, great to hear it’s working again for you. It’s a bit of an odd bug I suppose, but glad that’s it’s working more like it should.
Thanks for working through this!
Paul.
