> I think this is reasonable. All the HTML-files which I want insert (created with the software
> INCA) are not shown correctly. My testfiles made with OpenOffice are shown correctly. Maybe
> you have the time to program an option for the attachement "Show inside/Show in new window or
> tab", so that the user can choose, how his HTML file is shown. Similiar to the option "Submit
> as HTML text".

I changed it such that all attachment are shown in a separate browser window if clicked. Hope
this satisfies most people. I believe an extra switch in the config file is too much for this
little thing, unless someone absolutely wants back the old behaviour.

Thank you very much for your request, well motivated and described. I hope I 
will soon find time to impelment this.

I implemented your request. The syntax is:

Format <attribute> = <flags>,<css_class_name>,<css_class_value>,<width>,<size>

<flags>
  Sum of following values:
    1: Display attribute in same line as previous attribute
    2: Display radio buttons or check boxes in separate lines (if applicable)

<css_class_name>,<css_class_value> 
  Cascading Style Sheet class names used for cells containing attribute name
  or value, respectively. The classes must be defined in the style sheet file 
  (usually themes/default/default.css)

<width>> 
  Width of the text entry field in characters

<size> 
  Maximum number of characters allowed. 

Default is "0, attribname, attribvalue, 80, 500". Trailing parameters can be 
ommitted, so specifying for example only the flags is possible.

In order to have several attributes in one line, each line is now a separate 
table. This requires adjustment of the CSS class "attribname". Best you use 
the current default stylesheet (http://midas.psi.ch/elogdemo/default.css).

You can compare the two different approaches (one attribute per line/multiple 
attributes per line) in this forum and the "archive" logbook. The "subject" 
field in this forum also uses a different style class.

Note that if you upgrade to the current CVS version 
(http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.129), you also 
have to change following options in your elogd.cfg:

- The style sheet must contain the new class "attribhead"
- "Email message body" has been replaces by "Email format"
- "Filtered browsing" is now off by default
- Locking (during editing of messages) is disabled by default, and enabled 
by "Use lock = 1"

Very interesting, indeed!
Thank you very much for the implementation. I believe this is a big step ahead 
in terms of ELOG screen formating (and therefore easier/more ergonomic 
dataentry/reading).

We will test your modifications as soon as you make a new release.

Tomas


> I implemented your request. The syntax is:
> 
> Format <attribute> = <flags>,<css_class_name>,<css_class_value>,<width>,<size>
> 
> <flags>
>   Sum of following values:
>     1: Display attribute in same line as previous attribute
>     2: Display radio buttons or check boxes in separate lines (if applicable)
> 
> <css_class_name>,<css_class_value> 
>   Cascading Style Sheet class names used for cells containing attribute name
>   or value, respectively. The classes must be defined in the style sheet file 
>   (usually themes/default/default.css)
> 
> <width>> 
>   Width of the text entry field in characters
> 
> <size> 
>   Maximum number of characters allowed. 
> 
> Default is "0, attribname, attribvalue, 80, 500". Trailing parameters can be 
> ommitted, so specifying for example only the flags is possible.
> 
> In order to have several attributes in one line, each line is now a separate 
> table. This requires adjustment of the CSS class "attribname". Best you use 
> the current default stylesheet (http://midas.psi.ch/elogdemo/default.css).
> 
> You can compare the two different approaches (one attribute per line/multiple 
> attributes per line) in this forum and the "archive" logbook. The "subject" 
> field in this forum also uses a different style class.
> 
> Note that if you upgrade to the current CVS version 
> (http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.129), you also 
> have to change following options in your elogd.cfg:
> 
> - The style sheet must contain the new class "attribhead"
> - "Email message body" has been replaces by "Email format"
> - "Filtered browsing" is now off by default
> - Locking (during editing of messages) is disabled by default, and enabled 
> by "Use lock = 1"

Display Telephone = <a href="http://any.company.com/telbook.cgi?search=$Name">$Name's telephone number</a>

Until yesterday this was interpreted as HTML.

After upgrading to 2.7.7, I still get a valid link but the full HTML code is also displayed: the user sees
''<a href="http://any.company.com/telbook.cgi?search=myname">myname's telephone number</a>''
where he should only see:
''myname's telephone number''

I am 99% sure this is a consequence of the upgrade. Is there a way to get the original behaviour back?
Thanks a lot
Soren Poulsen

 I have more precise information about the nature of this issue, which concerns the display of E-logs

In the previous version 2.7.6, E-log would generate HTML like this:

td class="attribvalue">
<a href="https://edms.cern.ch/camms/plsql/d7i_report_CV_WO_VIEW.form_7?event=15403690&button=Search">15403690</a>&nbsp;</td>

In the latest version 2.7.7, E-log generates HTML like this (for the same attribute):

<td class="attribvalue">
&lt;a href="<a href="https://edms.cern.ch/camms/plsql/d7i_report_CV_WO_VIEW.form_7?event=15575045&amp;button=Search">https://edms.cern.ch/camms/plsql/d7i_report_CV_WO_VIEW.form_7?event=15575045&amp;button=Search</a>"&gt;15575045&lt;/a&gt;&nbsp;</td>

Soren Poulsen

Display Telephone = <a href="http://any.company.com/telbook.cgi?search=$Name">$Name's telephone number</a>

Until yesterday this was interpreted as HTML.

After upgrading to 2.7.7, I still get a valid link but the full HTML code is also displayed: the user sees
''<a href="http://any.company.com/telbook.cgi?search=myname">myname's telephone number</a>''
where he should only see:
''myname's telephone number''

I am 99% sure this is a consequence of the upgrade. Is there a way to get the original behaviour back?
Thanks a lot
Soren Poulsen

You need

Allow HTML = 1

in your configuration file. See the documentation for details. This featue is new in 2.7.7.

Display Telephone = <a href="http://any.company.com/telbook.cgi?search=$Name">$Name's telephone number</a>

Until yesterday this was interpreted as HTML.

After upgrading to 2.7.7, I still get a valid link but the full HTML code is also displayed: the user sees
''<a href="http://any.company.com/telbook.cgi?search=myname">myname's telephone number</a>''
where he should only see:
''myname's telephone number''

I am 99% sure this is a consequence of the upgrade. Is there a way to get the original behaviour back?
Thanks a lot
Soren Poulsen

Thanks a lot. In fact I did not read the 2.7.7 version of the documentation, which I should have done.

Have a good aftenoon

Soren

• As you can see...
• <UL> is possible