There is an use case that I don't know if other Advanced Forum users are sharing. For example, I'm trying to convert a couple of sites to Drupal. They have many topics in a hierarchy (similar to Drupal's taxonomy), and each topic has subsections such as a forum, a guide to resources, articles, etc., about that topic. I hope this is possible in some way using the forum vocabulary for all the content types, since the forums need to use the default forum vocabulary.

The problem is: when those other content types try to use the forum vocabulary for the site structure, their nodes appear in the forum pages. However, in my case, I would like to show only nodes of the forum content type in the forum pages (I can show the other content types in their own separate pages).

I think some Advanced Forum users would prefer the current behavior, and others the feature I've described, so I think adding these two options would be very useful (of course, the current behavior as default, and my feature request as optional):

Show in forums:
[X] All content using the forum vocabulary (default)
[ ] Only content using the forum content type

Thank you very much for considering this for Advanced Forum 2.x, if possible.

Comments

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented
Status: Active » Closed (won't fix)

Sorry, but this is an extremely unusual use case and I'm not going to code something into AF that will only be used by one person. You could probably do this with a custom module but that's beyond the scope of this issue queue. If you want some help with that, try asking in the module developers forum.

Michelle

juan_g’s picture

juan_g commented

Thanks for your quick reply. If no other users are needing display/hide options, I will try to find some workaround for this case. Maybe time to learn PHP; I can only program in Perl now, since I come from the old Netscape ages... :)

Anyhow, I've just remembered an important limitation of the forum vocabulary: it doesn't allow multiple select of terms, even for non-forum nodes using the forum vocabulary. Maybe there will be new forum options for this in future versions, but for now it seems necessary to use -at the same time- two duplicate vocabularies with the same terms to work around the forum vocabulary limitations (not a very good solution, sigh...).

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented

Well, I can't guarantee you're absolutly the only person wanting to do this, but using the forum vocabulary for things that don't go in the forum is a pretty rare edge case. As much as I'd love to help everyone, I have to spend the coding time I have on things that will help at least the majority of users.

Michelle

juan_g’s picture

juan_g commented

Naturally, I understand the priorities. I think I will find a way to make this special site structure work with advanced forum, taxonomy, etc., and will post it here, just in case someone else needs it later. Thank you as always for all your good work on this essential forum module.

kopeboy’s picture

kopeboy
Primary language Italian
Location Milan
commented
Version: 6.x-2.x-dev » 7.x-2.x-dev
Issue summary: View changes
Status: Closed (won't fix) » Needs work

Actually using a set of arguments for both forums and blog articles is common, and it's my usecase as well.

We have a setting to choose which node type to style at /admin/config/content/advanced-forum, why not adding a similar setting for which node type to list in the Forum overview table?

Keep in mind that this would be solved by the much more important issue of how the Forum list is generated, which is the only one NOT created with Views, like all the other Topic/Posts listings provided by default (Active, unread, etc. and lists in each forum term).

See #720118: Better handling of containers, forums, and subforums