Couldn't see this in the issues queue.

Not sure if it is just me, but I could not find anywhere in the admin settings of the dev version that allowed the update of the following site variable "nodewords_first_keywords".

The closest I could find was "Global keywords - first group:" which has a new variable "nodewords_global_keywords_1" not seen in older versions. This was not updated during the update.

I have had to manually delete the "nodewords_first_keywords" from the site as it was still being used to generate the keyword meta tag. In addition any keywords I enter into "nodewords_global_keywords_1" are not being included in the keyword list. Before I look into fixing this and issuing a patch I just wanted to ensure that I was correct in how this should work?

Comments

jonathan_hunt’s picture

I also found the nodewords_global_keywords_1 token not being populated, so not appearing via Page Title module. That's because the nodewords_tokens_token_values() is matching on the incorrect variable name, AFAIK.

Index: nodewords/nodewords_tokens/nodewords_tokens.module
===================================================================
--- nodewords/nodewords_tokens/nodewords_tokens.module	(revision 19439)
+++ nodewords/nodewords_tokens/nodewords_tokens.module	(working copy)
@@ -188,11 +188,11 @@
 
   switch ($type) {
     case 'global':
-      $value = nodewords_unique_values(variable_get('metatags_extra_global_keywords_1', ''));
+      $value = nodewords_unique_values(variable_get('nodewords_global_keywords_1', ''));
       $values['metatags-global-keywords-1-raw'] = $value;
       $values['metatags-global-keywords-1'] = check_plain($value);
 
-      $value = nodewords_unique_values(variable_get('metatags_extra_global_keywords_2', ''));
+      $value = nodewords_unique_values(variable_get('nodewords_global_keywords_2', ''));
       $values['metatags-global-keywords-2-raw'] = $value;
       $values['metatags-global-keywords-2'] = check_plain($value);

dave reid’s picture

Status: Active » Fixed

Looks like this has already been addressed in the latest code.

Status: Fixed » Closed (fixed)

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