Closed (works as designed)
Project:
Featured Content
Version:
6.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
26 Nov 2011 at 19:52 UTC
Updated:
11 Jan 2026 at 23:40 UTC
Jump to comment: Most recent
Comments
Comment #1
kristen polUnfortunately no tokens are handled but that is a good idea... I'm not sure how easy that would be since you could select multiple authors. Perhaps I need to create my own tokens like:
fc-users
fc-content-types
fc-terms
etc.
I'll think about this but they need to be specific to the block... so really it would probably need the block number in it like fc-6-users or something similar.
Kristen
Comment #2
kristen polJust an update that I won't have time to look into any feature requests until February at the earliest as I just started writing a Drupal book on a compressed timeline.
Thanks for your patience,
Kristen
Comment #3
kristen polGetting back to the queue... I don't think this will make sense for the block title because you won't know who the author is (each node might be a different author).
If someone wants to pursue this, let me know if you want to be a co-maintainer. Thanks!
Comment #4
sayansk commentedНа моем сайте около сотни организаций, которые должны иметь собственное меню. С помощью вашего модуля мне удалось это реализовать. Каждая организация группируется с помощью терминов таксономии. Очень хорошо было бы, если бы в заголовке меню у каждой организации было одноименное название термина. Однако tokens [term:name], как впрочем и все остальные, не работают. Ругается на "invalid tokens..."
Comment #5
kristen polGoing through old items... the text above roughly translates (via Google Translate) to:
"On my site about a hundred organizations that need to have their own menu. With your module I managed to implement it. Each organization is grouped with the help of taxonomy terms. Very nice it would be if the title menu each organization had the same name of the term. However, tokens [term: name], as well, and all the rest, do not work. Swears on "invalid tokens ..."
This appears to be a different issue altogether but the idea of supporting tokens is interesting and would need to be a separate ticket. The context for the token would need to be the node though so the example above ([term: name]) wouldn't work.
Comment #6
kristen polcleaning up my issues list