Hi Ivan,<br><br>I just looked over your post really quickly. But that quick glance makes me think you are need of one or both of the following modules in addition to nodewords:<br><br><div style="margin-left: 40px;"><a href="http://drupal.org/project/nodewords_bypath">http://drupal.org/project/nodewords_bypath</a><br>
<a href="http://drupal.org/project/nodewords_nodetype">http://drupal.org/project/nodewords_nodetype</a><br></div><br>best,<br><br>Shai<br><a href="http://content2zero.com">content2zero</a><br><br><div class="gmail_quote">
On Fri, Jan 2, 2009 at 9:17 AM, Ivan Sergio Borgonovo <span dir="ltr"><<a href="mailto:mail@webthatworks.it">mail@webthatworks.it</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>
<br>
The actual problem is providing an API to let modules add META in a<br>
more structured way so that eg. the same META is not sent 2 times or<br>
module can decide to concatenate further meta or define a<br>
"owerwriteability" level.<br>
<br>
I gave a look to nodewords aka Meta tags but I have stuff that<br>
aren't nodes (they aren't views or taxonomies either) that don't fit<br>
with the node paradigm too well.<br>
<br>
nodewords provide a hook to 'prepare' META but it is on a module<br>
base.<br>
Nodewords needs to be aware of all the content types (or just pages,<br>
menu_hook etc...) it can support (*unless I'm missing something...*)<br>
but actually what know better which are the most suitable meta for a<br>
"content" should be the content producer (be it a "node" or just a<br>
MENU_CALLBACK).<br>
Other modules like nodewords_bypath and _nodetype do some extrawork<br>
to know what actually called the hook.<br>
But I'd find myself more comfortable with a different approach:<br>
- there is a common API that let me manage META<br>
- modules that want to add META use it<br>
- when everything is ready drupal_set_html_head get called<br>
<br>
The problem is:<br>
- the API functions should be ready when other modules call them<br>
- drupal_set_html_head($meta) should be called last<br>
<br>
If the weight of my meta module is high, other modules won't find<br>
the functions.<br>
If the weight of my module is low and I put<br>
drupal_set_html_head($meta) in the menu hook, drupal_set_html_head<br>
will be called before $meta had the chance to be filled by other<br>
modules.<br>
<br>
I'd say this is a general common problem but I didn't find any<br>
"drupalish" way to solve it.<br>
<br>
The easiest (and somehow elegant) way I thought to deal with this<br>
problem was to build up 2 modules with different weight):<br>
- meta_prepare (that will offer the functions)<br>
- meta_deliver (that will simply call drupal_set_html_head)<br>
<br>
Is there a more drupalish way to deal with dependency and "order of<br>
execution" in drupal?<br>
<br>
thanks<br>
<br>
--<br>
Ivan Sergio Borgonovo<br>
<a href="http://www.webthatworks.it" target="_blank">http://www.webthatworks.it</a><br>
<font color="#888888"><br>
--<br>
[ Drupal support list | <a href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a> ]<br>
</font></blockquote></div><br>