On term pages for both a parent and child term, it seems the meta tags for the parent term are being used. The meta tags for the child term should be used though.

Comments

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

It's not clear to me what you mean by a term page for both a parent and a child term. May you explain me that?

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Postponed (maintainer needs more info)
OneTwoTait’s picture

OneTwoTait commented

For example, there are two terms: "fruit" and "apple". "fruit" is the parent term for "apple". Fruit has a term id of "4" and apple has a term id of "6".

The page with the path "taxonomy/term/4,6" shows nodes tagged with both "fruit" and "apple".

Currently, using Meta Tags, the meta tags for "fruit" will be used. However, for a page like this I think it would be more appropriate to use the meta tags for "apple".

The term "fruit" may have many child terms, and without this differentiation all those pages will have the same meta tags which is bad for search engines.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

Currently, using Page Titles, the meta tags for "fruit" will be used.

My apologies for not understanding correctly what you are saying. You made a reference, and I am not sure if you are suggesting to not do as Page Title does, or you got confused, and you posted here a report that should be for Page Title.

OneTwoTait’s picture

OneTwoTait commented

I meant Meta Tags... obviously I used the wrong module name.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

Is the issue still valid for the development snapshot?

OneTwoTait’s picture

OneTwoTait commented

I'm using 6.x-1.0 now and it is still an issue, yes.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

The development snapshot is version 6.x-1.x-dev; version 6.x-1.0 is an official release.

OneTwoTait’s picture

OneTwoTait commented

It's not an issue on the development version.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Version: 6.x-1.0-rc1 » 6.x-1.x-dev
Status: Postponed (maintainer needs more info) » Fixed
Issue tags: +6.x-1.0

As version 6.x-1.0 cannot be changed, and the never version doesn't have the problem, I am setting this report as fixed.
Version 6.x-1.x-dev is the code used to create version 6.x-1.1.

Status: Fixed » Closed (fixed)
Issue tags: -6.x-1.0

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

Issue tags: +6.x-1.0

Restoring issue tags, see #2125755: System messages removed all issue tags during D7 upgrade.