Token is not replaced for custom pages

strange..

i tried out a couple of more things and noticed that even when explicitly specifying the canonical url in the custom meta tag section, the custom value is ignored

so on that same food-and-dining page i've entered "food-and-dining" in the canonical field. i've confirmed that it is saved in the database.. but when viewing the page source i see the same as above (should i open a new issue for this)

<link rel="canonical" href="http://omaha.net/%5Bmetatags-url-alias%5D" />

another thing i noticed is that i can't actually delete these custom page settings.. i click delete and get confirmation that "My configuration options have been saved" - but the entry is still in my list of custom pages and still in my database

lastly regarding tracker pages.. it gets even wierder.. the token is properly expanded on user tracker pages with URLs like (token IS expanded):
user/100/track/navigation

but not on node tracker pages with URLs like (token NOT expanded):
node/796/track

thanks for working on this so fast.. unfortunately something is still not working

this is what i'm still seeing on pages i've created with panels

<link rel="canonical" href="http://omaha.net/%5Bmetatags-url-alias%5D" />
<meta name="keywords" content="[metatags-taxonomy-keywords]" />
<meta name="description" content="[metatags-description]" />

any ideas?

I've now got my front page tags displaying properly thanks to your clarification. But all other pages created with panels are still printing the tag itself rather than the value of the tag for description and keywords.

No pressure, but just wondering where this is on your list of priorities? I need to make a determination about which version to go with.

thanks!

Do you have panels installed? If you do I think you should be able to recreate this by creating a page with panels and then try to add custom meta tag settings for that page.

I'm really not seeing any sign that the custom pages meta tags is working

are you planning on supporting pages created with panels??

this is a crucial issue for me and I would imagine many users for this module.. there seem to be a lot of people having trouble with tokens not printing on custom pages

okay - this is very crude.. but could be the start of support for panels pages - its working for me right now with the current dev release

function _nodewords_detect_type_and_id() {
  $arg = arg();

  if (variable_get('site_offline', 0) && !user_access('administer site configuration')) {
    return array('type' => NODEWORDS_TYPE_OFFLINE, 'id' => 0);
  }
  // **** start new code ****
  // check if this is a panels page
  $page = page_manager_get_current_page();
  if ($page) { 
    // is the panel page path in nodewords_custom table ?
    // try to get pid
    $id = db_result(db_query_range(
      'SELECT pid FROM {nodewords_custom} WHERE path = "%s"', $page['subtask']['admin path'], 0, 1
    ));
  if ($id) {
    return array('type' => NODEWORDS_TYPE_PAGE, 'id' => $id);
  }
}
// **** end new code ****

  $headers = drupal_get_headers();

for the specific case of a page generated by views i still can't get any meta tags to appear

the change in #16 helps a bit in that this no longer appears:

<link rel="canonical" href="http://omaha.net/%5Bmetatags-url-alias%5D" />
<meta name="keywords" content="[metatags-taxonomy-keywords]" />
<meta name="description" content="[metatags-description]" />

yay and thanks!

but with this fix, when i create a custom page for a views page meta tags still do not appear

Cool - that solves part of the problem.

Any new ideas why the module can't "understand" that a page was created by views and to add meta tags when a custom page has been created?