Allow to set a default value for the location meta tags as it was allowed before

To set the meta tags geo.url and icbm, you need to set the values for the form fields listed under the fieldset Location; it is possible to set those values only for nodes, and users.

So if you have a content type that has a location (via the location module) it automatically adds the GeoURL metatag?

Both the meta tags are populated from the data set with location.module.

Probably the module should also hide its own location fieldset in the case location.module is enabled; I am not sure if I will add that feature, anyway.

I had a default value set that propogated throughout the site.

It is not possible to set a default value for the location meta tags, as those values would be used also for the error pages, all the pages of the site when it is offline, the tracker page, and all the custom pages. That is surely not desired (what is the location of an error page, anyway?).
Location meta tags can only be associated with nodes, and user profiles.

Before upgrading to the latest security version I had the ability to set geo location to taxonomy terms. I had set up a taxonomy for 'towns' which was populated with local town names. Each of the towns in my county was given a geo location. That option has now gone and so has the data.

I'm relatively new to Drupal but isn't a taxonomy term a node? As such it did seem very logical to use the geourls in the format above.

I'd like to define a global geolocation for the complete site as in past.

I'm relatively new to Drupal but isn't a taxonomy term a node?

Taxonomy terms are not nodes; taxonomy terms are associated to nodes, but are not nodes.

agree with hass #7, I have been looking for the geo tag which was in the past release.
I figured the issue would come up soon enough. I use them for local business sites that have only anonymous users. I suppose the new way is to add them in the page.tpl file or am i missing something.

See comment #1.

I am marking this report as fixed as it has already gotten an answer.

There seems still no global setting restored and #1 does not answer this.

Should the location be allowed also for the taxonomy terms, and vocabularies? I think that somebody could like to set the location for a vocabulary that is associated to a town.

The code I committed allows to set the location meta tags in all the forms where it is possible to set the value for the meta tags.

I spoke to soon, this is working. There may have been an issue with Boost and/or the cache holding it up from showing in the html code.
This new version of nodewords does have some really neat features. Nodewords has always been a great module, we just have to learn how to use it.