Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 194 of 238  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
icon5.gif   <img> in Display Attribute, posted by Emiliano Gabrielli on Fri Jul 8 19:08:30 2005 
My goal is to be able to do the following :

Display Category = $category <img src="icons/$category.png" border="0">


This way one can add a self explaining icon to the attribute or just replaceing it (only in visualization)

Is there another method to accomplish this ? otherwise I's in my wish list Smile
    icon2.gif   Re: <img> in Display Attribute, posted by Stefan Ritt on Fri Jul 8 22:18:01 2005 

Emiliano Gabrielli wrote:
My goal is to be able to do the following :

Display Category              = $category <img src="icons/$category.png" border="0">


This way one can add a self explaining icon to the attribute or just replaceing it (only in visualization)

Is there another method to accomplish this ? otherwise I's in my wish list Smile


Ok, it's implemented in CVS.
       icon2.gif   Re: <img> in Display Attribute, posted by Emiliano Gabrielli on Sat Jul 9 16:06:58 2005 

Stefan Ritt wrote:

Emiliano Gabrielli wrote:
My goal is to be able to do the following :

Display Category              = $category <img src="icons/$category.png" border="0">


This way one can add a self explaining icon to the attribute or just replaceing it (only in visualization)

Is there another method to accomplish this ? otherwise I's in my wish list Smile


Ok, it's implemented in CVS.


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
          icon2.gif   Re: < img > in Display Attribute, posted by Stefan Ritt on Mon Jul 11 13:13:27 2005 

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.
             icon2.gif   Re: < img > in Display Attribute, posted by Emiliano Gabrielli on Mon Jul 11 14:30:11 2005 

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 ?
                icon2.gif   Re: < img > in Display Attribute, posted by Emiliano Gabrielli on Fri Jul 15 17:28:33 2005 
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 Tongue
                   icon2.gif   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
                      icon2.gif   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]

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


LOL Smile
                icon2.gif   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 "<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.
                   icon2.gif   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 <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 ..
          icon2.gif   Re: <img> in Display Attribute, posted by Stefan Ritt on Wed Jul 20 23:32:46 2005 

Emiliano Gabrielli wrote:
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


I added the conditional attributes for the "single entry" view (not the mail yet), so you might again try it.
             icon2.gif   Re: <img> in Display Attribute, posted by Emiliano Gabrielli on Thu Jul 21 12:54:32 2005 

Stefan Ritt wrote:

Emiliano Gabrielli wrote:
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


I added the conditional attributes for the "single entry" view (not the mail yet), so you might again try it.

uhm... it appears a bit strange now..

In the single list:
- only "Author" and "subject" is displayed (text too of course) Crying
- if one edits the entry all fields ar correctly displayed
In full list mode:
- nothing changed, no conditional display is working Crying

revision 1.707 works correctly instead
                icon2.gif   Re: <img> in Display Attribute, posted by Stefan Ritt on Fri Jul 22 23:14:23 2005 

Emiliano Gabrielli wrote:
- only "Author" and "subject" is displayed (text too of course) Crying


That was a bug. I fixed it in CVS.


Emiliano Gabrielli wrote:
In full list mode:
- nothing changed, no conditional display is working Crying


What do you want? In full mode you have a multi-column display of attributes. If you display a different number of attributes for each entry, the table gets screwed up and becomes very hard to read.

BTW: Conditional attributes now also work for email notifications, so you can do for example:
Attributes = Author, Category, Email encoding, Subject
Options Email encoding = plain{1}, HTML{2}
{1} Email encoding = 1
{2} Email encoding = 2
                   icon2.gif   Re: <img> in Display Attribute, posted by Emiliano Gabrielli on Sat Jul 23 16:16:10 2005 

Stefan Ritt wrote:

Emiliano Gabrielli wrote:
- only "Author" and "subject" is displayed (text too of course) Crying


That was a bug. I fixed it in CVS.


Emiliano Gabrielli wrote:
In full list mode:
- nothing changed, no conditional display is working Crying


What do you want? In full mode you have a multi-column display of attributes. If you display a different number of attributes for each entry, the table gets screwed up and becomes very hard to read.

BTW: Conditional attributes now also work for email notifications, so you can do for example:
Attributes = Author, Category, Email encoding, Subject
Options Email encoding = plain{1}, HTML{2}
{1} Email encoding = 1
{2} Email encoding = 2


