Closed (fixed)
Project:
Metatag
Version:
7.x-1.x-dev
Component:
Other tags
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
3 May 2013 at 11:20 UTC
Updated:
16 Jun 2016 at 18:11 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
damienmckennaHave you checked the instructions in the README.txt file? There are some tweaks that occasionally need to be done to get them to output. Do any meta tags show? What are you using to display the term pages - core's default pages, Views, Panels, etc?
Comment #2
fhdrupal commentedThanks for response, using views to display contents for the auto generated terms path. The terms itself has Meta description option during creation, but doesn’t show it later.
Comment #3
kolier commentedI'm encountering the same issue. This patch would temporary fix, it works, but I'm not sure if it's following the best practice while I'm not familiar with the Ctools context.
Comment #4
kolier commentedChange status.
Comment #5
kolier commentedChange version to 7.x-1.x-dev.
Comment #6
fhdrupal commentedI put tried many Tokens for description is in global metatag settings, but still don't see description output in the header. I apply the patch given in #3, but it also did not work. Even I tried simple text without token, still can't see description. I am using omega sub-theme for e-commerce project. Thanks
Comment #7
kolier commentedThis may only fix the metatag_panels.
Are you talking about views?
The potential problem maybe the $context->keyword shows "taxonomy_term", but the tokens functionality need to use "term" to identify.
Comment #8
damienmckennaignore that
Comment #9
fhdrupal commentedWhen I put token “[term:name] ” in the title box of the metatag module, it works. That mean it recognizes the term from the url. But doesn't pick up the description. Tried to changed to the dev version module, applied patch nothing works.
Comment #10
damienmckennaCommitted! Thanks kolier.
Comment #12
kopeboyI'm using Metatag 7.x-1.0-beta9 and Views 7.x-3.8, new site building from scratch.
Configuration of said modules is default.
I enabled the provided View to override taxonomy/term/%
Metatag option in the View is "Using defaults".
All those taxonomy term pages now don't have the metatags. Not even the TITLE.
I only have:
<meta name="description" content="A view to emulate Drupal core's handling of taxonomy/term.">The site is multilingual and I'am using Translated taxonomy terms (x ID for each)
EDIT: I deleted the default Metatags FROM the view (now showing overridden), and all the default metatags defined in admin/config/search/metatag are now correctly provided.
Please add some instructions somewhere.. or fix this, because now I have to do this for every View page I create :(
Comment #13
damienmckenna@kopeboy: I'm sorry you're running into these problems. Could you please open a new issue for this, as-is you're hijacking a closed issue. You might also try searching the issue queue for open tickets related to "views", there might be an existing issue for the problem you're seeing. Thanks.
Comment #14
webhippies commentedSorry for posting and hijacking a closed issue but have to share the solution that worked for me.
I also deleted the default metatags from the view collection_products (Master, Page & Block) as kopeboy did at #12 and created a little module that i found out there http://drupal.stackexchange.com/a/146896
Hope this helps. I wasted a couple of hours searching.
Comment #15
damienmckennaComment #16
abhishek.pareek commentedThanks kopeboy, for your helpful comment, solved my problem. :)
Comment #17
hevmills commentedI couldn't get #14 to work in Commerce Kickstart. I used dpm() the display $entity_info and found that there wasn't a $entity_info['path'] declared, but there was an $entity_info['default path']. Changing one line seems to have got this working for me:
Change:
if (isset($entity_info['path']) && $entity_info['path'] == 'taxonomy/term/%taxonomy_term') {to
if (isset($entity_info['default path']) && $entity_info['default path'] == 'taxonomy/term/%taxonomy_term') {I have no idea if this is correct, but it seems to be working here.