| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66286
|
Wed Apr 1 18:03:44 2009 |
 | Joseph Le | joseph.p.le@nasa.gov | Question | Windows | 2.7.5-218 | is it posible to configure text message area contain two sections |
Hi,
I try to configure the elog as servers log book. I need to devide the text entry area by 2 section: 1 for issue so I can put in detail what is the issue of my servers. the other section below the 1st one for solution. is it posible to do so?
Joseph. |
|
Draft
|
Wed Sep 16 01:27:20 2015 |
| Joseph McKenna | joseph.mckenna@cern.ch | Bug report | Linux | 2.9.0(elogd) | elog client overwriting attached files when editing existing log |
Using the elog client to upload atachments, I can successfully send attachments to an existing elog, however the existing attachments are lost.
I have tested using the elog client version 3.1.1 and elog client version 2.9.2 sending to elogd 2.9.0
elog -h localhost -p 8080 -l test -f file1.png -f file2.png -e 249 -v -x
This works great, the text contained in the elog post is retained, however all attachments are lost and replaced with those sent by this command.
Can anyone provide some tips? I am not sure if its a problem with the client or server.
Thank you in advance!
Joseph
|
|
68116
|
Wed Sep 16 02:47:33 2015 |
| Joseph McKenna | joseph.mckenna@cern.ch | Bug report | Linux | 2.9.0(elogd) | elog client overwriting attached files when editing existing log |
Using the elog client to upload atachments, I can successfully send attachments to an existing elog, however the existing attachments are lost.
I have tested using the elog client version 3.1.1 and elog client version 2.9.2 sending to elogd 2.9.0
elog -h localhost -p 8080 -l test -f file1.png -f file2.png -e 249 -v -x
This works great, the text contained in the elog post is retained, however all attachments are lost and replaced with those sent by this command.
Can anyone provide some tips? I am not sure if its a problem with the client or server.
Thank you in advance!
Joseph
|
|
68792
|
Fri May 4 14:43:35 2018 |
 | Joseph McKenna | joseph.mckenna@cern.ch | Bug report | Linux | 2.9.2 | Elog ID entry bug at >99999 entries |
We have a possible bug with elog that the ID for an elog entry at over 99,999 entires reads as 10,000...
68792/1 Illistrates the problem, we use this ID often to cross reference from out datalog...
Is this a know bug we can find a fix for? We are using: elogd 2.9.2 built Jul 14 2015, 18:58:06 revision |
| Attachment 1: sequencer_events.png
|
|
|
68798
|
Tue May 8 16:17:28 2018 |
 | Joseph McKenna | joseph.mckenna@cern.ch | Bug report | Linux | 2.9.2 | Re: Elog ID entry bug at >99999 entries |
Thank you all for your kind responses. Please consider this thread resolved: no bug in elog
| Chris Rasmussen wrote: |
|
ah yes, that was a helpful clue. Our elogd.cfg file led me to a .js file which redefines the ID to the elog:SequencerEvents/XXXXX format and it indeed had a silly hard coded length of that string.
Since I am pretty sure this is our code, I think it is safe to say that this is not a bug in the elog
| Andreas Luedeke wrote: |
|
Well, in my example the ID link worked just fine.
There could be a string length limitation, but it could be as well the way you are creating the ID that is the source of the problem: I would need the part of your elogd.cfg that defines how you format your ID in order to try to reproduce your problem.
Cheers, Andreas
| Chris Rasmussen wrote: |
|
Hi Andreas, I'm working on the same experiment as Joseph who submitted the bug report.
You are right, IDs greater than 10^5 are created no problem. The issue is with the internal elog link, in this case of the form elog:SequencerEvents/XXXXX The link generated uses only the first 5 digits of the message ID, and therefore links to the wrong message. In the two attachments you can see our sequencer event number 100098, first displaying the message where all of the ID is displayed and secondly in "full" view of the elog front page. Here, the "ID" column contains a link with the string: elog:SequencerEvents/10009. Our problem is that we often use this string to paste into other elogs and generate a link to the sequencer event message. However, since the string uses too few digits, we end up with a link to the wrong message
| Andreas Luedeke wrote: |
|
I am not sure I understand your bug report.
I can easily create IDs greater than 100'000 (see attached picture), but that is not your problem, or is it?
Cheers, Andreas
| Joseph McKenna wrote: |
|
We have a possible bug with elog that the ID for an elog entry at over 99,999 entires reads as 10,000...
68792/1 Illistrates the problem, we use this ID often to cross reference from out datalog...
Is this a know bug we can find a fix for? We are using: elogd 2.9.2 built Jul 14 2015, 18:58:06 revision
|
|
|
|
|
|
|
67336
|
Sun Sep 16 18:40:06 2012 |
| Josef Uher | josef.uher@gmail.com | Question | All | 2.9.2 | HTML editor |
Hi All,
maybe I missed something in the configuration, but how do I get this nice editor for HTML like the one available on this forum?
Thanks a lot for advice. |
|
67337
|
Sun Sep 16 21:14:12 2012 |
| Josef Uher | josef.uher@gmail.com | Bug report | Mac OSX | 2.9.2 | Crash with long image names |
Hi All,
I found that elog crashes if I try to upload an image with long name. It actually uploads the file after the crash. It crashes also if in the full view with attachments visible. If I shorten the name all is fine.
The crash report screenshot is attached. It looks like a too small buffer (?).
|
| Attachment 1: Screen_Shot.png
|
|
|
67340
|
Mon Sep 17 15:14:46 2012 |
 | Josef Uher | josef.uher@gmail.com | Question | All | 2.9.2 | Re: HTML editor |
| Andreas Luedeke wrote: |
|
| Josef Uher wrote: |
|
[...] maybe I missed something in the configuration, but how do I get this nice editor for HTML like the one available on this forum?[...]
|
The fckeditor is already installed with the elog package. All you need to do is to enable HTML in ELOG and Javascript in your browser.
The ELOG command "Allowed encoding = 7" gives you the same encoding choices as in this forum.
|
Hi Andreas, thank you for your reply. I have already found out that the problem on Mac was that I moved the cfg file to some other folder which did not contain the resources and scripts. I used the "-s" switch and now it works nicely. However, now I try to do the same thing on Windows and even the "-s" switch does not help (the default encodings etc. are set in the cfg file). I compiled the elog on Mac, but I used the installation package on Windows. |