| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
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  |
|
1274
|
Fri Jul 15 17:28:33 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Request | All | | Re: < img > in Display Attribute | the very usefull thing my request will enable is the following:
Options Category = Info,Report,[B]Problem[I]{1}[/I][/B],Other
Preset Category = Info
Display Category = <img style="border:0; float:left; margin-right:5px" src="icons/$category.png">$category
[B]{1}[/B]ROptions Level = Notice,Warning,Alert,Fixed
{1}Preset Level = Warning
[B]{1}Display[/B] Category = <img style="border:0; float:left; margin-right:5px" src="icons/[B]$level[/B].png">[B]$category[/B]
note that this way I could use a single field to have the both the category name and the level icon .. this is specially usefull for a "problem" or "bug" category, becouse this way one can see status of the "bug"..
.. I'd really like conditional Display  |
|
1275
|
Sat Jul 16 12:30:33 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | | Re: < img > in Display Attribute |
| Emiliano Gabrielli wrote: | IMHO the solution may be in allowing html code only in the cfg, not in the value of the field..
i.e., elog has to first allow html in the cfg attribute and then replace every $attribute with their values... this values as to be translated in html entities in order to solve the problem
in other wordsthe value of the attribute as to httl_encoded when displayed.. and the cfg line not
or I am loosing some point ? |
I don't like that solution. Sometimes I want to write some HTML tag myself into an attribute (like "<b>") and have this interpreted, meaning having the following word in bold, and sometimes I want to talk about HTML tags, like to tell you to use <b> for bold, and have it not interpreted. The same with the ELCode tags.
So I added an escape character. If you write <b> or [b], then it gets interpreted. If you write \<b> or \[b] with the "\" in front of the tag, it does not get interpreted, thus the '\' works like an escape character. I edited your old entry with the <img> in the subject, and as you see it is now not interpreted.
The modification is in CVS and documented in the ELCode help. |
|
1276
|
Mon Jul 18 10:09:06 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Request | All | | Re: < img > in Display Attribute |
| Stefan Ritt wrote: | I added an escape character. If you write <b> or [b], then it gets interpreted. If you write \<b> or \[b] with the "\" in front of the tag, it does not get interpreted, thus the '\' works like an escape character. I edited your old entry with the <img> in the subject, and as you see it is now not interpreted.
The modification is in CVS and documented in the ELCode help. |
Ok, it's a good solution for me ... as using a <pre> html tag does not seem to preserve an <img> tag .. |
|
1281
|
Wed Jul 20 20:13:26 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.5.4-3 | Re: Cannot stat() config file |
| Stefan Rudat wrote: | | Cannot stat() config file; No such file or directory. |
I do not know what exactly is going on. This error occurs during runtime when elog tries to check if the config file (usually elogd.cfg) has changed. It checks if the file is there on startup, but apparently it is there, otherwise elog would not start. Then it checks about once per second if the file access time has changed. If so, it rereads the file. This way changes to the file become valid immediately, without restarting elog. The fact that elog has access to the file on startup, but not later, is somehow strange. Maybe you lock this file with an editor, or it is on a network drive which gets disconnected, or the permission changed after the startup. Something in that direction. |
|
1282
|
Wed Jul 20 20:54:01 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.5.9-2 | Re: Omitting some fields in e-mail | > E.g, if you have the following:
> Attributes = TA, Endret, UA, Pri, Status, Oppdragsgiver, EpostTil, EpostIKT, Tittel
>
> Then you get the heading:
> Logbook :
> TA :
> Endret :
> UA :
> Pri :
> Status :
> Oppdragsgiver :
> EpostTil :
> EpostIKT :
> Tittel :
>
> (removed the attribute data),
>
> But I would like to send out only:
> UA :
> Pri :
> Status :
> Oppdragsgiver :
> EpostTil :
> Tittel :
>
> Any way to do this in the current version?
>
> And perhaps change the order too... I'm asking for much perhaps?
I added the option "Email attributes = <list>" for that. So you can specify
Email attributes = UA, Pri, Status, Oppdragsgiver, EpostTil, Tittel
which also sets the order of the attributes. The cange is in CVS. |
|
1283
|
Wed Jul 20 21:03:29 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug fix | Linux | 2.5.9 | Re: elog utility for submission used wrong 'Host:' in POST header |
| Emiliano Gabrielli wrote: | This is not completally true IMHO .. better, it is, but it is not the only problem.
Elog seems to speak HTML/1.0, where "host:" is not implemented ... Since ELOG does not support Vhosts I think the right beaviour is to remove the "Host:" header at all ... |
So I remove the Host: ... line at all, I hope this is ok with everybody. |
|
1284
|
Wed Jul 20 21:13:03 2005 |
| Michael Husbyn | michaelh@online.no | Question | Linux | 2.5.9-2 | Re: Omitting some fields in e-mail |
> I added the option "Email attributes = <list>" for that. So you can specify
>
> Email attributes = UA, Pri, Status, Oppdragsgiver, EpostTil, Tittel
>
> which also sets the order of the attributes. The cange is in CVS.
Nice!
Thanks Stefan, I will test it when I'm back from my holiday. Only problem is that this change is also in a
beta version of elog (more "beta" than usual)
Perhaps it is not in this state when I'm back :)
have a nice holiday
Best regards
Michael |
|