When "Use front page meta tags" is checked, if the front page is a node, the "meta tags" fieldset should display and update the default values defined in "Default and specific meta tags" > "Front page."
Here is my use case:
- Checked "Use front page meta tags" so that I could display site verification codes.
- On "Default and specific meta tags" > "Front page," I filled in Description, Keywords and the site verification codes.
- Everything works as expected and the front page is outputting the appropriate meta tags.
- The client comes along to edit the "description" and gets confused when she pulls up the edit form (node/#/edit), finds the "Description" field blank and then when she enters the new description, it won't update in the HTML.
So, in order to make it easier on the client, the "meta tags" fieldset should be pre-populated with the default values (including the site verification codes which currently don't show up there) and submitting the node updates the default values.
Another option is to simply hide the "meta tags" fieldset from the front page edit node form, with a link or note for the user that she needs to visit "Default and specific meta tags" > "Front page" in order to edit the meta tags on the front page.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | nodewords-665042-2.txt | 1.78 KB | jbjaaz |
Comments
Comment #1
jbjaaz commentedIf anyone is curious how to achieve this without hacking the module, hook_form_alter works well.
Comment #2
jbjaaz commentedSo, I gave modifying the module a shot and came up with something. I'm taking the approach of hiding the Meta Tags form from the front page edit node form and replacing it with a message pointing the user to the Front Page settings page. See the attached patch.
I've tested it on Drupal 6.15.
Comment #3
Anonymous (not verified) commentedComment #4
Anonymous (not verified) commentedThe code has been changed, and the meta tags edit fields don't appear for the node that is used as front page; the help message for the front page meta tags edit page reminds of this.
Comment #5
Anonymous (not verified) commentedI am changing the referring version to the latest version available, which does not implement the requested feature.
Comment #6
vikingew commentedAfter updating to 6.x-1.x-dev(2010-Apr-09) which has a CVS commit referensing this issue, I get a warning:
running update.php appearing on 'Overview' and 'Select update' stages and when finally clicking update button just a blank page.
And I found the solution! :-) it appears as a space character has sneeked in infront of the opening
<?phptag of the nodewords_custom_pages.module file.