ELOG Forum

Demo Discussion

Forum Config Examples Contributions Vulnerabilities

Discussion forum about ELOG, Page 122 of 806

Not logged in

Find | Login | Help

New entries since:

Thu Jan 1 01:00:00 1970

Full | Summary | Threaded | Hide attachments

6445 Entries

Goto page Previous 1, 2, 3 ... 121, 122, 123 ... 804, 805, 806 Next

Wed Jul 20 21:43:56 2005

Re: [code] should be a sort of <CDATA >

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.

1286

Wed Jul 20 22:28:14 2005

Re: Display Subject and HTML tags, regression

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

1287

Wed Jul 20 22:39:05 2005

Re: Display Subject and HTML tags, regression

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.

1288

Wed Jul 20 23:24:59 2005

Re: hide attributes when view the logbook

Juliana Peng wrote:

but it seems only effective when adding the new entry. All the attributes will show in logbook. Is there a way to hide some of the attributes? It would be good to let each user to choose what to see what not to see, create their own view. Can you put it on your to-do list or wishlist?

I implemented your request and committed to CVS. Please test if it does what you want, since I did not have much time to test it.

1289

Wed Jul 20 23:30:45 2005

Re: < img > in Display Attribute

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

1290

Wed Jul 20 23:32:46 2005

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

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]

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

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

thanks

Goto page Previous 1, 2, 3 ... 121, 122, 123 ... 804, 805, 806 Next

ELOG V3.1.5-3fb85fa6