title displays custom [tag] when $form['page_title'] is populated

I'm not entering a token in the Page Title field on the node form.

Page Title default settings (Default Pattern): [mycustomtag]
node form Page Title field: 'I want this text to replace the custom tag.'

When I try this the title shows as '[mycustomtag]', but I'm not sure why. When the field on the node form is blank the title shows the custom tag as expected. The problem only occurs when text is input into the node form field.

Basically the field in the node form only overrides [page-title], I'd like to be able to choose a different token to override instead. Maybe this should be a feature request?

Many thanks

If you create your own module which implements the token hooks and is in either the global or the node scope then you can declare your OWN [mycustomtag] which can be used in the default pattern...

That is exactly what I'm doing. But as I specified [mycustomtag] in the defaults, this is the tag I want to override to change the html page title.

I should just overwrite [page-title] in my module instead of creating a custom tag I think.

Sorry for wasting your time.

If I use either [page-title] or [longname] in the admin/content/page_title/settings defaults they display correctly, but neither gets overridden by text entered in the page-title field on the node form. I understand that this field only overrides [page-title] so there's no reason why it should change [longname].

Here's the code I'm using to create the tokens.

function general_page_token_values($type, $object = NULL, $options = array()) {
  if($type == 'node') { // if I change the scope to global I get Array due to array_merge in tokens (see below)
    $node = $object;
    
  	$masternode = hotel_master_object($object->hotel_id);
      $tokens['page-title'] = $masternode->hotel_long_name;  // this line is preventing the page title field on the node edit page from working with node scope
      $tokens['longname'] = $masternode->hotel_long_name;
    
    return $tokens;
  }
}

I think the problems are caused by different token scopes, the use of array_merge in the tokens module and possibly the module weight in the system table. I've created a support request against tokens #304333: How can I overwrite [page-title] from my custom module? re the array_merge issue, maybe a patch for tokens is necessary to overwrite the duplicates instead of merge them?

I just want to be able to overwrite [page-title] with for all nodes, and override [page-title] for a specific node using the field on the node form - drupal should be able to handle this.

Nicholas, can I discuss this with you on IRC? What time of day are you around (UTC)?

Thanks

Thank for taking the time to discuss this, I appreciate that you're busy.

I played with the weights but that didn't change anything.

I'd started hacking both page-title and tokens which isn't a good idea so I decided to leave tokens alone and make my own custom version of page-title that does what I need it to do. It's not a large module so the maintenance should be minimal.

Page-title, as it stands, is a great module - it's just that my requirements for it are obscure.

Many thanks for your help.

I didn't want another field, I wanted to use the page-title field but for a different token.

I already had another token that contained the value I wanted to use, my original thinking was to use that token but when I realised that would 'go against the grain' I decided to use [page-title]. I thought it would be as simple as [page-title] = [mytoken], unfortunately not.

The conversation has spawned another thought though... I might implement a "hook_page_title_alter" where other modules can be written to modify the page title after is generated. I might even create an earlier hook so that other modules can DEFINE their page title.

That sounds like the sort of functionality I'm after, especially the second part.

If you're interested I can show you my custom page-title module.