I don't want to change the number of columns along different rows .. of course Smile
I'd like to be able to do what I explained in elog:1289 ...

not to display or not an attribute, but to be able to choose among different display of an attribute basing the choice on the value of an other attribute

look at my previous post .. I'm trieng to display an icon in the "category" attribute showing the "level" of the "problem", beeing "problem" one of the possible values of the attribute "category" itself
                      icon2.gif   Re: <img> in Display Attribute, posted by Stefan Ritt on Sat Jul 23 18:23:57 2005 

Emiliano Gabrielli wrote:
I'd like to be able to do what I explained in elog:1289 ...


Ok, got it. So I implemented conditional display in the list mode. If that works for you, it was the last wish fulfilled before Christmas! Wink
                         icon2.gif   Re: <img> in Display Attribute, posted by Emiliano Gabrielli on Mon Jul 25 13:29:23 2005 

Stefan Ritt wrote:

Emiliano Gabrielli wrote:
I'd like to be able to do what I explained in elog:1289 ...


Ok, got it. So I implemented conditional display in the list mode. If that works for you, it was the last wish fulfilled before Christmas! Wink


Smile ok now it works .. can I request a simple regression and then shut up untill heaster ?!? Tongue

I think that the conditional view in the Single Entry is not so good (at less in my test case) ..
My scenario should be:
- List View (full,summary,3d):
it's perfect as is now
I have a "Problem" and a "level" attribute, I don't display the level directly but only show an icon in the
field of the category
- Sinlge entry view
In this view It's supposed to go in details .. so I'd like to display both a "Category" (with its icon) *and*
a "Level" (with its own icon too) ...

nowaday in the single view the category can only have the same icon it has in the list view..
donno if a "List Display <Attribute>" could be *the* solution ... having this way the total contol over conditional displaying in every view Smile

btw:
the calendar is at good point Tongue


                            icon2.gif   Re: <img> in Display Attribute, posted by Stefan Ritt on Mon Jul 25 21:29:52 2005 

Emiliano Gabrielli wrote:
donno if a "List Display <Attribute>" could be *the* solution ...


That's a good idea. Unfortunately, "List Display" is already used to specify which attributes to display in list mode. So I changed "Display <attibute>" to "Change <attribute>" and added "List change <attribute>", just to be different from "List display". In principle "List display =" and "List display <attibute> =" can be distinguished by elog, but it could be confusing to have the same option for two different things. The downside is that everybody using "Display <attribute>=" has to change this to "Change <attribute>=".
                               icon2.gif   Re: <img> in Display Attribute, posted by Emiliano Gabrielli on Tue Jul 26 10:45:14 2005 

Stefan Ritt wrote:

Emiliano Gabrielli wrote:
donno if a "List Display <Attribute>" could be *the* solution ...


That's a good idea. Unfortunately, "List Display" is already used to specify which attributes to display in list mode. So I changed "Display <attibute>" to "Change <attribute>" and added "List change <attribute>", just to be different from "List display". In principle "List display =" and "List display <attibute> =" can be distinguished by elog, but it could be confusing to have the same option for two different things. The downside is that everybody using "Display <attribute>=" has to change this to "Change <attribute>=".


It works perfectly now Smile thank you Stefan
                   icon2.gif   Re: <img> in Display Attribute, posted by Emiliano Gabrielli on Sat Jul 23 16:45:28 2005 

Stefan Ritt wrote:

BTW: Conditional attributes now also work for email notifications, so you can do for example:
Attributes = Author, Category, Email encoding, Subject
Options Email encoding = plain{1}, HTML{2}
{1} Email encoding = 1
{2} Email encoding = 2


if one uses ROptions instead of a simple Options the text displaied is "plain{1}" (with the "{1}" not stripped out!!)
                      icon2.gif   Re: <img> in Display Attribute, posted by Stefan Ritt on Sat Jul 23 18:30:57 2005 

Emiliano Gabrielli wrote:
if one uses ROptions instead of a simple Options the text displaied is "plain{1}" (with the "{1}" not stripped out!!)


Ok, fixed.
icon5.gif   Date in CSV and XML in UNIX time, posted by PJ Meyer on Fri Jul 22 03:15:29 2005 
Q: How can dates be exported correctly in CSV and XML?
In windows version I'm getting the Unix seconds since 1970.
XML export:
<DATE>Wed Jun 22 08:29:58 2005</DATE>
<Date_Needed>1119384000</Date_Needed>
<Date_Added>1119470400</Date_Added>

