Problem/Motivation
I have a lot of banned IPs (> 7.000). It would be more friendly to have a paged report of IPs. To load the report it takes "hours".
The pagination should work in combination with other features like filtering and bulk-selection / deletion!
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
Introduced terminology
API changes
Data model changes
Release notes snippet
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | After Patch.png | 68.74 KB | prasanth_kp |
| #10 | Before Patch.png | 65.95 KB | prasanth_kp |
| #8 | 3153262-8.patch | 1.62 KB | pagaille |
Issue fork drupal-3153262
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Issue fork ban-3153262
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #6
pagaille commentedComment #7
promesThanks, It works.
Comment #8
pagaille commentedGlad to hear it! Here's a patch for convenience.
Comment #10
prasanth_kp commentedThanks for the patch,
Its working perfectly fine, Now displays 50 records per page instead of all records on a single page.
Comment #11
alexpottI think we need to implement this in the BanAdmin class. Making this change of behaviour to findAll() - so that it no longer findsAll doest seem like a change in accord with our BC rules or a good one in light of the API... see
would no longer be true.
Perhaps in the interests of encapsulation we can add a pager method to BanIpManagerInterface so that all the interaction with the table is via the BanManager and an alternate backend could implement this.
Comment #14
quietone commentedThe Ban Module was approved for removal in #1570102: [Policy] Deprecate Ban module.
This remains Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project and the Extensions approved for removal policies.
The deprecation work is in #3482198: [meta] Tasks to deprecate the Ban module and the removal work in #3488827: [meta] Tasks to remove Ban module.
Ban will be moved to a contributed project after the Drupal 12.x branch is open.
Comment #15
johnvComment #17
mstrelan commentedMoved to contrib queue
Comment #18
anybodyComment #21
anybodyComment #22
anybodyComment #23
anybodyComment #24
anybodyPlease use a MR instead of a patch here for further review. Also see #11.
#3575759: Add (starts with) filtering for banned IPs table is related.
Comment #25
anybodyMaybe we should consider NOT adding a pager to be able to filter directly on the page, see #3575759: Add (starts with) filtering for banned IPs table. Might simplify things and it seems a pager wasn't really needed in the last 10 years? :D
What do the other maintainers think about it?
Comment #26
anybodyIndeed I'd vote to close this won't fix, as "good enough" and smart. Especially once we have a collapsible field group around the large list.
Comment #27
grevil commentedI agree!
Comment #28
anybody