• I really liked the feature allowing me to view all the bad login attempt so I could add them to the “banned users setting” to block the IP addresses.
    I also miss the feature allowing me to view all the 404 detection together. It was easy to see which page needed redirection. Now I have to go through the whole log.
    Any way you can offer to go back to the previous version?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hi,

    Moving forward I hope you’ll come to enjoy this format better, though I understand it may take some getting used to. Simply put, all of the data isn’t equally important, and shouldn’t be presented as such.

    For example, the bad login attempts should be considered informational, not actionable. Adding these IPs to the Banned Users is causing more work for yourself. The plugin will automatically ban them if they reach the lockout criteria in your Global Settings. The plugin is designed to save you time, not create more work for you. Moving forward a major plan of ours is to automate the process even more.

    Thanks,

    Gerroald

    This does not answer the issue raised. I’m with mflem – I liked the ability to filter the specific log issues I was interested in at the moment. Your comment that “all of the data isn’t equally important, and shouldn’t be presented as such” makes no sense, since that’s exactly what you’ve done. Thousands of log entries of all different types are now lumped in together with no ability to filter and sort them.

    …with no ability to filter and sort them.

    That is actually not true.

    Simply hover with the mouse cursor over the log records in any column (except Details) and a filter dashicon with show up. Then click on that filter icon to filter. Easy as that.

    Oh and previously you were unable to sort anything from the main log screen. Now you can sort on Time and Host …

    I think the Logs page is actually offering better functionality now … ??
    Perhaps you just need a bit of time to get used to it.

    @nlpro, thank you! For some reason, I did not get that filter option, but I am now seeing it with the latest update. Thanks for letting me know about it – this is the function I was looking for.

    Gerroald – I take issue with your reply that “bad login attempts should be considered informational, not actionable”

    If you have used the feature to “hide backend” (from this very same plugin), then a bad login attempt is indeed actionable. It indicates that someone (beyond the two users who know the login slug) has defeated the “hide backend”, or your login slug is compromised. But you’ve hidden away the bad logins now, so we might not ever see this.

    It’s a bit presumptuous for you to assume that you know exactly what is important to whom. Particularly when you can’t even get it right in your responses here.

    What is wrong with letting users decide what they want to see?
    Alternatively, if you are dead set to dumb-down the plugin, why not offer a “dummy mode” or something similar?

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Itheme Security latest update, view login attempts’ is closed to new replies.