Posted by jasonabc on September 3, 2010 at 7:22pm
6 followers
| Project: | Nodewords: D6 Meta Tags |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Dave Reid |
| Status: | needs review |
| Issue tags: | v6.x-2.0 blocker |
Issue Summary
I have 6.x-3.x-dev installed. How do I set keywords and description just for the front page? I saw this feature in 6.x-1.11 but it seems to be missing from 6.x.3
Any pointers?
thanks!
Jason
Comments
#1
sorry - I got the version number wrong. Changed to 6.x-1.x-dev.
thanks
Jason
#2
anyone??
#3
Hi Jason,
You have a specialized page metatag support. You enter the path (for you it would be <front>) and the meta tags. That's in the Meta tags settings and you need to install a specific module for that to work.
Thank you.
Alexis
#4
Good luck getting it to work. I've been trying for weeks to get 1.x.-dev (two versions of it) to show custom meta tags on <front>, which I have set as a View.
I'm going to use drupal_set_html_head instead for my homepage. My regular contents nodes, the ones using defaults, thos ework fine, as long as you don't want to override the defaults in the node form (won't save changes).
#5
#6
Tagging as a stable release blocker
#7
#8
The frontpage meta tag definitions should take priority over others, e.g. if you have a node as your homepage it means the terms defined for the front page will be ignored. Certain tags you want defined via the admin, e.g. canonical URL.
#9
Here's a version of the patch from #7 that checks the front page first.
#10
Looks great to me.
#11
Hmmm... is this adding a new Front Page tab again?
Could we not use the new mechanism, just stick the Front Page in there automatically? That way, if you don't need it, you could delete it instead.
99% of my websites use a regular node as the front page so not having a specialized front page entry is a good thing for me...
What's your thought on that?
Thank you.
Alexis
#12
#14
Bumping to 6.x-1.13. We really, really need to get a 6.x-1.12 release out before adding any more new features.
#15
We've had a change of plans in the Nodewords project. What previously was known as 1.12 (which was an actual rewrite of the module) has been moved to 2.x. The new 1.12 version will be a minor bug fixing update. I'm moving this issue to the appropriate version queue.
#16
subscribe
#17
FYI, v6.x-1.13 has the Frontpage back again, if you aren't using Tokens in your meta tags you should use it.
#18
@AlexisWilke: I see the use case and have done so several times myself. Perhaps an option to use the separate Front Page settings should be included, with it defaulting to use the separate settings to retain backwards compatibility, but which would allow many sites to just use the tags from the homepage node?
#19
I'm stealing this issue to work on my idea from #18.
#20
Sorry, I've pushed my idea to a new ticket (#1406042: Option to not use the separate Front Page tag settings) and we'll leave this one as-is for now.
#21
FYI 6.x-1.13 also has an option on the main settings page "Use front page meta tags". This is enabled by default, so it use the values stored for the "front page", if the option is disabled it will instead load the values from the node (or whatever else is appropriate).