Hey everyone.
When i assing some value of metatag description, it's correctly injected into the selected view page html code. The bad news is that the same metatag value appear in some other views pages (2 exactly)...

For example I have a pages A, B and C (Views generated, type Node - like taxonomy teasers view). And for those pages I set meta descriptions:
for A set X,
for B set Y and
for C set Z.

Result:
page A has description X as expected;
page B and C have descriptions X.

What the hell??

Did anyone have this kind of problems? For me it's the only one problem with the site I have: www.geotekst.pl - it's polish site nawigate to www.geotekst.pl/aktualnosci and www.geotekst.pl/aktualnosci_filmy for example to see what i'm talking about (if it's not fixed yet.)

Anyway, this should corrected.
Cheers!

Comments

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Title: Nodewords works incorectly with Views » Nodewords incorrectly works with Views pages

As I already reported in another issue, the support for Views pages will be implemented differently; rather than having a specific support for Views, and Panels, the module will implement a generic support for page meta tags.

pawel.traczynski’s picture

pawel.traczynski commented

I'm sorry but I don't understand.
What exactly do you mean?

pawel.traczynski’s picture

pawel.traczynski commented

I would be very greatful if you please explain how could I make meta tags injected into the html code for specified views.

On the meta tags project page it's written that this module works with views. I'd love know why it doesn't work for my view.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Version: 6.x-1.0 » 6.x-1.x-dev

I am changing the referring version, as bug can just be fixed in the development snapshot, and in the new official release created from the development snapshot.

pawel.traczynski’s picture

pawel.traczynski commented
Version: 6.x-1.x-dev » 6.x-1.0

OK. I understand that I should wait for the new version to show up.

Let me explain how exactly is this bug happening - might help you in developing the module.

Lets say i have a content type 'x'. This content type uses taxonomy terms: a, b and c.

I create 3 views:

  • view ONE: displays node of 'x' content type, taxonomy term 'a' only
  • view TWO: 'x' content type, taxonomy term 'b'
  • view THREE: 'x' content type, taxonomy term 'c'

Now I add the meta-description and keywords for each of those views. Each description is different.
If the path-word of the FIRST view is part of the path-word of view TWO or THREE then that other view (second or third) will display the meta-tags of the FIRST view.

Example 1:
The paths for views are:
1: drupaldir/news
2: drupaldir/conferences
3: drupaldir/articles
Here everything works fine.

Example 2:
The paths for explained views are:
1: /drupaldir/news
2: /drupaldir/news_conferences
3: /drupaldir/news_articles
Here the nodewords works incorrectly, because the path of the view ONE is part of views TWO and THREE. Because of that view TWO and THREE will have the meta-description assigned to view ONE. If i delete view ONE then views TWO and THREE will display their own correct descriptions. If I create the new view ONE, with all the same settings (especially the path), the nodewords will work incorrectly again.

Example 3:
The paths for views are:
1: drupaldir/article_s
2: drupaldir/articles_archive
3: drupaldir/articles_upcoming
Here it will works correctly because the view ONE path-word isn't part of the paths of view TWO and THREE.

Hope it helps!
Drop me an answer, please.
Cheers!
Pawel

avpaderno’s picture

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

Meta tags doesn't associate the meta tags to a view basing on its path, and it doesn't associate to a view the meta tags associated to the nodes, taxonomy terms shown in the view; for the module, a view, a node, a taxonomy term are completely different entities.

It could help if you would report exactly the meta tags associated with a node, a taxonomy term, and the view which contains both; then reports the meta tags you see in the HTML output.

pawel.traczynski’s picture

pawel.traczynski commented

"Meta tags doesn't associate the meta tags to a view basing on its path, and it doesn't associate to a view the meta tags associated to the nodes, taxonomy terms shown in the view"

Yes, I know that :-)
I just said that the meta tags associated to chosen views are breaking down if the path is set up like described before.
Other views settings doesn't matter at all. I don't know how exactly is the nodewords working but that's a fact that it breaks (on my site) when the path is set up like described. Magic? :-)

Ok. And the report You asked for:
I didn't use any meta tags associated with taxonomy terms. The only meta tags were those assosiated to nodes contained in those views and those views themself. It didn't matter what meta tags values were associated to those nodes. It didn't have any impact on the views meta tags either. If the described view ONE had no values set for meta tags keywords and/or description, then views TWO and THREE had no meta-descriptions at all, and had only those keywords which were specified on the configuration pages as global keywords.

I checked that I want to have the following meta tags to be included in the code: Copyright, Description, Keywords, Robots.
Hope it helps.
Cheers.
Paweł

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Closed (duplicate)

For an explanation of why version 6.x-1.0 doesn't work correctly in cases like that, see #538630: _nodewords_detect_type_and_ids + views + wildcard arguments in view = broken.

I am marking this report as duplicate of that one.