Deprecated - Drupal core

According to module development docs, a module's node type(s) should be prefixed by the module's name followed by a dash. For instance, MyModule's node should be called: "Cookbook-ingredient". Unfortunately, since a node's type is limited to 16 characters, a comprimise has to be made when naming node types with longs names, so we're stuck with "Cookbook-ingred" or renaming the module to, say, "CookBk" or "CBook" or something more obscure l just to allow for more room for the node type name.

I'm trying to change my Drupal mailiing list subscriptions to a new e-mail address and the mailman software is failing with a file permission error. Same error occurs whether changing settings, or trying to subscribe a new address. Here's an example:

I ran into a confusing issue... it turns out that I have two accounts at drupal.org, one called oc and the other called oc@drupal.org. I don't know how this happened; I probably set up the account twice. I tried to delete the extra account and to my amazement, Drupal won't let me! I noticed that this functionality was added and then removed, see: http://drupal.org/node/8 .

I think this is a pretty basic feature, but I also recognize that there is a problem. If you somehow gain access to someone's Drupal password you can delete their account, which would not be good.

Of course you could require email confirmation. But that wouldn't work because an unauthorized person could easily change the email address associated with a Drupal account before clicking the delete button, and then use that email address to confirm the deletion. Of couse that would be less anonymous, and you could more easily discover the hacker.

But a much better way would be provide a "security question" when the user first logs in. New users would be prompted that they would need to answer that question correctly in order to delete their own account. It should be done by adding a couple of fields to the user record, namely the question (mothers' maiden name, last 4 digits of drivers license, pets name), and the answer. This info could not be seen by a user.

Then Drupal could provide a 4th tab in the "My Account" menu item for users, to allow them to do enter the security info and click on confirm.

I am happy to introduce the first test version of this. You may download it from http://cvs.drupal.org/viewcvs/contributions/sandbox/chx/. Alter table implementation will come from http://code.jenseng.com/db/ but I've not made it yet. The database is based upon the latest database.mysql.

Let me post menu.module suggestion. Let's say that is defined a vocabulary containing many terms. The terms may be assigned to an article but many of them not assigned, they are ofphans. In 4.5 Drupal we genarate menu tree based on the vocabulary. Menu will consist of many item linking to empty page. It's possible to enable or disable item manually but when someone assigns article to the corresponding taxonomy item it should toggle it.

Hi,

I am on Drupal 4.5.0 and PostgreSQL 7.4.6

I had to add c.format column to GROUP BY clause in line 776 of comment.module to avoid Postgress error messages:

Errors were:

user error: query: SELECT c.cid, c.pid, c.nid, c.subject, c.comment, c.format, c.timestamp, c.name, c.mail, c.homepage, u.uid, u.name AS registered_name, u.picture, u.data, c.score, c.users FROM drpl_comments c INNER JOIN drpl_users u ON c.uid = u.uid WHERE c.cid = 139 AND c.status = 0 GROUP BY c.cid, c.pid, c.nid, c.subject, c.comment, c.timestamp, c.name, c.mail, u.picture, c.homepage, u.uid, u.name, u.picture, u.data, c.score, c.users in .../includes/database.pgsql.inc on line 121.

warning: pg_query(): Query failed: ERROR: column "c.format" must appear in the GROUP BY clause or be used in an aggregate function in .../includes/database.pgsql.inc on line 104.

It was:

$result = db_query('SELECT c.cid, c.pid, c.nid, c.subject, c.comment, c.format, c.timestamp, c.name, c.mail, c.homepage, u.uid, u.name AS registered_name, u.picture, u.data, c.score, c.users FROM {comments} c INNER JOIN {users} u ON c.uid = u.uid WHERE c.cid = %d AND c.status = 0 GROUP BY c.cid, c.pid, c.nid, c.subject, c.comment, c.timestamp, c.name, c.mail, u.picture, c.homepage, u.uid, u.name, u.picture, u.data, c.score, c.users', $cid);

After the fix:

$result = db_query('SELECT c.cid, c.pid, c.nid, c.subject, c.comment, c.format, c.timestamp, c.name, c.mail, c.homepage, u.uid, u.name AS registered_name, u.picture, u.data, c.score, c.users FROM {comments} c INNER JOIN {users} u ON c.uid = u.uid WHERE c.cid = %d AND c.status = 0 GROUP BY c.cid, c.pid, c.nid, c.subject, c.comment, c.format, c.timestamp, c.name, c.mail, u.picture, c.homepage, u.uid, u.name, u.picture, u.data, c.score, c.users', $cid);