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.
The Forum module defines this option and is accessible from admin/structure/forum/settings
The Advanced Forum module uses it, but doesn't pass it to the view 'advanced_forum_topic_list'
Proposed patch attached
Comment | File | Size | Author |
---|---|---|---|
core-overrides.inc_.patch | 364 bytes | samsouk | |
Comments
Comment #1
troky CreditAttribution: troky commentedNice one. Committed to 7.x-2.x-dev. Thanks!
I believe 6.x needs this patch as well.
Comment #2
mcdruidThanks samsouk and troky; I've added this to 6.x-2.x-dev
The only difference was that I had to forcibly set the option on the view's handler, rather than using the setter method as per samsouk's patch (I tried that and it didn't affect the number of topics displayed).
...this is with Views 6.x-2.16 if that makes any difference.
Anyway, it seems to work.
Comment #3
mcdruidAlso noticed that the overridden menu callback advanced_forum_page does:
...but doesn't actually use this when listing forums (rather than topics - n.b. the option is labelled as 'topics per page' in the admin form, but that doesn't reflect the variable name).
So, for example, if you have lots of forums in the top level which are not inside containers, they all get displayed at /forum with no pagination.
In fact, core forum does exactly the same thing - I suppose there's an assumption that when the list of forums gets too long, they'll be organised into containers.
I suspect we won't get round to doing anything about this, but I thought I'd make a note of it here, as it's relevant to this issue.