Closed (fixed)
Project:
Nodewords: D6 Meta Tags
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
21 Oct 2010 at 12:39 UTC
Updated:
4 Aug 2021 at 09:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
dave reidI'm fine with them staying separate since it's a bridge between two modules rather than simply adding title support in nodewords.
Comment #2
dave reidWell, I reconsider. Taking a look at the page title module and it duplicates a lot of the context handling that we already do in nodewords. The only thing is we have to do a little bit of special casing since the page title has its own variable in template_preprocess_page separate from $variables['head'].
Comment #3
dave reidComment #4
dave reidSo yeah, this completely obsoletes the page_title and nodewords_pagetitle module when nodewords is in use. And was ridiculously easy to implement.
Comment #5
dave reidWe should probably target 6.x-1.13 for this so we can get a chance to discuss with the nodewords_pagetitle maintainers.
Comment #6
Brian294 commentedThanks for keeping me in the loop Dave on this recent development. You're right, implementing page titles into nodewords natively is ridiculously easy, that's why I wrote nodewords_pagetitle with just a few lines of code!
I'll get back with you soon once I have a chance to review the patch.
Peace,
Brian
Comment #7
robbertnl commentedGreat patch. I can confirm this patch works. I am looking forward this patch is included in the new release
Comment #8
Liam Mitchell commentedApplied patch and working fine so far. Will update if I encounter problems.
Thanks
Comment #9
pfx commentedI tested the patch and it worked well for me. Thanks for the patch.
Comment #10
damienmckennaWill review.
Comment #11
hanoiiQuestion: Are you saying with this we can just not use page_title and achieve the same results on any page? or is it the nodewords_pagetitle bridge that's not necessary?
Comment #12
hanoii>> Provide a description for this "forum overview page"??
Was that description on purpose?
>> "It is generally accepted this field should be less than 70 characters."
I recently found this: http://www.hugoguzman.com/2010/05/dont-believe-the-hype-google-does-full...
Just thought of pointing this out.
Other than that, tested the patch and it's working great, and I think I can answer #11, which is that page_title is not really needed any more, Am I right?
Powered by Dreditor.
Comment #13
robbertnl commentedI am only missing the sitename in the title. So i changed the patch a little bit in nodewords.module:
From:
To:
Maybe this is not the best place and there should be an option to select if you want the sitename included in the the title
Comment #14
hanoii@robbertnl: No need for an option, you can use tokens on the title metatag as with any other tag. So, you could have:
[title] | [site-name], that works, I am using it.
I don't remember the site-name token exactly so it may be slightly different.
Comment #15
robbertnl commentedI guess that should work but then i have to edit all pages and add the [site-name] token
Comment #16
hanoiiIsn't there a default setting where you can put the token?
Comment #17
robbertnl commentedYes there is but i have titles that are slightly different compared to the page title. SO i cant use the 'title' token
Comment #18
mrfelton commentedThis doesn't completely replace the page_titles module does it? You can't set the default page titles on a per content type basis as you could with the page_title mosule
Comment #19
mrfelton commentedAlso, how about providing a migration path from the page_title module?
Comment #20
nevets commentedLooking at #13 I would not expect this module to call drupal_set_title($pagetitle), since I believe that also changes the viewable title.
Comment #21
dave reidBumping to 6.x-1.13. We really, really need to get a 6.x-1.12 release out before adding any more new features.
Comment #22
damienmckennaDe-tagging, will review priorities after the next stable release.
Comment #23
damienmckennaThis needs to be rerolled for the current codebase.
Comment #24
damienmckennaA new patch with several improvements - there's now an option to automatically append the site name (with an optional divider), and I updated the docs accordingly.
Comment #25
damienmckennaForgot to bump the API version listed in the main module.
Comment #26
damienmckennaBTW when this is committed the Nodewords_PageTitle module should be marked as obsolete (which would also solve #1301972: Deprecate Nodewords_PageTitle).
Comment #27
damienmckennaCommitted!
Comment #28
damienmckennaA follow-up patch for a permission reference that was missing from the tag definition.
Comment #29
damienmckennaAnother follow-on, renaming the 'title' value as 'page_title', to avoid any possible conflict with any other possible meta tags.
Comment #30
damienmckennaThis time *with* the patch. #facepalm.
Comment #31
damienmckennaI've committed the last patch, the 'title' field has now been renamed to the 'page_title' field and the field labels updated accordingly.
Comment #32
damienmckennaOne final follow-on patch from the last, the API version of nodewords_basic needed to be bumped to accommodate the new page title meta tag.
Comment #33
hanoiismall note: nodewords-n948342-32.patch is the same as nodewords-n948342-29.patch
Anyway, I think I found another follow-on patch, the preprocess variable should be head_title instead of page_title as per the default garland theme and probably most themes.
Comment #34
hanoiiI guess it's now a bug as this is already a feature.
Comment #35
hanoiiSorry, fixed patch.
Comment #36
damienmckennaThanks for catching that, I've committed it.
Comment #38
summit commentedHi,
Set this to active again, because I think a small think was missing from this port.
I used nodewords_pagetitle with tokens support for page title, description, keywords in custom pages.
This somehow is not working anymore with 1.x and 2.x Nodewords including this nodewords_pagetitle port.
Greetings,
Martijn
Comment #39
summit commentedHi seeing this issue for token support http://drupal.org/node/1380362
So setting this to closed fixed then, right?
Looking forward to token support on 6.1.x!
greetings, Martijn
Comment #40
damienmckenna