| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66497
|
Thu Aug 6 11:53:29 2009 |
 | soren poulsen | soren.poulsen@cern.ch | Bug report | Linux | 2.7.7 | Re: 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> </td>
In the latest version 2.7.7, E-log generates HTML like this (for the same attribute):
<td class="attribvalue">
<a href="<a href="https://edms.cern.ch/camms/plsql/d7i_report_CV_WO_VIEW.form_7?event=15575045&button=Search">https://edms.cern.ch/camms/plsql/d7i_report_CV_WO_VIEW.form_7?event=15575045&button=Search</a>">15575045</a> </td>
Soren Poulsen
|
|
66496
|
Thu Aug 6 11:40:11 2009 |
 | soren poulsen | soren.poulsen@cern.ch | Bug report | Linux | 2.7.7 | HTML in attribute values |
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
|
|
66495
|
Thu Aug 6 08:00:22 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | 2.7.6 | Re: 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 |
|
66494
|
Wed Aug 5 19:05:01 2009 |
| Dennis Seitz | dseitz@berkeley.edu | Request | All | 2.7.6 | alphabetize Quick Filter items? |
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 |
|
66493
|
Wed Aug 5 13:36:44 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | 2.7.7-2246 | Re: 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 |
|
66492
|
Wed Aug 5 01:07:04 2009 |
 | Richard Stamper | r.stamper@rl.ac.uk | Bug report | All | 2.7.7-2246 | init_resize sometimes not defined |
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 |
|
66491
|
Tue Aug 4 11:22:18 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Mac OSX | 2.7.6 | Re: 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. |
|
66490
|
Tue Aug 4 10:48:26 2009 |
| Ricardo Goncalo | jgoncalo@mail.cern.ch | Question | Mac OSX | 2.7.6 | Re: Problems when trying to set up mirror elog |
| 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! |