ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67183
|
Fri Feb 10 17:18:25 2012 |
| John Doroshenko | doroshenko@physics.rutgers.edu | Bug report | Linux | Windows | 2.9.0 | Re: ssl problems |
Olaf Kasten wrote: |
Hi there,
I have a connection problem with an actual elog installation. Many Browsers like as Chrome, Firefox and IE don't connect to the elog server with ssl = 1 in elogd.cfg.
I tested with Firefox 3.6 and IE 7 installations and there are no problems.
I guess it's a bug. Does someone have a suggestion to solve that problem?
Thx. Olaf
|
Hi!
This just started happening here also. Some users can't get on to a SSL=1 config'd elog using either IE or firefox 10 (win7 or linux) or chrome. SAFARI works. Occurs in 2.8.0 and a newly built (even after
ssl yum updates) 2.9.0 version on SL5.5 system. Seems to accept self signed cert then nothing.. (connection reset message). Tried an stunnel from one port to port running elog
with SSL=0. Same behavior. Doesn't work on some browsers. Any clues?
Thanks,
-John |
67208
|
Mon Mar 5 16:19:24 2012 |
| Paraic Fahey | paraic.fahey@pfizer.com | Bug report | Windows | 2.7.6 | Record Proliferation |
Saving, using Submit sees recently updated fields cleared after hitting SUBMIT.
MOre significantly this then leads to a proliferation of instances of the same record being generated in the logfile and consequently on the logbook.
Has anybody a fix or advice on this? |
67209
|
Thu Mar 8 10:01:47 2012 |
| Olivier Callot | olivier.callot@cern.ch | Bug report | Linux | 2.9.0-2418 | Truncation of the displayed text in Summary view of the list of entries |
In the summary view, it seems that the text is truncated at the first "<" character. See https://lblogbook.cern.ch/Shift/48812 for a simple entry, then use the 'list' command to see that only a very small part is displayed. |
67210
|
Wed Mar 14 14:38:10 2012 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.9.0-2418 | Re: Truncation of the displayed text in Summary view of the list of entries |
Olivier Callot wrote: |
In the summary view, it seems that the text is truncated at the first "<" character. See https://lblogbook.cern.ch/Shift/48812 for a simple entry, then use the 'list' command to see that only a very small part is displayed.
|
That's a feature 
In the summary view, I cannot use any HTML code, since it will screw up the table layout. Therefore elog searches for any "<" and ">" pairs and removes the text in between. In principle one could do a better job, but I do not want to write a complete HTML interpreter just for that purpose. |
67211
|
Wed Mar 14 14:45:23 2012 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.7.6 | Re: Record Proliferation |
Paraic Fahey wrote: |
Saving, using Submit sees recently updated fields cleared after hitting SUBMIT.
MOre significantly this then leads to a proliferation of instances of the same record being generated in the logfile and consequently on the logbook.
Has anybody a fix or advice on this?
|
I have not heard of that problem before.
The key to fix is to reproduce it, then teach me how to reproduce it. Only errors I can reproduce on my computer I am able to fix.
Best regards,
Stefan |
67212
|
Wed Mar 14 15:08:17 2012 |
| Olivier Callot | olivier.callot@cern.ch | Bug report | Linux | 2.9.0-2418 | Re: Truncation of the displayed text in Summary view of the list of entries |
Stefan Ritt wrote: |
Olivier Callot wrote: |
In the summary view, it seems that the text is truncated at the first "<" character. See https://lblogbook.cern.ch/Shift/48812 for a simple entry, then use the 'list' command to see that only a very small part is displayed.
|
That's a feature 
In the summary view, I cannot use any HTML code, since it will screw up the table layout. Therefore elog searches for any "<" and ">" pairs and removes the text in between. In principle one could do a better job, but I do not want to write a complete HTML interpreter just for that purpose.
|
Well, this is a choice. But if the encoding of the entry is 'plain', you could just avoid checking for embeded HTML. We use the summary view constantly for our main experiment logbook. Thanks anyway. |
67213
|
Wed Mar 14 15:34:41 2012 |
| David Pilgram | David.Pilgram@epost.org.uk | Bug report | Linux | Windows | 2.7.6 | Re: Record Proliferation |
Stefan Ritt wrote: |
Paraic Fahey wrote: |
Saving, using Submit sees recently updated fields cleared after hitting SUBMIT.
MOre significantly this then leads to a proliferation of instances of the same record being generated in the logfile and consequently on the logbook.
Has anybody a fix or advice on this?
|
I have not heard of that problem before.
The key to fix is to reproduce it, then teach me how to reproduce it. Only errors I can reproduce on my computer I am able to fix.
Best regards,
Stefan
|
Does this occur if you are adding an attachment? As I am blessed with forever using ancient systems, I've seen fields and indeed text being cleared because they were entered between clicking on 'Upload' for an attachment and the .png files being generated and displayed. Answer here is patience - I use all too much of mine up in this exercise, sadly.
|
67214
|
Wed Mar 14 16:04:04 2012 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.9.0-2418 | Re: Truncation of the displayed text in Summary view of the list of entries |
Olivier Callot wrote: |
Stefan Ritt wrote: |
Olivier Callot wrote: |
In the summary view, it seems that the text is truncated at the first "<" character. See https://lblogbook.cern.ch/Shift/48812 for a simple entry, then use the 'list' command to see that only a very small part is displayed.
|
That's a feature 
In the summary view, I cannot use any HTML code, since it will screw up the table layout. Therefore elog searches for any "<" and ">" pairs and removes the text in between. In principle one could do a better job, but I do not want to write a complete HTML interpreter just for that purpose.
|
Well, this is a choice. But if the encoding of the entry is 'plain', you could just avoid checking for embeded HTML. We use the summary view constantly for our main experiment logbook. Thanks anyway.
|
Ok, I fixed that in revision 2442. |