Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Part of [META] Services injecting @database in core. See the parent issue for details.
This is dependent on the BanIpManager doesn't have interface
Comment | File | Size | Author |
---|---|---|---|
#8 | 2224723-ban_ip_manager-8.patch | 2.86 KB | skipyT |
#6 | 2224723-ban_ip_manager-6.patch | 2.86 KB | skipyT |
#3 | ban_ip_manager.patch | 3.04 KB | skipyT |
Comments
Comment #1
skipyT CreditAttribution: skipyT commentedComment #2
skipyT CreditAttribution: skipyT commentedComment #3
skipyT CreditAttribution: skipyT commentedAdded the mongo.ban_ip.manager mongo service.
Comment #4
skipyT CreditAttribution: skipyT commentedComment #5
marcingy CreditAttribution: marcingy commentedWhen we ban an IP in mongo we never set iid, as a result it won't exist, instead we will have an _id. This will be a mongo_id object based _id. I am thinking that we need to swap this query to use _id (free index) and also explicitly set the _id when we create the ban record.
Comment #6
skipyT CreditAttribution: skipyT commentedusing the _id from mongo now instead of iid.
also deleted the isDenied function, because it was deleted in core and rerolled the patch on current mongo codebase.
Comment #8
skipyT CreditAttribution: skipyT commentedfixed typo.
Comment #9
fgmAlthough there was no move in 4 years on that issue, the feature and its implementation might make sense in 8.x-2.x, so bumping.
Comment #10
fgmRebased on 8.x-2.x but needs changes to use the 8.x-2.x API instead of 8.x-1.x.
PR at https://github.com/fgm/mongodb/pull/63