Deprecated - Usability feedback

Using: Drupal 4.7.2
Theme: chameleon (costum)
Level of Drupal knowledge: very basic

I need to have a costum block to be displayed in side-right-bar in a 3-col, layout, BUT only in some sub nodes.
This will be used as a submenu, but aside from the main navigation, that only appers when enterd to specific nodes, that are of type PAGE.
Could I do this with a PHP snipplet or something, help anybody.
SMAP (Save My A** Please)

Thanks in forehand...

Can anyone give me a hand with the views module. I cannot get my title (that starts with a date, 2006/06/31, for an example of the format) to sort properly in a view. I simply want the most recent date to appear at the top of the list. The alphabetical sort in 4.7 makes a mess of this. Any ideas? I may be missing something rather simple-- but in 4.6 I could do this rather easily by sorting on title. Now the behavior of the views module has apparently changed. Any suggestions would be appreciated!

I am trying to figure out the easiest way to build a Drupal powered site containing of a set of "pages", each containing multiple dynamic or static "objects".

definitions:
I guess what I call an "object" is close to a Drupal "node" (a piece of text or html, an image, a set of images, one or more downloadable files (contained in a nice box), a comment area etc etc).
A "page" consist of some kind of design template together with the actual content specific to the "page" (probably located somewhere in the middle). I want several of these "objects" or "nodes" to be coexisting on the main part of each "page".

I have only a few hours experience with Drupal (been installing and playing with a lot of modules to grasp what's possible without too much coding of my own).

For example I guess it would be possible to create a container-node which upon creation/instantiation would allow me to choose and/or create a few child-nodes (normal drupal nodes) to be displayed side by side when the container-node is accessed by the visitor. Is there such a node already? I tried category (not very easy to understand), flexinode (too simple/restricting), views (didn't find anywhere to f.e enter node id:s, other than as url arguments....) and others without finding what I'm looking for...

Another way would be the php snippets claiming to be able to display several nodes when inserted into a page node as "php code". Can't get these to work though, maybe because:

Real people are lazy. Thats what too many designers think. They think that people should take the time to read everything and work their way through stuff methodically.

Well people are not lazy, just goal oriented and sometimes they miss stuff.

Hands up everyone who has a Community site where you know that people have failed to turn on their Personal Contact and are wondering why no one talks to them. They didn't notice the box.

This is not a rant.

Drupal rocks.

However, in order to shed the stigma of being targeted only at super-geeks, everybody agrees that the documentation needs some serious upgrading.

I have what I think is a simple suggestion that may go a long way towards removing the stigma: when any code snippet is shown, or any other similar action step, there should be two cross-references in the description immediately after (or before) the item in question:

1) pre-requisites

2) insert location

I could argue that the first should be a link, and that after a suitable set of links is established, inserting such a link would become trivial, but until a satisfactory set of links is established, an inline list would satisfy.

As an example, here is a link to a description of how to add a custom element from the "Forms API Quickstart Guide", found at:

http://drupaldocs.org/api/head/file/contributions/docs/developer/topics/...

Begin Quote:

For example, here's how to go about constructing a textfield form element:

$form['foo'] = array(
  '#type' => 'textfield',
  '#title' => t('bar'),
  '#default_value' => $object['foo'],
  '#size' => 60,
  '#maxlength' => 64,
  '#description' => t('baz'),
);

End Quote

I defy anybody who is not intimately familiar with Drupal to understand where this snippet is to be placed. Further, on the page, there is nowhere that indicates the version of Drupal that the Forms API being referenced applies to. Those who follow the versioning of Drupal may know that the Forms API is not available to versions of Drupal prior to a certain specific version. Those that don't may be confused. Why should they be confused when it is so easy to ensure that their confusion is eliminated?

How can i do this:
I want add to my drupal 4.7 a second administer user, who can manage users, but can't see and can't modify first (uid=1) administer user's password and email address. Is this possible?