the date record added is good and readable, the two user defined dates are Unix and not real useful in Excel.

Same behavior is the CSV file, the date record added is good, the two user defined dates are Unix seconds.

Now when E-log emails the records all the dates are good - ie readable dates.

So what can be done to make all the dates look like dates?
    icon2.gif   Re: Date in CSV and XML in UNIX time, posted by Stefan Ritt on Fri Jul 22 08:56:20 2005 

PJ Meyer wrote:
So what can be done to make all the dates look like dates?


Simply upgrade to 2.6.0beta where this problem has been solved.
       icon2.gif   Re: Date in CSV and XML in UNIX time, posted by PJ Meyer on Mon Jul 25 19:15:33 2005 

Stefan Ritt wrote:

PJ Meyer wrote:
So what can be done to make all the dates look like dates?


Simply upgrade to 2.6.0beta where this problem has been solved.


I did upgrade to "2.60-beta2" of the Windows binaries - June 16th date stamps on Elog.exe and Elogd.exe.
I'm still getting dates that are in "Unix time"

Anything else?
          icon2.gif   Re: Date in CSV and XML in UNIX time, posted by Stefan Ritt on Mon Jul 25 20:20:18 2005 

PJ Meyer wrote:

Stefan Ritt wrote:

PJ Meyer wrote:
So what can be done to make all the dates look like dates?


Simply upgrade to 2.6.0beta where this problem has been solved.


I did upgrade to "2.60-beta2" of the Windows binaries - June 16th date stamps on Elog.exe and Elogd.exe.
I'm still getting dates that are in "Unix time"

Anything else?


I just tried again myself. Put following into elgod.cfg:

[demo]
Attributes = Author, Category, Arrival
Type Arrival = Date


type in one entry, did a XML extract, and got
<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- ELOGD Version 2.6.0-beta2 export.xml -->
<ELOG_LIST>
	<ENTRY>
		<MID>1</MID>
		<DATE>Fri Jul 22 22:50:34 2005</DATE>
		<Author>sr</Author>
		<Category>Problem</Category>
		<Arrival>7/25/2005</Arrival>
		<TEXT></TEXT>
	</ENTRY>
</ELOG_LIST>

where the date looks ok. So what do you do differently?
             icon2.gif   Re: Date in CSV and XML in UNIX time, posted by PJ Meyer on Mon Jul 25 22:27:06 2005 

Stefan Ritt wrote:

PJ Meyer wrote:

Stefan Ritt wrote:

PJ Meyer wrote:
So what can be done to make all the dates look like dates?


Simply upgrade to 2.6.0beta where this problem has been solved.


I did upgrade to "2.60-beta2" of the Windows binaries - June 16th date stamps on Elog.exe and Elogd.exe.
I'm still getting dates that are in "Unix time"

Anything else?


I just tried again myself. Put following into elgod.cfg:

[demo]
Attributes = Author, Category, Arrival
Type Arrival = Date


type in one entry, did a XML extract, and got
<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- ELOGD Version 2.6.0-beta2 export.xml -->
<ELOG_LIST>
	<ENTRY>
		<MID>1</MID>
		<DATE>Fri Jul 22 22:50:34 2005</DATE>
		<Author>sr</Author>
		<Category>Problem</Category>
		<Arrival>7/25/2005</Arrival>
		<TEXT></TEXT>
	</ENTRY>
</ELOG_LIST>

where the date looks ok. So what do you do differently?



Not sure where we differ....

My cfg:
Attributes = System, Requestor, Title, Priority, Date Needed, Type, Also Notify, Subsystem, Status, Work Order, Assigned To, Team Lead, Percent Complete, Estimated Hrs, Actual Hrs, Date Added, Expected Delivery, Date Completed, Notifications, Completed
Options Priority = A-Emergency{p1}, B-Critical{p2}, C-High{p3}, D-Medium{p4}, E-Low{p5}
Preset Priority = D-Medium
Type Date Needed = Date

XML Extract:
<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- ELOGD Version 2.6.0-beta2 export.xml -->
<ELOG_LIST>

