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. |
|
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 .. |
|
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. |
|
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  |
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  |
|
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"
thank you in advance  |
I added the conditional attributes for the "single entry" view (not the mail yet), so you might again try it. |
|
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 |
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 |
|
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 |
|
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"
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 |