Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 646 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  67682   Fri Mar 28 14:55:16 2014 Reply David PilgramDavid.Pilgram@epost.org.ukInfoLinux2.9.2-a738Re: A couple of observations
I tried to attach a screenshot showing this, but kept getting a 502 bad gateway error.
The message in the red banner is
Error sending Email via <i>"psquad.psi.ch"</i>
with that html showing, by the way.
> Hi Stefan and Andreas,
> 
> When I submitted the previous entry, I had an error message about not able to send via psxxxx.psi.ch come up as
> a red bar at the top of the elog page - sorry, cannot remember the subdomain name correctly.
> 
> The observations I was going to make is firstly the change in layout of the Find section - maybe I'll get used
> to it but the change in layout wasn't warmly welcomed.
> 
> Also, shame that moving from Subversion means that the increments are no longer in easy numerical order.  So I
> believe that I am commenting on the latest possible version available, a738232.
> 
> A question.  My logbooks directory is now 1.8GB.  Yes, there are a lot of attachments etc to bulk it out, but
> it's all plain text comments.  Is there a limit as to the size, or total number of entries?  Elog takes a
> notible amount of time to index it all these days, and I have wondered whether a couple of "instabilities" might
> be caused by this.  Anyone any thoughts?
> 
> I don't know how I managed it, but I got elog to generate two entries with the identical ID no.  The new entries
> were different as well.  The log file faithfully had recorded the two separate replies to the entry having the
> same ID no as well.   Unfortunately I went and corrected it by editing the YYMMDDa.log file without keeping a
> copy.  I have also had a mysterious entry ID0 appear in threaded display, despite there being no entry 0; and if
> it appears, it appears in two or three places within the list of threaded entries.
  1171   Fri Jun 3 18:11:09 2005 Question Emiliano GabrielliAlberT@SuperAlberT.itInfoWindowslatestRe: 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 Agree Gary Claysonimppster@gmail.comInfoWindowslatestRe: 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 Reply Stefan Rittstefan.ritt@psi.chRequest  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 Reply Stefan Rittstefan.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 Agree Guenter NowakGuenter.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 Reply Stefan Rittstefan.ritt@psi.chRequestAll 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" Tongue


thank you in advance Smile


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 Crying .

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 Reply Emiliano GabrielliAlberT@SuperAlberT.itRequestAll 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" Tongue


thank you in advance Smile


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 Crying .

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 ?
ELOG V3.1.5-3fb85fa6