<ENTRY>
<MID>585</MID>
<DATE>Wed Jun 22 08:29:58 2005</DATE>
<System>SDWIS</System>
<Requestor>Other...</Requestor>
<Title>EDI rejects report to George WAUN</Title>
<Priority>B-Critical</Priority>
<Date_Needed>1119384000</Date_Needed>


Q: could it be the spaces in Attribute name????
Or the differences between Linux and Windows ports?
                icon2.gif   Re: Date in CSV and XML in UNIX time, posted by Stefan Ritt on Tue Jul 26 09:25:40 2005 

PJ Meyer wrote:
Q: could it be the spaces in Attribute name????
Or the differences between Linux and Windows ports?


I tried following elogd.cfg:
[global]
port = 8080

[demo]
Attributes = System, Requestor, Title, Priority, Date Needed, Type, Also Notify, Subsystem, Status, Work Order, Assigned To, Team Lead, Percent Complete, Estimated Hrs, Actual Hrs, Date Added, Expected Delivery, Date Completed, Notifications, Completed
Options Priority = A-Emergency{p1}, B-Critical{p2}, C-High{p3}, D-Medium{p4}, E-Low{p5}
Preset Priority = D-Medium
Type Date Needed = Date

and got
<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- ELOGD Version 2.6.0-beta2 export.xml -->
<ELOG_LIST>
	<ENTRY>
		<MID>2</MID>
		<DATE>Tue Jul 26 09:10:33 2005</DATE>
		<System>s</System>
		<Requestor>r</Requestor>
		<Title>t</Title>
		<Priority>D-Medium</Priority>
		<Date_Needed>07/26/05</Date_Needed>
		<Type></Type>
		<Also_Notify></Also_Notify>
		<Subsystem></Subsystem>
		<Status></Status>
		<Work_Order></Work_Order>
		<Assigned_To></Assigned_To>
		<Team_Lead></Team_Lead>
		<Percent_Complete></Percent_Complete>
		<Estimated_Hrs></Estimated_Hrs>
		<Actual_Hrs></Actual_Hrs>
		<Date_Added></Date_Added>
		<Expected_Delivery></Expected_Delivery>
		<Date_Completed></Date_Completed>
		<Notifications></Notifications>
		<Completed></Completed>
		<TEXT></TEXT>
	</ENTRY>
</ELOG_LIST>

So I have the blank in the attribute, and I tried it both under windows and linux. I looked again at the code, and am pretty sure you run an old version. So I made a 2.6.0beta3 windows binaries, with which you could try it again.
icon5.gif   Literal comma in elogd.conf entries where "," is an item separator?, posted by Chris Green on Mon Jul 25 19:24:47 2005 
Hi,

Could you tell me if there is a way to escape characters in elogd.conf? Particularly, I want to have a drop-down "Keyword" attribute where one of the options is "Spelling, grammar and typos.". This invariably gets split into "Spelling" and "grammar and typos". I've tried "\,", ",,", "%," and "%27", to no avail.

Can I get there from here, or do I have to go someplace else?

Thanks,
Chris.
    icon2.gif   Re: Literal comma in elogd.conf entries where "," is an item separator?, posted by Stefan Ritt on Mon Jul 25 20:25:26 2005 

Chris Green wrote:
Could you tell me if there is a way to escape characters in elogd.conf? Particularly, I want to have a drop-down "Keyword" attribute where one of the options is "Spelling, grammar and typos.". This invariably gets split into "Spelling" and "grammar and typos". I've tried "\,", ",,", "%," and "%27", to no avail.


Just put it in quotations, like
Options Keyword = "Spelling, grammar and typos", Other

that will do the job.
       icon2.gif   Re: Literal comma in elogd.conf entries where "," is an item separator?, posted by Chris Green on Mon Jul 25 21:41:00 2005 
Sorry for being dense. Thanks for this,

Chris.
icon1.gif   A new ELOG user wants to register on "127.0.0.1", posted by Emiliano Gabrielli on Thu Jul 14 15:58:07 2005 
A new ELOG user wants to register on "127.0.0.1"


the scenario is:
- elog on localhost
- stunnel on the external interface

I dont want elog to listen on external interface, so.. why do not use the URL cfg attribute for this issue ?
    icon2.gif   Re: A new ELOG user wants to register on "127.0.0.1", posted by Stefan Ritt on Thu Jul 14 17:29:42 2005 

