Deprecated - Drupal core

Hi,

I'm having a difficult time figuring out exactly what happens when a form is submitted to Drupal. For example, on the edit account page, the form attribute action="/?q=user/edit". I assume this leads to a function call that builds a user object from the post parameters and updates the database. Where is this code? How is this explained generally? What combinations of ?q=object/action are there? Is there documentation on this somewhere that I've overlooked? Thanks for any info! The sooner I get a grip on all this the sooner I can start contributing code.

Problem: Using webserver_auth to automatically login a user authenticated externally via the webserver (and presented to Drupal with $REMOTE_USER set). However, watchdog is showing content being accessed by user "anonymous." Why?

Shouldn't the webserver_auth module always ensure someone is logged in? This is not a problem for most people accessing content but is a problem if someone wants to add a comment to a node (they are asked to login).

The only node in which webserver_auth works (aligns externally authenticated id with drupal id) is via the home page for the site. If user clicks a node url in an email invoking a new browser session the webserver's external authentication method is invoked but webserver_auth is not aligning external id with a drupal id.

Background: Webserver_auth aligns an external webserver session with a drupal id using authmap. $REMOTE_USER is queried in authmap which results in the drupal id being returned (or creates one if it does not exist).

Analysis:

When using webserver_auth a non-persistent session cookie is used. It expires upon termination of the browser. This is a good thing because you only want access granted via the webserver authentication and not a persistent session cookie from drupal.

Webserver_auth is invoked via an "init" hook, using module_init(). This hook is only invoked in common.inc. Apparently, an "init" hook is only sent when the default home page is referenced. When accessing other nodes an "init" hook is never invoked.

Should the "init" hook always be invoked? For all nodes?

Possible fixes:
Ensure "init" hook is always invoked, for all nodes.
Use persistent cookies (not preferred).

I am running a multilanguage drupal site with cyrillic (russian), german and english content and had permanent problems with cyrillic characters.

I upgraded to Drupal 4.4.1 (from 4.3.x), and all is well.

Great job guys.

However, I have the following problems that are bugging me. They are not show stoppers by any means, but they are inconsistent and annoying.

- When creating nodes of type 'book', the aliases are ignored in the navigation.
This means that the navigation will point to book/view/xxxx and not mycustomurl.html

I filed a bug report here: http://drupal.org/node/view/7867

Is there any facility to allow for users to vote for features, or fixes, to allow the wider community to asynchronously contribute to defining what is targetted in future versions of drupal? If not, would it help the team working on core, and/or provide useful feedback to modules/theme residing in the contributions tree?

hi.

i have started working on making a patch to add the following functionality:

1) add a "make node into block" checkbox to the options section of a node add/edit form
2) when this box is checked certain configurable fields from the node are placed into the boxes table and the node shows up in the blocks configuration page
3) you can then add a block with the contents of the node (or truncated contents) in it and you can weight it and it behaves like any other custom block.

while i have not delved this deep into drupal coding before, i have though a lot about it and have come up with some pseudo code that i think, illustrates how this could work.