Deprecated - Drupal core

Sometimes people would like to maintain a private blog.
It would be great if that feature could be enable.

Should be simple, I guess.

I'm customizing a Drupal installation to use it as an ecommerce site. We have to make as easy as possible the buying process: imagine a person who arrives to the site, browse through the available products and decides to buy something. After he clicks "add to cart" adn then "checkout", he must register himself in the system, but this is a task which interferes seriously with the chekout process, as he has to change application in order to get the password to be able to login and then continue with the checkout. Also the system election of the password is a drawback in user terms, as he is faced with an additional task (change password) which he might forget to do.

I'm sure this must have been disussed here previously, but my question is if it wouldn't be useful to provide a configuration option for the user module in which you let decide the site admin about:

- letting users chosing his own passwords
- automatic login after registration

These two things would be one only option, as you are not going to do an automatic login if the user hasn't chosen his own password.

Our opinion is to face problems when they appear, but not make difficult the user experience when it can be easier. The advantage of forcing the users to check their emails in order to get their password is to check that they are who they say they are, but this is not needed in most registrations. At least, let the admin decide when to do that check.

Hello everyone,

After a new node is inserted or an existing node is updated, node.module calls drupal_goto.
I want my still-to-be-written 'nextstep' module to be able to manipulate the destination that Drupal redirects to.

Although I only quickly looked through the attachment.module ( as an example ) and node.module,
I think there's currently no clean way to do this. Am I correct ?

Earlier today I installed the quotes module and I noticed in the instructions it says:

NOTE: Use of Drupal's cache (in "site configuration") is discouraged as a static quote will be cached, and anonymous users will not see a random quote. It will only be updated when a logged-in user makes a change that invalidates the cache. If you have any ideas on getting around this limitation, please let me know.

I was wondering if anybody had looked into the idea of having a caching system like XOOPS. I've used XOOPS in the past and it's a great CMS, just not for every scenario, which is why I'm trying out Drupal (which has been mostly great to me thus far). The XOOPS caching system lets you turn caching on/off for different modules and it also lets you set a timer on how long before the cache will automatically regenerate itself (on the next hit to the site after the time has expired).

Does any one have any tips on tools and procedures for reverse engineering Drupal? It has become very tiresome and time wasting to hunt through thousands of lines of code looking for abstract variables and objects.

Right now I am trying to use Zend Studio to run debugging to find errors. But even Zend Studio has problems with the way some parts of the core are written.

The documentation still lacks a definative explaination of how the core engine works and how to use it. I have recently read up on the the Zend engine core and found it easier to understand.

Should I use taxonomy/term/ or should I use taxnomy/page/or/ for url alias?