I want to use the google webmaster tools. For this:

    I uploaded module nodewords to my website
    Enabled the modules nodewords, nodewords basic and nodewords verification. (in home/admin/build/modules)
    I ennabled (in home/admin/content/nodewords) “Google Webmaster Tools verification code” on both the “Meta tags to show on edit forms” as the “Meta tags to output in HTML”

But ......where do I enter the: google verification code ?

CommentFileSizeAuthor
#16 Voila_Capture_55.png110.17 KBAnonymous (not verified)
#14 Voila_Capture_100.png69.37 KBAnonymous (not verified)
#14 Voila_Capture_102.png90.35 KBAnonymous (not verified)
#8 remove_edit_boxes.patch1.8 KBjenlampton
#6 remove_verif_edit_boxes.patch1.99 KBjenlampton
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

marijnvanlith’s picture

Status: Active » Closed (fixed)
jenlampton’s picture

Title: Where do I enter the google verification code? » Where do I enter verification codes?
Version: 6.x-1.3-beta5 » 6.x-1.2
Status: Closed (fixed) » Active

I think this is a valid question, I can't find a new settings page, new fields on the existing forms, or anything else for verification tags, though I remember seeing it on a previous version of the module.

@marijnvanlith what was your solution? It would be great if you could post it here for the rest of us when you mark an issue closed :-)

jenlampton’s picture

Title: Where do I enter verification codes? » Verification codes can't be set without "Tags to show on edit forms" boxes checked
Category: support » task

Aha, I found it. You need to check the boxes for "Tags to show on edit forms" if you want the form elements to show up on the "front page" tab under "global meta tags".

This is confusing, I think the instructions on the "Tags to show on edit forms" section need to be clearer, to explain that those boxes also apply to settings forms, not just edit forms, or better yet, these checkboxes should not be required to set the defaults.

Also, the language on this tab should be updated (this is super minor) these are not really "global" meta tags, they are defaults.

Jen

apaderno’s picture

Version: 6.x-1.2 » 6.x-1.x-dev
Status: Active » Fixed

Tags to show on edit forms is generic enough to include also the front page settings form; I could not use Tags to show on settings forms because the node edit form is not a settings form.

The strings used in the settings tabs have been already changed in the development snapshot, and in the beta releases.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

jenlampton’s picture

Status: Closed (fixed) » Needs review
FileSize
1.99 KB

These checkboxes should not be required to set the defaults. In fact, they should not exist at all. This part of the nodewords module is confusing as it is now. I believe this improves things a little bit.

My thoughts: If you have enabled the verification tags module, then it goes without saying that you'd like to use some kind of verification tag. It's harmless to leave all three fields present on the front page form, and print only those indicated via settings.

Patch attached. (it's often better to explain by example)

Anonymous’s picture

Category: task » feature
Status: Needs review » Fixed

Users with permission to administer meta tags can edit any meta tags, even if they are not selected to appear in the meta tags edit form.

jenlampton’s picture

Status: Fixed » Needs review
FileSize
1.8 KB

Wow, the dev branch is looking much better. Thanks so much for all your hard work on this.

Patch removes problematic verification checkboxes for "edit forms" (re-rolled against dev branch).
Please review.
Jen

Anonymous’s picture

Status: Needs review » Fixed

The conditions that are verified because the edit field for a meta tag is shown are the following:

  1. The user has permission to administer meta tags; OR
  2. The meta tag is listed between the meta tags that appears in the edit form.

As the verification meta tags are edited in the front page meta tags edit form, which is visible to users with permission to administer meta tags, it is possible to edit those meta tags in that page, even if they are not selected to appear in the edit form; therefore, it is not true that verification codes can't be set without Tags to show on edit forms boxes checked.

Madbreaks’s picture

Title: Verification codes can't be set without "Tags to show on edit forms" boxes checked » Verification input fields missing on node forms altogether

As discussed above, regardless of how I configure nodewords, the site verification input fields do not show up on node creation/edit forms. What's more, I'm logged in as user 1 and can see ALL other meta tag input fields (enabled or not on nodewords config page) - I understand that it's supposed to work this way for the superuser. BUT, no verification input fields are there. I've disabled/reenabled verification tags on the modules page, still no joy. The only place I see these fields is if I click "Default and Specific Meta Tags", I see them on the "front page" tab (which I'm not utilizing per my config, and I do not plan to). If I try to create an entry under "other pages", the fields do not appear there either.

6.x-1.11 and D6.14.

What am I missing? Am I only supposed to be able to set these for the "front page"?

Thanks

Madbreaks’s picture

Version: 6.x-1.x-dev » 6.x-1.11

D'oh! Sorry for double post. :/

apaderno’s picture

What am I missing? Am I only supposed to be able to set these for the "front page"?

Site verification meta tags are looked only on the front page; that is why you can set them just for the front page.

jenlampton’s picture

Title: Verification input fields missing on node forms altogether » Remove verification tag checkboxes for "edit forms" since they ONLY appear on the front page
Category: feature » task
Status: Fixed » Needs review

@kiamlaluno & @Madbreaks

Verification tags ONLY appear on the front page.

@kiam The original issue...

verification codes can't be set without "Tags to show on edit forms" boxes checked"

has been resolved in the dev branch. But the way the module works with the "edit forms" checkboxes is terribly confusing, and also unnecessary.

Verification tags do not need checkboxes to allow them to appear on "edit forms", since the ONLY form they actually appear on is the form to set tags for the front page.

The patch in #8 resolves that problem. Would someone please review this patch?

This is a huge usability issue, and I'd like to get it resolved. If you do not like the way I've attempted to fix it, please suggest an alternative. The way I see it, this issue will not be fixed until people stop getting confused (as demonstrated in #10). But, would you prefer I open a new issue instead?

Jen

Anonymous’s picture

Status: Needs review » Reviewed & tested by the community
FileSize
90.35 KB
69.37 KB

I am changing the status to remind me that I changed the code in the local copy of the module, and I just need to commit the code.

The settings to enable the meta tags are two sets: one for the administrative settings page, and one for the other pages.
The meta tags that can only appear in the administrative settings pages will not have a setting for the other pages.

If Drupal.org allows me, I will add a screenshot to show how the settings page is changed.

There is a little issue that I need to fix, but the site confirmation meta tags appear just in one list, and so do other meta tags.

MercuryPDX’s picture

We are experiencing the same issue with google being unable to find the tag.

When I "View Source" on the homepage I see the following:
<meta name="verify-v1" content="[actual tag deleted]" />

Google is looking for:

<meta name="google-site-verification" content="String_we_ask_for">

So it appears that the NAME needs to be updated from "verify-v1" to "google-site-verification" somehow. Any ideas on how to go about it?

(Side note: I am aware this is discussed here: http://drupal.org/node/733092 , but that is in regards to a different "Site Verification" module, and not Nodewords.)

Anonymous’s picture

FileSize
110.17 KB

@MercuryPDX: That issue is not related with this one. Anyway, the latest code uses already the meta tag expected from Google Webmaster Tools.

Anonymous’s picture

Status: Reviewed & tested by the community » Fixed

The code has been committed.

As usual, read what reported in the project page, before to update the installed modules.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.