Banned Items

Banned Items module changelog Version 1.6.2: - Change: Removed "Retry-After" header from 403 Forbidden response - Change: Banned item timeout cache key changed from 5 minutes to 60 minutes Version 1.6.1: - Bug Fix: Possible Activity Log error resetting banned item cache when auto ban is enabled Version 1.6.0: - New: "Auto Ban Blocked Requests" global setting that is used to enable auto-banning - Change: Updated view structure to support new updates in Jamroom Core 6.5.12+ Version 1.5.4: - New: "Enable in Forms" global config to enable/disable automatic form submission scanning Version 1.5.3: - New: "banned_item_create" Event trigger fired when a new banned item is created - New: "banned_item_delete" Event trigger fired when an existing banned item is deleted Version 1.5.2: - New: Create Banned Item form updated to allow creating multiple banned entries Version 1.5.1: - New: "Blocked URL Strings" config option to define strings to block in URLs - New: "Blocked User Agents" config option to block access by browser agent Version 1.5.0: - New: "Enable Blocking" config option to block server scanners for wordpress, phpMyAdmin, etc. - Change: Exclude existing profile/user names and emails from banned text check Version 1.4.0: - New: Option added to select word or partial seaches for banned names, emails and words Version 1.3.6: - Change: Updated to prevent the local server IP address from being banned Version 1.3.5: - Change: Admin Note for a banned item entry now opens in a modal window when clicked Version 1.3.4: - Bug Fix: Banned items may not show as banned when using the Test Items tool Version 1.3.3: - New: Admin note can be added when adding a ban to help keep track of why the ban is there Version 1.3.2: - Bug Fix: Banned Items not being deleted during Developer Tools system reset Version 1.3.1: - Bug Fix: Some "name" banned items could get used as "word" banned items Version 1.3.0: - New: Support for modules to register "banned_type" support for custom ban functions Version 1.2.1: - Change: Banned words must be at least 2 characters in length - Bug Fix: Multi-byte banned words may not be caught as substring of string Version 1.2.0: - New: Banned Item check runs on all text fields by default (no more requiring module config) - New: Searches that include banned words result in no items found for non-admin users Version 1.1.3: - Bug Fix: Item Value error when entering certain characters for a banned name Version 1.1.2: - Bug Fix: "word" boundaries added in 1.1.1 may not work properly on HTML string Version 1.1.1: - Change: "word" banned items no longer match substrings of longer words - Bug Fix: Searching in the Banned Items browser was resulting in a 404 not found page Version 1.1.0: - New: "Test Items" tool will test a value against currently configured banned items - Change: Partial IP Addresses can now be entered as Banned Items Version 1.0.3: - New: Support added for banning email addresses and email domains Version 1.0.2: - New "Banned Items" tab in ACP that is the default view for the module Version 1.0.1: - Update error message for banned IP to use jrCore_notice() Version 1.0.0: - Initial Release