| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1297
|
Fri Jul 22 08:56:20 2005 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.5.? | Re: Date in CSV and XML in UNIX time |
| 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. |
|
1296
|
Fri Jul 22 03:15:29 2005 |
 | PJ Meyer | pjm@pjmeyer.org | Question | Windows | 2.5.? | Date in CSV and XML in UNIX time |
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? |
|
1295
|
Thu Jul 21 12:54:32 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Request | All | | Re: <img> in Display Attribute |
| 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" 
thank you in advance  |
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) 
- if one edits the entry all fields ar correctly displayed
In full list mode:
- nothing changed, no conditional display is working
revision 1.707 works correctly instead |
|
1294
|
Thu Jul 21 11:02:44 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Bug report | Linux | rev 1.703 | Re: Display Subject and HTML tags, regression |
| 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 |
|
1293
|
Thu Jul 21 11:00:47 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Bug report | Linux | rev 1.703 | Re: Display Subject and HTML tags, regression |
| 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  |
ok, nice |
|
1292
|
Thu Jul 21 10:59:22 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Bug report | All | | Re: [code] should be a sort of <CDATA > |
| 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 |
|
1291
|
Thu Jul 21 09:31:35 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Request | All | | Re: < img > in Display Attribute |
| 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 |
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  |
LOL |
|
1290
|
Wed Jul 20 23:32:46 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | | Re: <img> in Display Attribute |
| 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"
thank you in advance |
I added the conditional attributes for the "single entry" view (not the mail yet), so you might again try it. |