Roundup Tracker - Issues

Issue 994394

classification
mail dependent on realname
Type: rfe Severity: normal
Components: None Versions:
process
Status: closed out of date
:
: : jpend, jruh, marlonvdb, richard
Priority: normal :

Created on 2004-07-20 09:33 by anonymous, last changed 2007-10-12 17:37 by jpend.

Messages
msg3335 Author: [hidden] (anonymous) Date: 2004-07-20 09:33
File mailgw.py refers to the realname of a user. If no 
realname is specified (for example I have specified 
Forename and Surname) the mailgw cannot handle 
changes in the issues.
Issuer: J.Ruh@gmx.de
msg3336 Author: [hidden] (marlonvdb) Date: 2004-07-20 17:44
Logged In: YES 
user_id=1080231

The mail gateway requires the realname to make the mail 
more personal. If you split the name in forename and 
surename, it's best to keep the realname property in the user 
class next to the sure and forename, but remove the 
realname from the user.item.htm template. Then write a 
simple user class auditor that takes the content of newvalues
['forename'] and newvalues['surename'] and place it in 
newvalues['realname'].
msg3337 Author: [hidden] (anonymous) Date: 2004-07-23 08:36
Logged In: NO 

I have done that as a work around. I have written a small 
detector, which automatically forms a realname out of 
forename and surname (so no realname entry is necessary). 
But I have not seen any documentation which specifies that 
the realname is mandatory in the user class. This should be 
added (in best case generate the property "realname" 
automatically, no dbinit.py entry).
msg3338 Author: [hidden] (marlonvdb) Date: 2004-07-23 08:51
Logged In: YES 
user_id=1080231

You're right on that one, it's no where in the documentation. 
There are more such properties which are needed, but not 
saying it anywhere (don't try to remove the author prop from 
the msg class). It would indeed be nice if there would be a 
remark about these properties somewhere in the 
documentatin or as comment in the dbinit.py file. Or maybe 
even better, roundup to define new base classes for 
UserClass, and so on... The base classes must contain all 
required fields (and so can not be removed by us). In 
dbutils.py we that inherrit the base class and add our own 
properties.

Regards,
Marlon
msg3339 Author: [hidden] (jruh) Date: 2004-07-23 09:03
Logged In: YES 
user_id=1089647

That would be a good approach i think.
msg3340 Author: [hidden] (richard) Date: 2004-10-08 05:54
Logged In: YES 
user_id=6405

Have added some documentation. 
 
Re-filing as a feature request. 
 
msg3341 Author: [hidden] (jpend) Date: 2007-10-12 17:37
I don't think this is valid any longer. If realname isn't set, roundup will user the userid instead. I've tested in on my tracker here at work and it sent mail just fine when I removed my realname. If there are other places that are dependent on the realname being set we can file new bugs for those.
History
Date User Action Args
2004-07-20 09:33:24anonymouscreate