Closed (fixed)
Project:
Nodewords: D6 Meta Tags
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Issue tags:
Reporter:
Created:
21 Oct 2010 at 22:25 UTC
Updated:
3 Jan 2014 at 02:04 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
dave reidComment #2
dave reidComment #3
dave reidGah, there are additional of cleanups that were necessary with token handling code:
1. Not using the 'global' or 'node' token namespace complicates things unnecessarily.
2. The nodewords_replace_tokens() function that is called by every single meta tag processor still works even if the user has actually disabled the 'Enable tokens' option.
Comment #4
dave reidRerolled patch.
Comment #5
dave reidOne last effort. Noticed that we are using the fracking default meta tags on the front page by default. That is just wacky.
Comment #6
dave reidAlright, I feel really strongly about getting this in before 6.x-1.12 and I've tested this one extensively and fixes a few bugs, so I'm committing to CVS.
http://drupal.org/cvs?commit=444876
Comment #7
pfx commentedAfter updating to the latest development version from the previous I can not find the token [metatags-description] nor [metatags-description-raw] in the list of available tokens ?
In the previous development version these tokens were present and functioning properly ?
....
oops, excuse me, these tokens are absent from the list but their use for the description meta tag works!
sorry
Comment #8
dave reidIf you're using a fairly recent version you should find them under the 'Global' or 'Node' sections.
Comment #9
pfx commentedYes I found the token [metatags-description] under 'Node' section when I edit a page from the tab 'Custom pages meta tags'.
However, this token [metatags-description] is absent from the list 'Replacement pattern' from the tab 'Default meta tags'.
thank you very much
Comment #10
dave reidWhy would you need a node-related token on the default meta tag page? Why not just edit the meta tags on the node itself?
Comment #11
dave reidOh wait, I see what you need. You want a default that applies to all nodes.
Comment #12
pfx commentedYes exactly, I use the token [metatags-description] to automatically populate the meta tag 'Description' for each node.
Maybe it's not a very academic ... I do not know?
thanks
Comment #13
keva commentedThere are a whole lot of tokens that are not available with Nodewords 6.x-1.x-dev (2010-Nov-08).
In previous versions, there were tokens for [metatags-description] (very useful) and more: author, node, cck fields, vocab etc.
These are the only ones I currently have available:
[page-title] The page title.
[user-name] The name of the currently logged in user.
[user-id] The user ID of the currently logged in user.
[user-mail] The email address of the currently logged in user.
[site-url] The URL of the site's front page.
[site-name] The name of the site.
[site-slogan] The slogan of the site.
[site-mission] The optional 'mission' of the site.
[site-mail] The administrative email address for the site.
[site-date-small] The current date in 'small' format. (06/07/2010 - 23:28)
[site-date-yyyy] The current year (four digit)
[site-date-yy] The current year (two digit)
[site-date-month] The current month (full word)
[site-date-mon] The current month (abbreviated)
[site-date-mm] The current month (two digits with leading zeros)
[site-date-m] The current month (one or two digits without leading zeros)
[site-date-ww] The current week (two digits with leading zeros)
[site-date-date] The current date (numeric representation of the day of the week)
[site-date-day] The current day (full word)
[site-date-ddd] The current day (abbreviation)
[site-date-dd] The current day (two digits with leading zeros)
[site-date-d] The current day (one or two digits without leading zeros)
[site-date-raw] The current in UNIX timestamp format (1269441371)
[site-date-since] The current in 'time-since' format. (40 years 3 months)
[current-page-title] The title of the current page.
[current-page-path] The URL alias of the current page.
[current-page-path-raw] The URL alias of the current page. Warning: Token value contains raw user input.
[current-page-url] The URL of the current page.
[current-page-number] The page number of the current page when viewing paged lists.
[metatags-global-keywords-1] The global keywords.
[metatags-global-keywords-2] The global keywords.
[metatags-global-keywords-1-raw] The raw global keywords. Warning: Token value contains raw user input.
[metatags-global-keywords-2-raw] The raw global keywords. Warning: Token value contains raw user input.
Perhaps this should be added to this issue instead?
Comment #14
dave reid@keva: No, we could use more details about what page you're not seeing all the tokens listed? Are you using the latest Token module release?
Comment #15
keva commentedThe token list above is from "Replacement patterns" at admin/content/nodewords/default.
Using Token 6.x-1.15
Comment #16
keva commentedI just noticed that on node/edit, all the tokens are available.
Attached are 2 screenshots showing "Replacement patterns" at node/edit and at admin/content/nodewords/default.
Comment #17
dave reidThis should probably work in the meantime.
Comment #18
dave reidComment #19
keva commentedThanks for the lightening-fast fix. It worked perfectly!
Comment #20
keva commentedComment #21
dave reidCommitted #18 to CVS!
http://drupal.org/cvs?commit=452040
Comment #22
dave reid