| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1171
|
Fri Jun 3 18:11:09 2005 |
 | Emiliano Gabrielli | AlberT@SuperAlberT.it | Info | Windows | latest | Re: A comprehensive listing of all commands elog performs |
| Gary Clayson wrote: | Can someone please enter a comprehensive list of the commands eLog will honor. I'm trying to build a 'decent' start page and am not totally familiar with eLog just yet. Thanks Stefan for an awesome application. The documentation is really decent, too. I just have been unable to locate a list of all commands available.
Thanks in advance.
Gary ;-> |
there's a link in the main elog web page.. it's under the Admin guide and it is the elog.cfg syntax guide |
|
1233
|
Thu Jul 7 04:49:19 2005 |
 | Gary Clayson | imppster@gmail.com | Info | Windows | latest | Re: A comprehensive listing of all commands elog performs |
| Emiliano Gabrielli wrote: |
| Gary Clayson wrote: | Can someone please enter a comprehensive list of the commands eLog will honor. I'm trying to build a 'decent' start page and am not totally familiar with eLog just yet. Thanks Stefan for an awesome application. The documentation is really decent, too. I just have been unable to locate a list of all commands available.
Thanks in advance.
Gary ;-> |
there's a link in the main elog web page.. it's under the Admin guide and it is the elog.cfg syntax guide |
thanks for the advice. DuH on me, I just needed to read the syntax page a little more closely. |
|
328
|
Wed May 7 21:15:57 2003 |
 | Stefan Ritt | stefan.ritt@psi.ch | Request | | | Re: A NAME=... tags around the attachments | > it would be useful, if the web server automatically produced tags <A NAME=
