ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 647 of 808

Not logged in

Find | Login | Help

Full | Summary | Threaded | Collapse | Expand

6457 Entries

Goto page Previous 1, 2, 3 ... 646, 647, 648 ... 806, 807, 808 Next

Re: < img > in Display Attribute, posted by Stefan Ritt on Sat Jul 16 12:30:33 2005

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 "") 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 for bold, and have it not interpreted. The same with the ELCode tags.

So I added an escape character. If you write or [b], then it gets interpreted. If you write \ 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.

Re: < img > in Display Attribute, posted by Emiliano Gabrielli on Mon Jul 18 10:09:06 2005

Stefan Ritt wrote:

I added an escape character. If you write or [b], then it gets interpreted. If you write \ 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 ..

Re: < img > in Display Attribute, posted by Stefan Ritt on Wed Jul 20 23:30:45 2005

Emiliano Gabrielli wrote:

the very usefull thing my request will enable is the following:

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 Category           = <img style="border:0; float:left; margin-right:5px" src="icons/$level.png">$category

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 Tongue

You asked for ELCode tags not to be interpreted inside any [code] tag, but now the above entry gets screwed since you used it there! So no formatting any more in [code] section Wink

Re: < img > in Display Attribute, posted by Emiliano Gabrielli on Thu Jul 21 09:31:35 2005

Stefan Ritt wrote:

Emiliano Gabrielli wrote:

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]

You asked for ELCode tags not to be interpreted inside any [code] tag, but now the above entry gets screwed since you used it there! So no formatting any more in [code] section Wink

LOL

Re: 80 column Message width., posted by Stefan Ritt on Mon Jan 21 15:08:19 2008

Carl Shirey wrote:

First thing we have been using the Elog for 2 yr for a shift carryover and it has works out great.

Now for the problem I have. I heave the message width set to 80. It works for plain Encoding but it does not work for HTML or ELCode. The text does not wrap around when viewing using Explorer or Fire Fox or printing out the Elog. Is this a problem or do I need to modify the Config file?

Thanks

A limited message width does not make sense for HTML or ELCode encoding since the text is laid out by the browser dynamically when displaying messages. For example have a look at this very message in your browser, and resize your window. You will see that the text flows dynamically, so the line breaks move with the window size. Furthermore the text entry uses a variable width font, so a fixed line length would not result in line breaks at the same vertical position. Therefore the message entry size scales automatically with the browser window. If you need lines with fixed length, you can only do that in plain encoding.

Re: 80 column Message width., posted by Stefan Ritt on Mon Jan 21 15:33:22 2008

Carl Shirey wrote:

That is the the problem the text does not resize with the window or sending to the printer.

As I told you, if you need that feature, stick to plain encoding.

Re: 5.5.4 cannot decode AUTH parameter, posted by Stefan Ritt on Fri Nov 21 16:09:37 2014

harish amin wrote:

Dear Team,

I am having a log book and would like to activate the email notification. I have made the changes as per the guidelines but I am getting the error message while submitting the entry - Error sending Email via "smtp.omantel.net.om": 5.5.4 cannot decode AUTH parameter

The details are as below : (Please note I have replaced the password with the * marks)

21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} NEW entry #0

21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} Email from <harish.amin@holiday.co.om> to harish.amin@holiday.co.om, SMTP host smtp.omantel.net.om

21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} 220 fmgw1.omantel.net.om ESMTP Smtpd; Fri, 21 Nov 2014 15:32:52 +0400

21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT}

21-Nov-2014 16:58:28 [harish@127.0.0.1] {SCREENING VISIT} EHLO localhost

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-fmgw1.omantel.net.om Hello [188.66.222.72], pleased to meet you

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-ENHANCEDSTATUSCODES

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-PIPELINING

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-8BITMIME

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-SIZE 32235520

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-DSN

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-AUTH LOGIN PLAIN

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-STARTTLS

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250-DELIVERBY

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} 250 HELP

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} AUTH LOGIN

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} Username

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} harish.amin@holiday.co.om

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} Password

21-Nov-2014 16:58:29 [harish@127.0.0.1] {SCREENING VISIT} ******

21-Nov-2014 16:58:30 [harish@127.0.0.1] {SCREENING VISIT} 501 5.5.4 cannot decode AUTH parameter ******

Please help me to resolve this issue.

Thank you

Harish Amin

For the login to your email sever, the password is encoded in base64 form (actually not really secure). Somehow your server does not support this. Unfortunately I cannot test this without access to your server. But you can try yourself by doing a telnet to your mail server like:

$ telnet <server.domanin> 25

...

$ AUTH PLAIN

With the "plain" method, you should be able to enter your password in plain text (not base64 encoded), and see if that works. If you are successful, I can add this option to elog.

Best,

Stefan

Re: 5.5.4 cannot decode AUTH parameter, posted by harish amin on Fri Nov 21 17:00:09 2014