Deprecated - Usability feedback

anybody knows why taxonomy terms are not indexing in vendor searchengines?
and why "path"s are not showing instead of full url?
thanx in advance

I have several suggestions on enhancing Drupal security, but wanted to post to the discussion before making a feature request to see if there's a broader base of interest. I believe some of these ideas are already under way, but I'm still new here so I'm not sure.

1) Taxonomy User Roles? In commercial products I use it's possible to setup a hierarchy of user roles, each level inheriting the permissions of it's parent. Subsequently additional filters may be placed on the child level. Having this hierarchy of roles in Drupal would be very nice, and it seems that extending the Taxonomy concept to apply to user roles could do this.

2) Allow multiple roles for a single user. I think this is already under development. Rational is simply to reduce the number of roles that need to be defined to support various combinations of user permissions.

3) Node level security rules. It would be nice to control who has access to nodes by defining which roles have access to a node and it's children. That would allow the implementation of public and private spaces within a single Drupal application.

4) role based HTML filtering rules. I already requested this (http://drupal.org/node/view/5408). The idea is to allow different levels of HTML usage to users based on user roles. Thus, administrators could post content with virtually no restriction, while public users could be limited to simple layout tags.

I've been finding that the way we can implement theme("box") doesn't allow for the best semantic markup of section titles. Specifically, it only gives us the ability to give the $subject of a box one type of wrapper, e.g. <b> or <h2> or whatever you indicate in your theme -- I reserve <h1> for the site title, by the way. It would be nice if we were able to indicate that a $subject should be an h2, h3, etc. in our specific modules. What I'm wanting is for the titles of pages to have a higher heading, e.g. h2, so that subordinate sections of pages can then use the default box with h3 or whatever heading you pass in the box function.

For instance, say I modify the box function in my theme:

function box($subject, $content, $region = "main", $headtype = "null") {
  if ($headtype == "null") {
    print "<b>$subject</b><br />\n";
  } else {
    print "<$headtype>$subject</$headtype>\n";   
  }
  print $content;
  print "<br />\n";
}

Then I can change all my modules so that the _page functions put out the title of the page with an h2 tag, e.g.

theme("box", t("User account"), user_menu(), "", "h2");

and all other boxes, e.g. blocks and lower level boxes can use a lower level heading or bold tags or something. This is what I'm doing on this new blog I'm playing with and it seems to give me better page headings across the site. Any opinions on this issue?

Does anyone know how to change the code in the weblink module so that the title of the link becomes a link as well.

I know there's a link at the bottom of each node saying visit "link name" but if the titles were links as well it would be more user friendly.

I'm using drupal now for a couple of weeks at multiple domains (using 1 installation with multiple config files). It works very well, but I'm missing a feature to use a shared database for users, image galleries etc. and using a domain specific database for things like static pages, stories etc.

In this case users have ro register at one of the domains and are able to login with the same information at the other domains, they can use one large image gallery to avoid the same image uploaded several times (and using disk space), but all domains do have their own content.

In the process of translating drupal, I ran into this odd thing. It seems to me that the below mentioned text (copied from localise module) is redundant in two of the places. Is this neccesary?

Create a new user account.
/drupal/

Create new account
/drupal/?q=user/edit

Create new user account
/drupal/?q=user