Re: Truncation of the displayed text in Summary view of the list of entries, posted by Stefan Ritt on Wed Mar 14 14:38:10 2012
|
| 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. |
|
Re: Record Proliferation, posted by Stefan Ritt on Wed Mar 14 14:45:23 2012
|
| 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 |
Re: Truncation of the displayed text in Summary view of the list of entries, posted by Olivier Callot on Wed Mar 14 15:08:17 2012
|
| 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. |
Re: Record Proliferation, posted by David Pilgram on Wed Mar 14 15:34:41 2012
|
| 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.
|
|
Re: Truncation of the displayed text in Summary view of the list of entries, posted by Stefan Ritt on Wed Mar 14 16:04:04 2012
|
| 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. |
segfault on empty, non-writable passwd file, posted by Achim Dreyer on Mon Mar 26 13:44:23 2012
|
Segfault when password file is empty and not writable a segmentation fault is generated when a new user tries to register:
root# > passwd
root# chown root.root passwd
root# chmod 644 passwd
root# grep -i usr elogd.cfg
root#
kernel: [515323.672377] elogd[31048]: segfault at 78 ip 00000000004ba780 sp 00007fff03cd2078 error 4 in elogd[400000+dc000]
I cannot reproduce this error when running within gdb.
|
|
Preset Text?, posted by Grant on Mon Apr 9 15:02:24 2012
|
Hi Stefan,
I'm having a problem with 'Preset Text' now behaving differently in the latest release (2.9.1)?
My config file for example has always had: 'Preset Text = This is a test.', previously 'This is a test' was put
verbatim into the text area, now it seems to think whatever follows 'Preset Text =' is always a file and I end
up with 'File <i> This is a test. <i> cannot be found'?
I did notice a 'Print warning if "preset text" file cannot be found' line in the latest release notes, does this
now mean wherever I have used the method above I will now need to make a text file to match?
I'm using them embedded in conditional attributes if that makes any difference?
Thanks for your help. |
|
wrong version number in spec file, posted by Achim Dreyer on Mon Apr 9 19:58:51 2012
|
localhost$ svn diff elog.spec
Index: elog.spec
===================================================================
--- elog.spec (revision 2446)
+++ elog.spec (working copy)
@@ -2,7 +2,7 @@
Name: elog
Summary: elog is a standalone electronic web logbook
-Version: 2.8.1
+Version: 2.9.1
Release: 1
License: GPL
Group: Applications/Networking
|