The forum index page at /forum should be converted form a table to a list. The current table mark-up treats containers, forums, and subforums as table rows. Since all of them are structurally the same in the HTML mark-up, flexibility for themers is limited. A nested list structure would provide more flexible mark-up for themers. Semantically it also correctly defines the relationships between containers, forums, and sub-forums.

I am prepared to submit a patch for this.

CommentFileSizeAuthor
#5 forum-1130276-5.patch1.27 KBDevElCuy
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

droplet’s picture

sub

Michelle’s picture

I've done extensive work in changing the layout of this page in Advanced Forum but it never occurred to me to use a list structure. I'd like to see what's come up with here and see if it's anything I can use. I haven't quite finished the AF changes as there are a few remaining issues to iron out but it's closer to other forum apps than Drupal core is. If there's anything in my work that you can make use of, feel free. :)

Michelle

megan_m’s picture

Thanks for commenting, Michelle! I was planning on getting in touch with you at some point...

It turns out that this is a bit more complicated than I expected (surprise!). The output for the forum list comes from get_taxonomy_tree, which doesn't output a nested array. You get a flat array which doesn't easily enable you to format it as a nested list.

mattyoung’s picture

>get_taxonomy_tree, which doesn't output a nested array.

take a look at the comments in http://api.drupal.org/api/drupal/modules--taxonomy--taxonomy.module/func...

DevElCuy’s picture

FileSize
1.27 KB

Implementation of forum_get_tree(), based on the function commented at #4.

Michelle’s picture

Status: Active » Needs review

Setting this "needs review" since there's a patch, now.

Michelle

Liam McDermott’s picture

I won't mark this as needs work since I'm not sure on this, but shouldn't the *_get_tree function be part of the taxonomy module? I'm sure other people are looking for this functionality in non-forum related modules.

xamanu’s picture

I agree with Liam - it should be included in the taxonomy module. There is a patch available now: #1409780: Include hirarchical version of get taxonomy_get_tree

Anyway, I might not get the point completely. I just think, putting all the output of the forum list into a nested list would drive us into another problem: We'd loose a lot of semantics, since additional information, such as "Topics", "Posts" and "Last post" would be not clearly assigned to the respective information (as it would through the table's columns structure). Screen readers might not interpret the information in a good way.

yoroy’s picture

Looks like this changes the look of this page. Would be good to have before/after screenshots to help review.

droplet’s picture

Status: Needs review » Needs work

What's the purpose of this issue ? convert from table to list or adding a function for later use? I don't see any markup changes there.

megan_m’s picture

To convert from table to list. The problem is that it needs a get_taxonomy_tree function that actually outputs a hierarchical tree rather than a flat list. That needs to be addressed before we can fix the mark-up (see issue mentioned in #8, above)

@xamanu It's kind of a trade-off. Right now the sub-forums are structured with a <div class="indent"> inside the table cell. That's the only structural difference between container forums and sub-forums. Converting to a list would provide a semantic relationship.

There is a bit of a trade-off here. You lose the relationship between number of topics and posts, but you gain the relationship between parent and child forums. Personally, I think the latter is more important.

DevElCuy’s picture

Issue tags: +dlatino

Adding tag "dlatino" for reference of the Drupal Latino community.

joelpittet’s picture

Would it be worth moving this to a view so the style can be changed, then default it to a ul list view? Or would the nesting still be an issue?

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

geek-merlin’s picture

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Status: Needs work » Postponed

Forum is approved for removal. See #1898812: [policy] Deprecate forum module for removal in Drupal 11

This is now 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.

It will be moved to the contributed extension once the Drupal 11 branch is open.

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.