Is there a way, in server level, of forcing each page title (the one shown in the tab title in the browser) to begin with <sitename>:<pageTitle> ?
Is there a way, in server level, of forcing each page title (the one shown in the tab title in the browser) to begin with <sitename>:<pageTitle> ? |
look for: <title>__page_header__</title> in your templates/base/_header.html file. You can add a static title here, ie.: <title>My site: __page_header__</title> caredesign.net |
Sounds promising, but it didn't do the trick... I've emptied the server and the browser's cache after applying the suggested change, but it didn't seem to change anything, page titles remain the same.
Thank you for the effort! Other ideas? |
hmm - it worked on mine - did you clear your dolphin cache caredesign.net |
here are a couple of screenshots of what I have, as I also wanted the same thing you are looking for. THe MTS: is what I have in my _header.html file like so: <title>MTS: __page_header__</title> caredesign.net |
You are right, my mistake! I'm using a custom template, so I needed to apply the change to the _header.html file under that template, not under "base". Works great now, thank you very much for the info. |
i ran into s similar deal where a user had a custom template and had 2 _header.html files. Are the 2 files identical? cause In my custom template on my test site, I do not have a _header.html. Even the alt template doesnt have one - which is what I based my template off of.
In the scenario with the other user, he removed the _header.html file file in the template and everything worked perfectly. With both files, he was having issues, cause the base one would kick in and then the template one would screw things up.
It would be great if someone could clarify about having the 2. caredesign.net |
I've looked into what you said, and the _header file is indeed identical in the base template and the custom one. I've removed the custom one and applied the change in "base"- works just as great. I think I'll have it set back in the custom template folder, as I think it's a general rule to override things in the custom templates/CSS where possible, to avoid issues when upgrading. The custom template also overrides other HTML files in that level (some, not all), but besides _header, _footer and the _sub_header/footer files which are identical to the base files, the others actually change the base settings (like email footer). I didn't have any issues with it so far. |