Pattern for processing manually-assigned page titles [#689620]

Instead of always having to manually add the site name to overridden page titles it would be very beneficial if there was a field to define a pattern that was used. Here's an example workflow:

Have a node pattern set to "[title-raw] | [site-name]" with the site-name value being "example.com".
You edit a node with the title "green monkey" and override the page title to instead say "blah blah"
The outputted page title changes from "green monkey | example.com" to "blah blah", confusing the user

We should have either have a whole new field for a new pattern or an option to pass the title string for overridden objects through the default filter.

Comments

Comment #1

damienmckenna

TN, USA

commented 19 January 2010 at 20:34

As mentioned in #654758: The pattern overwrite the custom title, should the overridden titles also be processed for tokens? Is there a reason why I can't set the title for a node to "something about [site-name]" and expect it to process the token?

Comment #2

nicholasthompson

English

commented 20 January 2010 at 12:21

I'll test this - but the token template is wrong for starters... it should be:
[page-title] | [site-name]

And the correct behaviour for your example (node title = green monkey, page title = blah blah) should be:
blah blah | example.com

Comment #3

damienmckenna

TN, USA

commented 20 January 2010 at 14:24

So how would you handle this scenario:

By default, if you leave a vocabulary to use "[page-title] | [site-name]" as the pattern the titles will show as "Taxonomy term | example.com"
To get the desired default the vocabulary's pattern is set to "[cat] | [site-name]".
When an override is set it should use "[page-title] | [site-name]".