| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1269
|
Thu Jul 14 17:34:12 2005 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | | Re: short/long_name should point the same user |
| Emiliano Gabrielli wrote: | In my case I changed it by error, people inserted entries and now I restored the correct one .. so now I have to unlock the attribute and change every Author by hand as admin
 |
Well, that teaches you not to do this error again  |
|
1270
|
Thu Jul 14 19:11:54 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Bug report | All | | Re: short/long_name should point the same user |
| Stefan Ritt wrote: |
| Emiliano Gabrielli wrote: | In my case I changed it by error, people inserted entries and now I restored the correct one .. so now I have to unlock the attribute and change every Author by hand as admin
|
Well, that teaches you not to do this error again |
uhm.. I think the confusion intrinsict in elog between long and short name is something to be solved ..
an attribute of type "userlist" fills always with the long_name .. but if I would to insert it as short ?
the users shown in the users admin dropdown menu is short .. why? .. may be I didnt understood the way this issue works ..  |
|
1272
|
Thu Jul 14 20:24:07 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | | Re: short/long_name should point the same user |
| Emiliano Gabrielli wrote: | uhm.. I think the confusion intrinsict in elog between long and short name is something to be solved ..
an attribute of type "userlist" fills always with the long_name .. but if I would to insert it as short ?
the users shown in the users admin dropdown menu is short .. why? .. may be I didnt understood the way this issue works .. |
The "short name" is the equivalent to the unix login name. Under /etc/passwd, you have a login (short) name and a "full" (long) name. The first may not contain blanks, must be unique, while the second is more like a "real" name. This concept has been adapted in elog. While many people use cryptic or abbreviated login names, it's still nice know the real name, like if you get an email notification from someone. The userlist fills with the long_name because people refer to other people in the logbook usually with the real name (sometimes they even don't know the people's login name). The admin dropdown menu uses the short names because you look at the user database more from an administration point of view. Like if you edit /etc/passwd, you first look at the login name, not the full one. Maybe what one could add is to make the full name in the admin page a dropdown list as well, so the admin can either select the short or the long name. Another item for the wishlist |
|
1273
|
Fri Jul 15 15:03:01 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Bug report | All | | Re: short/long_name should point the same user |
| Stefan Ritt wrote: |
| Emiliano Gabrielli wrote: | uhm.. I think the confusion intrinsict in elog between long and short name is something to be solved ..
an attribute of type "userlist" fills always with the long_name .. but if I would to insert it as short ?
the users shown in the users admin dropdown menu is short .. why? .. may be I didnt understood the way this issue works .. |
The "short name" is the equivalent to the unix login name. Under /etc/passwd, you have a login (short) name and a "full" (long) name. The first may not contain blanks, must be unique, while the second is more like a "real" name. This concept has been adapted in elog. While many people use cryptic or abbreviated login names, it's still nice know the real name, like if you get an email notification from someone. The userlist fills with the long_name because people refer to other people in the logbook usually with the real name (sometimes they even don't know the people's login name). The admin dropdown menu uses the short names because you look at the user database more from an administration point of view. Like if you edit /etc/passwd, you first look at the login name, not the full one. Maybe what one could add is to make the full name in the admin page a dropdown list as well, so the admin can either select the short or the long name. Another item for the wishlist |
uhmm .. what I am talking about is something simpler ... It seems to me that elog does not use always the "login name" but somethins refers to the "gecos" ... What I'm askinf for is to separe the login name (to which elog has to refer for everything internally) and the long/short_name mechanism that should be a mere display issue ...
May be that it is the same to ask for the introdution of a "user_id" or to treat the login name as the uid, .. the "Author" field should be filled both with the long and the short name (and it is so now!) but, when checking the original author on a Edit action, aelog as to check always the actual logged *short* name against the original Author *short* name .. becoise is only the short name that should have a sense for messages .. the long one is only a nice reminder
Hope my english makes me to be understod now |
|
1277
|
Mon Jul 18 10:16:35 2005 |
 | Emiliano Gabrielli | AlberT@SuperAlberT.it | Bug report | Linux | rev 1.703 | Display Subject and HTML tags, regression |
rev 1.703 makes the following code not to work:
Display Subject = <b>$subject</b>
the <b> tag is displayed and not interpreted, as it was in previous revisions.. |
|
1278
|
Mon Jul 18 18:36:32 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Bug report | Linux | rev 1.703 | Re: Display Subject and HTML tags, regression |
| Emiliano Gabrielli wrote: | rev 1.703 makes the following code not to work:
Display Subject = <b>$subject</b>
the <b> tag is displayed and not interpreted, as it was in previous revisions.. |
this patch should fix the problem .. a little bug still remain, if you insert some allowed HTML tags in the subject this is detected by is_html() so the Display Attribute and the Link is not applied .. the result is that the HTML is working but no elog featur is applied |
|
1285
|
Wed Jul 20 21:43:56 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | | Re: [code] should be a sort of <CDATA > |
| Emiliano Gabrielli wrote: | Using the [code] elocode should be intended also to preserve the tagged text from beeing parsed as html or elcode itself ..
this is an example:
| Quote: | Note that, for security reasons, you should check the MD5 FINGERPRINT of the SSL certificate issued by the server agaist the following one:
MD5 Fingerprint = 23:A7:AD:33:3C:08:BE:2A:62:6E:85:DF:B8:00:23:40
Thank you |
|
As you can see, your entry with the [code] section is now shown without interpretation. So everything between [code] and [/code] is not interpreted as ELCode tags. The modification is committed to CVS. |
|
1286
|
Wed Jul 20 22:28:14 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | rev 1.703 | Re: Display Subject and HTML tags, regression |
| Emiliano Gabrielli wrote: | rev 1.703 makes the following code not to work:
Display Subject = <b>$subject</b>
the <b> tag is displayed and not interpreted, as it was in previous revisions.. |
rev. 1.707 makes it work again  |