Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 282 of 807  Not logged in ELOG logo
ID Date Icondown Author Author Email Category OS ELOG Version Subject
  66491   Tue Aug 4 11:22:18 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionMac OSX2.7.6Re: Problems when trying to set up mirror elog

Ricardo Goncalo wrote:

Stefan Ritt wrote:

Ricardo Goncalo wrote:

Retrieving entries from "https://www.pp.rhul.ac.uk:8080/ATLAS Trigger"...

Remote server is not an ELOG server

 
...so I'm running out of options. Any ideas would be welcome!
Cheers,
Ricardo

 

Your problem is here. I wrote that synchronization is not possible through SSL, but you try to access https://www.pp.rhul.ac.uk:8080 which is SSL (because you have https:// not http://). 

 Ah, I see. Hmm, ok it doesn't work without the s either. I can't access the server in that case. Ok, I think I'll just wait for this feature to be available. Thanks for your help!

 Of course you also have to switch your mirror server not to use SSL as well. You can check this then by accessing it directly via http://www.pp.rhul.ac.uk:8080/ATLAS Trigger from the same computer. Also make sure that you don't have any firewall issue.

  66493   Wed Aug 5 13:36:44 2009 Reply Stefan Rittstefan.ritt@psi.chBug reportAll2.7.7-2246Re: init_resize sometimes not defined

Richard Stamper wrote:

Under some circumstances the New/Edit entry screen can invoke the init_resize() function in the onload handler for the <body> tag, but the init_resize() function is not defined.  In my case there is a log where the encoding is plain text (Default encoding = 1) and the message height is restricted (Message height = 4).  Creating or editing entries in this log generates warnings in the Firefox error console and alert boxes in IE about init_resize being undefined.

I think there is some missing logic.  In revision 2246 of elogd.c

  • at line 9924, if enc_selected = 1 then init_resize() is included in the onload handler, but
  • at line 9801, if enc_selected = 1 but at least one of the  "Message height" or "Message width" attributes is set then the code defining init_resize() is not include

I think you need to duplicate the checks on the Message height and Message width attributes at lines 9924, so that the init_resize() function is only included when defined.

Richard S

Perfect! Not only your analysis but also your suggested solution. I implemented that in revision 2249.

Stefan 

  66495   Thu Aug 6 08:00:22 2009 Reply Stefan Rittstefan.ritt@psi.chRequestAll2.7.6Re: alphabetize Quick Filter items?

Dennis Seitz wrote:

 Hi Stefan,

I'd like to request a feature: automatic alphabetization of the items in the Quick Filter menus.

We track quite a few detector assemblies, which are produced with non-sequential designations. It would be useful if the Quick Filter list was automatically sorted alphabetically to make it more convenient for folks to find a particular item.

I know people can always search by designation but it would be handy to have this alpha sorting feature. Would it be possible to include that in a future release?

Thanks again for a *very* useful logging system!

Dennis

The order of items in a Quick Filter menu is exactly as in the configuration file. Like if you have items

Options Type = C, D, A, B

they are shown like that in the quick filter menu. If you want to sort them, just do the sorting yourself in the configuration file like

Options Type = A, B, C, D

I have not implemented automatic sorting since some people want a different order, like some main topics at top. So by following the order from the configuration file, everybody can be satisfied just by chaning the order in the config file.

- Stefan 

  66497   Thu Aug 6 11:53:29 2009 Reply soren poulsensoren.poulsen@cern.chBug reportLinux2.7.7Re: HTML in attribute values

soren poulsen wrote:

Hi,

I am using syntax like (from the doc):

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

 

  66498   Thu Aug 6 12:11:50 2009 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.7.7Re: HTML in attribute values

soren poulsen wrote:

soren poulsen wrote:

Hi,

I am using syntax like (from the doc):

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>

You need

Allow HTML = 1

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

  66499   Thu Aug 6 13:09:50 2009 Reply soren poulsensoren.poulsen@cern.chBug reportLinux2.7.7Re: HTML in attribute values

Stefan Ritt wrote:

soren poulsen wrote:

soren poulsen wrote:

Hi,

I am using syntax like (from the doc):

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>

You need

Allow HTML = 1

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

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

 

  66501   Fri Aug 7 08:36:19 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionAll2.7.3Re: Pre-populate Attachments in URL

Erik Iverson wrote:
Is there a way to pre-populate the new entry window with one or more attachments? Per the documentation, this is easy to do with attributes, i.e., http://localhost:8070/demo/?cmd=New&pauthor=joe&ptype=Info as a URL or bookmark will do it. I'd like to do the same thing with attachments, for example http://localhost:8070/demo/?cmd=New&pauthor=joe&ptype=Photograph&attfile1=picture1.jpg&attfile2=picture2.jpg might prepopulate two attachments, giving me an edit window all ready to enter the brief description represented by the two pictures.


That would be nice, I want this, too! But unfortunately your browser does not allow this for security reasons, and I found no way around. Assume you look to a page on the internet, and it pre-populates a file selector with something like /etc/passwd or any other sensitive file. Then this box gets hidden by some CSS style so you don't see it. So as soon as you click on something on that page, your sensitive files gets submitted, and you don't want that. Therefore it's impossible to pre-populate file selector boxes.

- Stefan
  66502   Fri Aug 7 23:09:42 2009 Reply Dennis Seitzdseitz@berkeley.eduRequestAll2.7.6Re: alphabetize Quick Filter items?

Stefan Ritt wrote:

Dennis Seitz wrote:

 Hi Stefan,

I'd like to request a feature: automatic alphabetization of the items in the Quick Filter menus.

We track quite a few detector assemblies, which are produced with non-sequential designations. It would be useful if the Quick Filter list was automatically sorted alphabetically to make it more convenient for folks to find a particular item.

I know people can always search by designation but it would be handy to have this alpha sorting feature. Would it be possible to include that in a future release?

Thanks again for a *very* useful logging system!

Dennis

The order of items in a Quick Filter menu is exactly as in the configuration file. Like if you have items

Options Type = C, D, A, B

they are shown like that in the quick filter menu. If you want to sort them, just do the sorting yourself in the configuration file like

Options Type = A, B, C, D

I have not implemented automatic sorting since some people want a different order, like some main topics at top. So by following the order from the configuration file, everybody can be satisfied just by chaning the order in the config file.

- Stefan 

 Yes, I have been manually sorting and resorting. We have extendable attributes and the list keeps growing so I have to resort every so often. I thought perhaps a simple alphanumeric sort as an option would be popular with most users so I thought I'd ask for it. It would really simplify things for me. Users who want to sort manually could do so by disabling the option. It never hurts to ask!

 

ELOG V3.1.5-3fb85fa6