Module development and code questions

Is it possible to create a secondary links menu from within a module?

I don't see a way to access this from hook_menu

What I'd like to do is to create a secondary menu at runtime.

I've tried putting something like this in the callback of my module display page

hi folks,

i am somewhat new to drupal but i am familiar with all the modules that are available. i have literally spent hours reading through all the modules and what each provides. saying that, drupal is somewhat seo friendly, but it could be better. there are two modules title and keywords that work on seo efforts but nothing beyond that (correct me if i am wrong).

Hello all.

HI,

when i open the /blog/feed page in drupal, i get an error thats says :

url : http://www.infostand.net/blog/feed

-----------
XML parsing failed: syntax error (Line: 3, Character: 0)

Reparse document as HTML
1:
2:
3: <?xml version="1.0" encoding="utf-8"?>
4: ]>
5:
6:
------------

this is the output from the opera browser. In IE it works fine but IE is ignoring the first empty lines.

I just wondered if anyone has any examples they want to share of using the excellent category.module?

I've obviously seen the tutorial on greenash, but wondered if anyone out there wants to share alternate navigation set-ups, or even their own tutorials. I'm just trying to get more of a feel for it and to see even further its potential.

I'm trying to get my head around the full process drupal uses regarding making nodes safe for display and whether there are any changes in 4.7 regarding this. I did a quick search and could not find this decision tree written out, so I thought I'd take a quick stab. Can anyone double-check that this sounds correct:

The process begins with node.module’s node_view making the following decision: If the node type’s module has a hook_view, let the module handle any filtering. Otherwise node.module will pass the body or teaser through node_prepare.

If we are using a hook_view, the module should first call node_prepare on the body / teaser. Then the module will pass it on to the theme. An example from forum.module’s forum_view:

$node = node_prepare($node, $teaser);
$node->body .= theme('forum_topic_navigation', $node);

This would suggest that the theme should not have to worry about making user-supplied content safe, but it appears that the general practice for custom content fields is to filter them in the theme function. On reason for this might be the l() function, which seems to filter the title of the link. If we were to filter all content at the hook_view level, things might get double-encoded[1]. However, in theory this opens the door for site admins and theme developers to overlook these calls to check_plain or l() while overwriting the theme function in their theme.