Deprecated - Drupal core

Hello:

When a user clicks www.example.com/node/23, I want to make it instead load www.example.com/node/23/12 where 12 is the very first comment of node 23. How can I achieve this? Any directional help is appreciated, thanks.

please email me at troypayne[at]gmail(dot)com to be alerted of an answer if possible.

Drupal won't send email! It either says that it sent the email but it never does, or it says it couldn't send to the email address.

Garland theme for Drupal 5 Beta 2 not flexible as Blumarine. When I resize my windows the content will stay and not flowing like the water in a balloon. This is a biggest mistake in Drupal 5 Beta 2.

Can anyone say:

What calls theme_user_pass() in user.module?

I ask, because I want to write a function to display a reasonably lengthy text message, similar to the theme_user_pass() function which displays the text:

Enter your username or your e-mail address.

... In the request password form at: user/password

I would like to similarly display a message above the Username field in: user/register

Thanks

How can I get full drupal output to postprocess it with my custom function.
I could'n find information about this.

I've got my first real Drupal site working, and I like the way that I can add functionality through the use of hooks. Getting the hang of this, I've begun to use the same method to communicate between my own custom modules, which nicely cuts down on the interdependency between these.

However, currently there is no control over which hooks "fire" - every module gets to fire its hooks. Yes you can undo some of the results with hook_form_alter but (in 4.7) there is no hook_view_alter. This leads to some oddities, like:

(1) Turning taxonomy terms into checkboxes (see e.g. http://drupal.org/node/84286) has to wait until taxonomy has done hook_nodeapi as usual, then write over it.

(2) user.module writes a "History" section to the user view page on hook_user('view'). There's no way to undo this, without hacking user.module, or writing a theme for the page.

(3) ecommerce tries to allow everything to be a pseudo-product. Every time a node is loaded it uses hook_nodeapi to do a SELECT from ec_product just in case it might be a pseudo-product, wasting db calls. I don't use pseudo-products, yet I can't turn it off without hacking ecommerce.

So a proposal:

Could Drupal core include some sort of "meta hook" (hook_hook()?), whose purpose is to allow modules to control the hooks that reach other modules? Or even a permissions system for hooks? Of course turning off hooks selectively could be dangerous, but then so is any new module...