Re: Crashes when editing entries, posted by T. Ribbrock on Wed Jul 29 14:48:34 2009
|
By now, I've installed 2244 and ran some rudimentary tests. So far, I was not able to reproduce the crash anymore. Looking good!  |
init_resize sometimes not defined, posted by Richard Stamper on Wed Aug 5 01:07:04 2009
|
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 |
Re: init_resize sometimes not defined, posted by Stefan Ritt on Wed Aug 5 13:36:44 2009
|
| 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 |
HTML in attribute values, posted by soren poulsen on Thu Aug 6 11:40:11 2009
|
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
|
|
Re: HTML in attribute values, posted by soren poulsen on Thu Aug 6 11:53:29 2009
|
| 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
|
|
Re: HTML in attribute values, posted by Stefan Ritt on Thu Aug 6 12:11:50 2009
|
| 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> </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>
|
You need
Allow HTML = 1
in your configuration file. See the documentation for details. This featue is new in 2.7.7. |
|
Re: HTML in attribute values, posted by soren poulsen on Thu Aug 6 13:09:50 2009
|
| 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> </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>
|
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
|
Fix text prevents user from editing text during creation, instead of just edit, posted by Allen on Mon Aug 24 21:47:14 2009
|
When we set Fix text = 1, according to the syntax, this should prevent users from modifying the text field during an edit, but it looks like it is blocking access at both time of edit and creation, meaning you can never add anything to it. Is that the intended functionality? |