Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 777 of 806  Not logged in ELOG logo
    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 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 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 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


    icon1.gif   Re: Can't set Author attribute properly in reply?, posted by Emiliano Gabrielli on Tue Jul 26 10:00:34 2005 

Chris Green wrote:
Hi,

I have two problems:

1) With the configuration below, I can't set the Author attribute to be the author of the reply. As written, it gives the Author field as blank. If the Remove on Reply line is removed, it is set to the parent's author. What am I doing wrong?

Subst on reply Author = $long_name
    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
    icon1.gif   Re: Can't set Author attribute properly in reply?, posted by Emiliano Gabrielli on Tue Jul 26 10:49:12 2005 

Stefan Ritt wrote:

Chris Green wrote:
1) With the configuration below, I can't set the Author attribute to be the author of the reply. As written, it gives the Author field as blank. If the Remove on Reply line is removed, it is set to the parent's author. What am I doing wrong?


Hey, elog made it to MiniBooNE! I'm working on MEG...

What you need is the following:
Preset on reply subject = Re: $subject
Preset Author = $long_name
Preset on Reply Author = $long_name
Locked Attributes = Author

The Subst statements work after the entry gets submitted, while the preset statements work before. So Preset on Reply <attribute> is what you need.


Depending of what your paranoia level is Smile
Substitute is the only way I have to be assure it is as I want ... yes, in real life nobody of my users will never try to change the generated HTML ad replace by hand the Author, but ... Tongue
    icon2.gif   Re: Can't set Author attribute properly in reply?, posted by Emiliano Gabrielli on Tue Jul 26 10:55:03 2005 

Stefan Ritt wrote:

Emiliano Gabrielli wrote:
Substitute is the only way I have to be assure it is as I want ...


No, that's not true. A
Locked attributes = Author

will do the job as well.


I can't argue how it works ...
The following code will assure that, if the HTML generated by elog would be modified by hand by a malicious user the server can still preset the author field with the right $long_name?
Locked attributes = Author
Preset on Reply Author = $long_name

how works in details the "Locked Attribute" parameter then ?? ...
ELOG V3.1.5-3fb85fa6