Emiliano Gabrielli wrote:
A new ELOG user wants to register on "127.0.0.1"


the scenario is:
- elog on localhost
- stunnel on the external interface

I dont want elog to listen on external interface, so.. why do not use the URL cfg attribute for this issue ?


You can specify the interface to liste on with the
"-n <interface>"
parameter of elogd.
       icon2.gif   Re: A new ELOG user wants to register on "127.0.0.1", posted by Emiliano Gabrielli on Thu Jul 14 19:16:06 2005 

Stefan Ritt wrote:

Emiliano Gabrielli wrote:
A new ELOG user wants to register on "127.0.0.1"


the scenario is:
- elog on localhost
- stunnel on the external interface

I dont want elog to listen on external interface, so.. why do not use the URL cfg attribute for this issue ?


You can specify the interface to liste on with the
"-n <interface>"
parameter of elogd.


I know Smile

the following is the configuration I'm telling about... and it raises the problem reported
albert@YYYYYYYYY:~$ ps axu | grep elog
elog     22348  1.0  1.9 23660 20408 ?       Ss   11:32   4:54 /usr/sbin/elogd -f /var/run/elogd.pid -c /etc/elog.conf -d /var/lib/elog -s /usr/share/elog -p 8081 -n 127.0.0.1 -x -D
root     22353  0.0  0.2 45436 2276 ?        Ss   11:32   0:17 /usr/sbin/stunnel -o /var/log/elog/elog_daemon.log -p /etc/ssl/certs/stunnel_XXXXXXX.pem -d XXXXXX.roma2.infn.it:8080 -r 127.0.0.1:8081
          icon2.gif   Re: A new ELOG user wants to register on "127.0.0.1", posted by Stefan Ritt on Sat Jul 23 15:46:06 2005 
Ok, I kind of misunderstood the "-n" parameter. It is the interface to listen to, which is not necessarily the host name as seen from outside. I changed that in the following way:

  • if the URL option is present, the host name is taken from there
  • if the URL option is not present, elog calls gethostname()/gethostbyname() to retrieve the local host name

the host name which comes from these two possibilities is used internally in all cases where it's needed, like email notifications.
icon4.gif   Display Subject and HTML tags, regression, posted by Emiliano Gabrielli on Mon Jul 18 10:16:35 2005 
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..
    icon4.gif   Re: Display Subject and HTML tags, regression, posted by Emiliano Gabrielli on Mon Jul 18 18:36:32 2005 

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
       icon2.gif   Re: Display Subject and HTML tags, regression, posted by Stefan Ritt on Wed Jul 20 22:39:05 2005 

Emiliano Gabrielli wrote:

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


Your line
if (p && strchr(str, '>') && p >= str && *(p-1) != '\\')

in the code does not work. If the pattern is at the beginning of the string (p == str), then (p-1) points to an invalid location and can cause a segmentation fault. The correct patch is in CVS.
          icon2.gif   Re: Display Subject and HTML tags, regression, posted by Emiliano Gabrielli on Thu Jul 21 11:02:44 2005 

Stefan Ritt wrote:

Emiliano Gabrielli wrote:

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


Your line
if (p && strchr(str, '>') && p >= str && *(p-1) != '\\')

in the code does not work. If the pattern is at the beginning of the string (p == str), then (p-1) points to an invalid location and can cause a segmentation fault. The correct patch is in CVS.


ehhe, I used "should" infact Tongue
    icon2.gif   Re: Display Subject and HTML tags, regression, posted by Stefan Ritt on Wed Jul 20 22:28:14 2005 

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 Big grin
       icon2.gif   Re: Display Subject and HTML tags, regression, posted by Emiliano Gabrielli on Thu Jul 21 11:00:47 2005 

Stefan Ritt wrote:

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 Big grin


ok, nice Smile
icon1.gif   [code] should be a sort of <CDATA >, posted by Emiliano Gabrielli on Wed Jul 13 15:09:48 2005 
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
    icon2.gif   Re: [code] should be a sort of <CDATA >, posted by Stefan Ritt on Wed Jul 20 21:43:56 2005 

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.
       icon2.gif   Re: [code] should be a sort of <CDATA >, posted by Emiliano Gabrielli on Thu Jul 21 10:59:22 2005 

Stefan Ritt wrote:

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.