> [AttachNo3]>Anhang 3</A> around the entry of the attachment. With this one
> could easily reference in the HTML text an attachement at the end of the
> page.
I added a name tag <A NAME=attx> where x is 1,2,3,... to the attachments
(->CVS). So you reference them by "/<logbook>/<id>#attx" where x is the
attachment number, <id> the message ID (the one displayed in the URL if you
display a single message) and <logbook> is the logbook name.
> I had a problem, when I just put a HTML text with <IMG> tags into the
> formular box and I could not reference them although they were available
> (and displayed pictures) as attachments.
That won't work, since attachments are preceeded by the date/time, to avoid
name collisions if two identical file names are submitted several times. You
see that if you click on an attachment to display only that picture. The URL
in the browser gives you the full URL including the date/time, which you
have to use to reference that image. This is of course not possible if you
are just submitting an entry, since you don't know which exact time the URL
will get. So you first have to submit the message with the attachment, the
lookup the attachment URL, then edit the message again and enter the full
URL. Not very handy, I know, but right now the only way. |
|
638
|
Fri Jul 30 09:15:39 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | | | | Re: ?cmd=New&pType=PC does not work | > according to the users guide,
>
> http://midas.psi.ch/elogs/Database/?cmd=New&pType=PC
>
> should create an entry with the type value set to PC, but this doesn't work
Now it works. Updated elog version under CVS and as a snapshot (see Download Page) |
|
639
|
Fri Jul 30 12:26:10 2004 |
| Guenter Nowak | Guenter.Nowqak@t-systems.at | | | | Re: ?cmd=New&pType=PC does not work | > according to the users guide,
>
> http://midas.psi.ch/elogs/Database/?cmd=New&pType=PC
>
> should create an entry with the type value set to PC, but this doesn't work
Thanks! |
|
1256
|
Mon Jul 11 13:13:27 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | | Re: < img > in Display Attribute |
| Emiliano Gabrielli wrote: | Still a problem .. sorry:
Options Category = Info,Report,Problem{1},Other
Preset Category = Info
Display Category = <img style="border:0; float:left; margin-right:5px" src="icons/$category.png">$category
{1}ROptions Level = Notice,Warning,Alert,Fixed
{1}Preset Level = Warning
{1}Display Level = <img style="border:0; float:left; margin-right:5px" src="icons/$level.png">$level
when I try to use this featur on a conditional attr it is ignored .. If I remove the {1} it is obviously showed .. but also when no $level is defined (taht is infact not what should be)...
BTW, is it possible to not show conditional attributes in mail and in "single entry" view? .. it's quite strange to ave a "Level" of a "Misure", not a "Problem" 
thank you in advance  |
Well, that's not the way condition attributes are supposed to work. They were designed to modify the new entry input mask, to have diefferent option lists depending on the value of an attribute. But conditional attributes do not have any meaning for normal display and for email notification. This would have to be implemented and is quite some work. So I would put following in your config:
Options Category = Info{1},Report{1},Problem{2},Other{1}
Preset Category = Info
Display Category = <img style="border:0; float:left; margin-right:5px" src="icons/$category.png">$category
{1}ROptions Level = Notice,Warning,Alert,Fixed
{1}Preset Level = Warning
{1}Display Level = <img style="border:0; float:left; margin-right:5px" src="icons/$level.png">$level
{2}Preset Level = N/A
Having N/A is not as nice as having this attribute not shown at all, but that's the only choice one has right now  .
Another thing: you maybe realized that putting <img> in the subject of your orignal entry results in a missing image. That's a nasty side effect of your wish to have any <img> interpreted as HTML. Of course you could argue that <img> is not a real HTML statement because the source is missing, but then another one will come and put there a subject like: "I want an <img src="bla.gif"> in my config" and bang, we are back to the same problem. So if anyone has a clever idea of how to solve this, please let me know. Maybe one should be able to put a "\" in front of any code (also the ELCode tags) to not interprete them by the system. But while this is maybe obvious for a C programmer or shell programmer, the normal user might not find this so obvious. |
|
1257
|
Mon Jul 11 14:30:11 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Request | All | | Re: < img > in Display Attribute |
| Stefan Ritt wrote: |
| Emiliano Gabrielli wrote: | Still a problem .. sorry:
Options Category = Info,Report,Problem{1},Other
Preset Category = Info
Display Category = <img style="border:0; float:left; margin-right:5px" src="icons/$category.png">$category
{1}ROptions Level = Notice,Warning,Alert,Fixed
{1}Preset Level = Warning
{1}Display Level = <img style="border:0; float:left; margin-right:5px" src="icons/$level.png">$level
when I try to use this featur on a conditional attr it is ignored .. If I remove the {1} it is obviously showed .. but also when no $level is defined (taht is infact not what should be)...
BTW, is it possible to not show conditional attributes in mail and in "single entry" view? .. it's quite strange to ave a "Level" of a "Misure", not a "Problem"
thank you in advance |
Well, that's not the way condition attributes are supposed to work. They were designed to modify the new entry input mask, to have diefferent option lists depending on the value of an attribute. But conditional attributes do not have any meaning for normal display and for email notification. This would have to be implemented and is quite some work. So I would put following in your config:
Options Category = Info{1},Report{1},Problem{2},Other{1}
Preset Category = Info
Display Category = <img style="border:0; float:left; margin-right:5px" src="icons/$category.png">$category
{1}ROptions Level = Notice,Warning,Alert,Fixed
{1}Preset Level = Warning
{1}Display Level = <img style="border:0; float:left; margin-right:5px" src="icons/$level.png">$level
{2}Preset Level = N/A
Having N/A is not as nice as having this attribute not shown at all, but that's the only choice one has right now .
Another thing: you maybe realized that putting <img> in the subject of your orignal entry results in a missing image. That's a nasty side effect of your wish to have any <img> interpreted as HTML. Of course you could argue that <img> is not a real HTML statement because the source is missing, but then another one will come and put there a subject like: "I want an <img src="bla.gif"> in my config" and bang, we are back to the same problem. So if anyone has a clever idea of how to solve this, please let me know. Maybe one should be able to put a "\" in front of any code (also the ELCode tags) to not interprete them by the system. But while this is maybe obvious for a C programmer or shell programmer, the normal user might not find this so obvious. |
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 ? |
|
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 |
|