The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.I went from 1.12-beta3 to 1.12-beta5 to 1.12-beta9 today, and now I am missing
- the option box to use meta tags for the front page (admin/content/nodewords on beta3)
- the input field "specific meta tags" - Front page (/content/nodewords/meta-tags/frontpage on beta3)
On 1.12-beta9 there is no option box to use meta tags for the front page, and under "specific meta tags" there are only sub-pages for the 404 and 403 error pages.
Is this function not there any more or am I missing something?
Comments
Comment #1
Anonymous (not verified) commentedThe settings have been removed because those meta tags can be handled through nodewords_custom_pages.module.
Comment #2
rokrEven with this sub module enabled the settings won't show up.
cheers, Ronald
Comment #3
rokrComment #4
Anonymous (not verified) commentedAre you sure the modules have been updated to the latest releases? If a module is not the latest version available, the settings page will not appear.
I am using the latest developed code, and I cannot reproduce this issue.
Comment #5
rokrI just enabled 1.12-beta9 on a site for the first time. After reading the project page this seemed to be the latest "stable" 1.12 release.
And i ended up with several issues and thats why i'm here. ;-)
(sorry to say but 1.12-beta9 is kind of unusable, together with #774652: Meta tag ROBOTS default is noindex,nofollow)
Going to try the dev soon.
cheers, Ronald
Comment #6
Anonymous (not verified) commentedI am changing the status of this support request because it has been already replied, and there have not been replies.
Comment #8
thinkpadius commentedI'm sorry to reopen this, but I'm also using the 6.1.12beta9 release and I can't seem to get metatags to function correctly on the front page.
I've created a custom nodewords-page for the frontpage - I even doubled down on the paths - I choose as well as /node just to be sure.
When I look at the metatags output all it shows me is the token [metatags-description] so it clearly is not integrating with token.
Now I thought to myself "well its because there's not content to pull a description!" so I replaced the token with my own text describing the site. But, still the problem continues.
I'm not sure what to do next. Advice would be appreciated. How do you set it up on your site?
Comment #9
dave reidYes, the token will not work on something that is not a unique content page (like a node page, etc). I re-tested a custom 'front page' meta tag set (with path = '') and it pulled in everything correctly for me. I feel confident marking this as fixed.