Problem/Motivation

The detail page of the Category taxonomy lists related events, locations, artists, and others. But it doesn't take into account that there is a term hierarchy. So entities linked with a subcategory aren't shown.

Steps to reproduce

  1. Install OpenCulturas with default content
  2. Create a few events(, locations, artists, …) and assign them to the category Rock and pop music, which is a subcategory of Music.
  3. Open the detail page for the Music category (/en/categories/music)

Expected result

All entities created in step 2 will be shown.

Actual result

No entities are shown, because they are releated to a subcategory.

Proposed resolution

Use a hierarchy context filter with a depth of 1.

Remaining tasks

  • Write patch
  • Review
  • Commit
Command icon 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

mrshowerman created an issue. See original summary.

mrshowerman’s picture

Assigned: mrshowerman » Unassigned
Issue summary: View changes
Status: Active » Needs review
hexabinaer’s picture

Makes sense, absolutely! I reviewed the diff and opt for a merge.

tobiasb’s picture

Status: Needs review » Fixed

Merged into 2.1.x.

mrshowerman’s picture

  • tobiasb committed 460b0551 on 2.1.x
    Issue #3418400 by mrshowerman: Category taxonomy's detail page doesn't...
hexabinaer’s picture

Category: Bug report » Feature request

For the record:

For the initial version we had discussed both variations: results tagged with current term including/excluding child terms. There are arguments for both because it depends on how hierarchical tags are used. For example, when music events are always tagged with music and the suitable child term, the difference in drilling down would be "discovery" vs. "filtering".

I am changing the category to feature request just for the sake of respecting both scenarios as valid. Whoever finds this may get an idea of where to make changes for the "excluding child terms" scenario.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.