| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1257
|
Mon Jul 11 14:30:11 2005 |
 | Emiliano Gabrielli | AlberT@SuperAlberT.it | Request | All | | Re: < img > in Display Attribute |
| 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" 
thank you in advance  |
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  .
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 ? |
|
1258
|
Mon Jul 11 14:35:00 2005 |
 | Emiliano Gabrielli | AlberT@SuperAlberT.it | Request | All | | Re: userlist multiple select |
| Stefan Ritt wrote: |
| Emiliano Gabrielli wrote: | Here I am again
My goal is to put a "Co-Authors" Attribute in my logbook, giving the possibility to other people in the control room to have credits about an entry... I added a "Co-Author" attribute, but It shold permit a "multliple" selection (a checkbox is not good) ... the perfect solution would be to add the attribute "multiple" to the <select> tag, and filling the elog Attribute value with a comma separated list of the selections ...
tnx in advance |
Have you tried MOptions ... which gives you check boxes where more than one can be selected?
I presume you have, but you really would prefer a multi-selection box instead of multiple check boxes  . Well, let's make a deal: if you explain everybody how to do a selection in a multi-select box (with all the Shift-Click, CTRL-Click, and this under different operating systems), I will implement it  |
a multiple selection box it's a standard web tool .. if one is not able to use its browser is not an elog problem IMHO
My request is becouse having a number of user (say 20) makes the checkbox solution very very nasty .. again, it's a choice you give to the smart user .. others simply will not notice any change in elog |
|
1261
|
Tue Jul 12 15:19:07 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | | Re: userlist multiple select |
| Emiliano Gabrielli wrote: | | a multiple selection box it's a standard web tool .. if one is not able to use its browser is not an elog problem IMHO |
Really? Can you point me to a common web site using this? I would really like to see how other people use this.
| Emiliano Gabrielli wrote: | | My request is becouse having a number of user (say 20) makes the checkbox solution very very nasty .. again, it's a choice you give to the smart user .. others simply will not notice any change in elog |
Ok, I put it on my wishlist. If more than one person asks for this, I will implement it. Unfortunately it's not only putting a multiple into the HTML page, it's also a different way how multiple selections are passed in the POST form and their decoding, so it will be an hour or two of work for me. |
|
1263
|
Wed Jul 13 10:12:38 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Request | All | | Re: userlist multiple select |
| Stefan Ritt wrote: |
| Emiliano Gabrielli wrote: | | a multiple selection box it's a standard web tool .. if one is not able to use its browser is not an elog problem IMHO |
Really? Can you point me to a common web site using this? I would really like to see how other people use this.
|
I can't remember just now a web site using it .. what I mean is that "multiple" attribute for the "select" tag is a standard for the web (it's not an IE extension or so on ..) so every web browser implements it.
It's normally used, for example, when you fill a form describing your attitudes, here you can often choose from a select box a number of interest you are concerded.. but it is only an example
| Stefan Ritt wrote: |
| Emiliano Gabrielli wrote: | | My request is becouse having a number of user (say 20) makes the checkbox solution very very nasty .. again, it's a choice you give to the smart user .. others simply will not notice any change in elog |
Ok, I put it on my wishlist. If more than one person asks for this, I will implement it. Unfortunately it's not only putting a multiple into the HTML page, it's also a different way how multiple selections are passed in the POST form and their decoding, so it will be an hour or two of work for me. |
Yes I know, uhm... if you point me to the right piece of code to be adjusted I can see if I'll be able to do the job |
|
1264
|
Wed Jul 13 15:09:48 2005 |
 | Emiliano Gabrielli | AlberT@SuperAlberT.it | Bug report | All | | [code] should be a sort of <CDATA > | 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 |
|
|
1265
|
Thu Jul 14 12:47:06 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Bug report | All | | short/long_name should point the same user | .. I mean that if I use:
Restrict edit = 1
; preset author and email
Preset Author = $short_name
Preset Author Email = $user_email
Preset on reply Author = $short_name
Preset on reply Author Email = $user_email
Subst on reply subject = Re: $subject
; these attributes cannot be changed
Locked Attributes = Author, Author Email
and then I change Preset Author to be "$long_name" Elog does not permit the autor to edit an old post of its own ...
It is not able to argue that short and long name are the same person..
Yes I know, you'll ask me why I should change it .. the anwer is.. I don't have to, but (as I could do it logically) I'd like to be able to do..
In my case I changed it by error, people inserted entries and now I restored the correct one .. so now I have to unlock the attribute and change every Author by hand as admin
|
|
1266
|
Thu Jul 14 13:05:33 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Bug report | All | | Re: short/long_name should point the same user |
| Emiliano Gabrielli wrote: | .. I mean that if I use:
Restrict edit = 1
; preset author and email
Preset Author = $short_name
Preset Author Email = $user_email
Preset on reply Author = $short_name
Preset on reply Author Email = $user_email
Subst on reply subject = Re: $subject
; these attributes cannot be changed
Locked Attributes = Author, Author Email
and then I change Preset Author to be "$long_name" Elog does not permit the autor to edit an old post of its own ...
It is not able to argue that short and long name are the same person..
Yes I know, you'll ask me why I should change it .. the anwer is.. I don't have to, but (as I could do it logically) I'd like to be able to do..
In my case I changed it by error, people inserted entries and now I restored the correct one .. so now I have to unlock the attribute and change every Author by hand as admin
|
a problem related to this issue is that an attribute of userlist type automatically sets the user to be in the long form..
My proposal is to alwais store users in the long form and anly give the possibility to use the short or long form in displaing time.. |
|
1267
|
Thu Jul 14 15:58:07 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Comment | All | | A new ELOG user wants to register on "127.0.0.1" | 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 ? |
|