Deprecated - Drupal core

There are some enhancements I'd like to see in path.module, mostly to support the pathauto module (but some generally useful as well).

1. The newest version of pathauto in HEAD allows users to have aliases automatically replaced when editing content. Since there is no way to tell whether an existing alias was manually entered or generated by pathauto, there's a risk of blowing away manual aliases (which I believe should, ideally, never be touched by pathauto). I would like to add a flag to url_alias to indicate whether a given alias was entered manually (in a node form or the url aliases settings) or generated automatically by pathauto, so pathauto can leave the manual ones alone.

2. The path module allows multiple aliases for one page, but provides no way for the administrator to choose which is the "favored" one (the one returned by drupal_get_path_alias(). The ease with which pathauto can create multiple aliases makes this issue more apparent. I would like to add a flag to url_alias to indicate that a given dst is the "primary" alias for src. The nodeapi hook would display all aliases for a given node (currently only one is shown, regardless of how many there are) with a radio button to choose which one should be primary.

3. Replacing an existing alias breaks old links/bookmarks to the original alias. Adding a new alias to a page with an existing alias may hurt the page's search engine rankings, minimally by dividing incoming links and potentially by giving the appearance of spamming (some unsavory webmasters will give the same content many addresses to try to flood search engine results). I would like to see every alias that isn't the primary alias (see #2 above) respond with a 301 - Moved Permanently status code and redirect to the primary alias. Or, more flexibly, add a response field to url_alias which potentially could support other responses (such as 410 Gone for content that has been deleted).

I really like the distributed authorization of the Drupal system. But it does raise a security issue for me. It seems that it would be trivial for a malevolent web owner to hack the drupal script so that he can collect my username and password. usually this wouldn't be a problem. However, with the drupal system, if I login using my normal account from my own Drupal website username and password he could then log into my website and have full privileges of my account.

I hope this is the right place ot post this. If not, I appologise for my transgression.

I picked Drupal for my next site.
So far it looks great, supposed to do what I need as far as features etc.

Problem is I can't get forums to work like they should. Yes, there are several bug reports on this.
There are many many forum posts on this problem. Lots of users are crying for help on this issue.

Personally it's holding up deployment of my site. I considered installed 4.5.x but really 4.6 seems like a huge leap forward and I'd rather start here.

So to this end, I'd like to try and come up with a solution. I'm not a php or sql brainiac. But I can make changes, do some logical deduction and with some assistance perhaps we can solve this problem.

So here's my observations.
Forums seem to not work with taxonomy. When you list forums, none of the terms or vocabulary with forums enabled show up in the forums list.
I think this might be the problem right here:

/**
* Returns the vocabulary id for forum navigation.
*/
function _forum_get_vid() {
$vid = variable_get('forum_nav_vocabulary', '');
if (empty($vid)) {
// Check to see if a forum vocabulary exists
$vid = db_result(db_query("SELECT vid FROM {vocabulary} WHERE module='%s'", 'forum'));
if (!$vid) {
$vocabulary = taxonomy_save_vocabulary(array('name' => 'Forums', 'multiple' => 0, 'required' => 1, 'hierarchy' => 1, 'relations' => 0, 'module' => 'forum', 'nodes' => array('forum')));

A small question: when I was running Drupal CVS (before the official release of 4.6) the administer>>categories page had some rather nice formatting that highlighted the vocabularies so that they were more easily distinguished from their terms. Somewhere along the way, the formatting disappeared and with the official 4.6 taxonomy.module, the vocabs do not have distinct formatting. I liked that feature. Although I'm not sure if it's still there-- maybe I tampered with that part of my theme?

Hi,

I am new to drupal and need to get the following done..
Don't seem to be able to find any direct answers to tehse questions so that I can get started.

I need to create my on database of customer records using MySql, how and where can I create these tables in drupal?
Once there created how do I query them?
Last how can I print the fields retrieved?

Than you very much

David.