thanks Smile
icon4.gif   elog utility for submission used wrong 'Host:' in POST header, posted by Heiko Scheit on Mon Jul 11 19:04:38 2005 
The 'elog' utility for commandline submission used wrong 'Host:' in POST header.
The host listed after 'Host:' should be the host where the server runs, not the 
localhost (see patch below).

$ diff -u elog.c_20050711  elog.c
--- elog.c_20050711     Mon Jul 11 18:54:20 2005
+++ elog.c      Mon Jul 11 18:55:31 2005
@@ -421,7 +421,7 @@
       sprintf(request + strlen(request), "%s/%d?cmd=download", experiment, message_id);
    strcat(request, " HTTP/1.0\r\n");
 
-   sprintf(request + strlen(request), "Host: %s\r\n", host_name);
+   sprintf(request + strlen(request), "Host: %s\r\n", host);
    sprintf(request + strlen(request), "User-Agent: ELOG\r\n");
 
    first = 1;
@@ -872,7 +872,7 @@
    strcat(request, " HTTP/1.0\r\n");
 
    sprintf(request + strlen(request), "Content-Type: multipart/form-data; boundary=%s\r\n", boundary);
-   sprintf(request + strlen(request), "Host: %s\r\n", host_name);
+   sprintf(request + strlen(request), "Host: %s\r\n", host);
    sprintf(request + strlen(request), "User-Agent: ELOG\r\n");
    sprintf(request + strlen(request), "Content-Length: %d\r\n", content_length);
    icon4.gif   Re: elog utility for submission used wrong 'Host:' in POST header, posted by Emiliano Gabrielli on Tue Jul 12 10:15:30 2005 
> The 'elog' utility for commandline submission used wrong 'Host:' in POST header.
> The host listed after 'Host:' should be the host where the server runs, not the
> localhost (see patch below).
>
> $ diff -u elog.c_20050711 elog.c
> --- elog.c_20050711 Mon Jul 11 18:54:20 2005
> +++ elog.c Mon Jul 11 18:55:31 2005
> @@ -421,7 +421,7 @@
> sprintf(request + strlen(request), "%s/%d?cmd=download", experiment, message_id);
> strcat(request, " HTTP/1.0\r\n");
>
> - sprintf(request + strlen(request), "Host: %s\r\n", host_name);
> + sprintf(request + strlen(request), "Host: %s\r\n", host);
> sprintf(request + strlen(request), "User-Agent: ELOG\r\n");
>
> first = 1;
> @@ -872,7 +872,7 @@
> strcat(request, " HTTP/1.0\r\n");
>
> sprintf(request + strlen(request), "Content-Type: multipart/form-data; boundary=%s\r\n", boundary);
> - sprintf(request + strlen(request), "Host: %s\r\n", host_name);
> + sprintf(request + strlen(request), "Host: %s\r\n", host);
> sprintf(request + strlen(request), "User-Agent: ELOG\r\n");
> sprintf(request + strlen(request), "Content-Length: %d\r\n", content_length);

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

On the other hand it should replay with an error when a bogus client tries to speak HTML/1.0 specifing "host:",
and (the wrost case) when the bogus client says to speak HTML/1.1 and doesnt provide the required "Host:" header ...
Yes .. elog will ignore it, but it is an RFC requirement for HTML/1.1 !
       icon2.gif   Re: elog utility for submission used wrong 'Host:' in POST header, posted by Stefan Ritt on Wed Jul 20 21:03:29 2005 

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.
icon3.gif   Cannot stat() config file , posted by Stefan Rudat on Wed Jul 20 08:32:06 2005 
Hi

Elog runs now for serveral month without any problem at a Windows 2000 server.
I must change the access rights for all Folders, remove the user everyone and set the
Rights only to defined groups .
Now I can see following Event ID

Event Type: Information
Event Source: ELOG
Event Category: None
Event ID: 0
Date: 20.07.2005
Time: 08:14:24
User: N/A
Computer: SNDSRV1
Description:
The description for Event ID ( 0 ) in Source ( ELOG ) cannot be found.
The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: Cannot stat() config file; No such file or directory.

My question now. Have someone see the same Problem ?
It this is a access right problem How to set up the access rights for Elog
Elog folders ?

Bye
    icon2.gif   Re: Cannot stat() config file , posted by Stefan Ritt on Wed Jul 20 20:13:26 2005 

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