Deprecated - Drupal core

I see a couple of niggling issues. In the user module, I can't save the block settings on a per individual basis (admin/blocks works, but not from user/<#>/edit). Also in aggregator, settings for categories don't stick either.

In both cases, the checkbox can be selected, but on save the settings are back to the original. (Drupal HEAD from 20051103.)

c.

CREATE TABLE files (
  fid int(10) unsigned NOT NULL default '0',
  nid int(10) unsigned NOT NULL default '0',
  vid int(10) unsigned NOT NULL default '0',
  filename varchar(255) NOT NULL default '',
  description varchar(255) NOT NULL default '',
  filepath varchar(255) NOT NULL default '',
  filemime varchar(255) NOT NULL default '',
  filesize int(10) unsigned NOT NULL default '0',
  list tinyint(1) unsigned NOT NULL default '0',
  KEY vid (vid),
  KEY fid (fid)
) TYPE=MyISAM;

Sorry if this is the wrong place to post this. I was going to try to post this as a bug, but the profile module doesn't show up on the project list dropdown on the bug post page.

That said, I think I've come across a potential problem in the profile.module distributed with drupal 4.6.3.
// $Id: profile.module,v 1.90.2.2 2005/06/01 04:30:07 unconed Exp $

Briefly stated:

in function_profile_admin_add, a call to profile_validate_form is followed by two more validations designed to prevent duplicate titles and duplicate field names.

in function_profile_admin_edit, there is also a call to profile_validate_form, but afterwards it is NOT followed by the previously mentioned checks for duplicates.

It seems to me (and I'll say now that I'm not an expert), that one could create a new profile field, then go back and edit it, change the title and name to be the same as an already existing field, and the module would try to save it. The actual save might in some cases be prevented at the database level (name is a unique key, but not title), but even so the edit validation should be made to catch this error before it gets that far.

Forgive me if I've interpreted the code incorrectly, or if I should have posted this somewhere else (if so, please let me know where).

Steve

PS: As long as I'm here, does anyone know if the 4.7 version of this module is going to include any additional field types, and if so what ones?

this may be very strange ,I was running drupal 4.6.2 then I have upgraded to 4.6.3.

when I create/delete content or change on configuration the status message ( e.g The configuration options have been saved.) . stay on screen for all the session errors are got appended and status message persist all the session long till I log out.

if i have different changes all these messages are stayed till logout,suppose i have to add user, then I should add new content ,then add term i have 3 message on screen will never disappear till loging-out .

Could anyone provide me with some links or ideas on how to utilize related terms and get those terms to display, ideally with other terms in the category description of nodes

It seems like related terms could be very powerful, but its a little confusing in the documentation how they are actually implemented. Nothing seems to happen in the drupal interface to indicate related terms when I start declaring related terms in a specific vocab and then tag nodes??

Are there php variables to recall related terms in a theme template? (phptemplate ideally or xtemplate)

When i try to reach the page admin/user/configure the system gives the following error:

Fatal error: Only variables can be passed by reference in /var/wwwDrupal/drupal-4.6.3/modules/user.module on line 1293

I use Drupal 4.6.3 on Red Hat Linux 9.0, Apache 2.0.54, Php 5.0.5 .

Using Easyphp1.8 (www.easyphp.org)I don't have this problem.

Anyone has ideas?