Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 721 of 807  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Categorydown OS ELOG Version Subject
  68064   Tue Aug 4 13:18:26 2015 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux3.1.0-2Re: elogd crashes with a URL

I could not reproduce your problem. I can only fix it if I can reproduce it, so let's agree on a common test base. May I ask you to do the following:

  • Download the most recent elog version from bitbucket and compile it
  • Create two new logbooks "demo1" and "demo2" with minimal configuration, but using yor global password file which differs from the group ones
  • Send me step-by-step instructions how to trigger the problem, including your elogd.cfg file and your password files (of course with fake accounts)

If I can reproduce the crash, I can fix it.

Jaime Duran wrote:

URL causes elogd to crash when a global password file name doesn't match any group's password file name. 

The offending URL is copied from the address field of the browser after sorting a logbook by on of the fileds.

After login out and using the copied URL, elogd shows the authentication dialog and then crashes after the credentials are submited.

Some debugging point me to a NULL pointer on the following instruction in line   25502  of elogd.c :

  if (lbs->pwd_xml_tree) {

The work around was to name the global password file as the password file of one of the groups.

 

  68068   Tue Aug 4 13:57:28 2015 Reply Stefan Rittstefan.ritt@psi.chBug reportLinuxV3.1.1-f613012Re: Minor bug in the emails generated by elog.

Apostrophes are encoded as "'" inside the CKEditor used by elog, which sents the raw HTML text as email notification. You can test this by pressing the "Source" button at the top left menu in the CKEditor, then you see it. In my mail program (both Apple Mail and Thunderbird) this HTML enocding is correctly shown as the original apostroph, so I suspect that your mail program has an issue interpreting HTML encodings.

David Pilgram wrote:

In the emails generated by anyone making an entry in this log book, every apostrophe is followed by a semi-colon.  So the text "I don't think..."  appears in the email as "I don';t think...", and possibly that comment will appear in the email as "I don';;t think...." - not sure on the last bit.  It has been around in the past few versions of elog, but don't recall precisely when this started occurring.  It was fine back in February, with v2.9.2 (presumably) running.

 

Attachment 1: Screen_Shot_2015-08-04_at_14.01.09_.png
Screen_Shot_2015-08-04_at_14.01.09_.png
  68110   Wed Sep 2 20:23:21 2015 Entry Edmund Hertleedmund.hertle@kit.eduBug reportWindows3.1.1Attachment Uploaded Time is off by one hour

If I upload an attachment the timestamp of the attachment is set to one hour in the future, as demonstrated with this test attachment being one hour in the future compared to the entry time

Attachment 1: elogTest.rtf
{\rtf1\ansi\ansicpg1252\cocoartf1348\cocoasubrtf170
{\fonttbl\f0\fswiss\fcharset0 Helvetica;}
{\colortbl;\red255\green255\blue255;}
\paperw11900\paperh16840\margl1440\margr1440\vieww10800\viewh8400\viewkind0
\pard\tx566\tx1133\tx1700\tx2267\tx2834\tx3401\tx3968\tx4535\tx5102\tx5669\tx6236\tx6803\pardirnatural

\f0\fs24 \cf0 test}
  68113   Mon Sep 7 12:44:42 2015 Entry Edmund Hertleedmund.blomley@kit.eduBug reportAll3.1.1Creating ELog Links not working properly in HTML Editor

Hey,

the syntax for creating links to other elog entries has a small issue in the HTML editor. The link will not be created properly if there are whitespaces in the name of the logbook. Using ELCode (or in a simple attribute field) the whitespaces can be replaced by "+", but this does not work in the HTML editor. The work-around would be to use ELCode mark-up instead of HTML.

Example 1 (this should work): elog:Contributions/47

Example 2 (this will not work): elog:Config+Examples/11

Example 3 (will also not work): elog:Config%20Examples/11

  Draft   Wed Sep 16 01:27:20 2015  Joseph McKennajoseph.mckenna@cern.chBug reportLinux2.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 Question Joseph McKennajoseph.mckenna@cern.chBug reportLinux2.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


            

  Draft   Mon Sep 21 10:14:50 2015 Reply Edmund Hertleedmund.hertle@kit.eduBug reportLinux2.9.0(elogd)Re: elog client overwriting attached files when editing existing log

Hey,

I think this is a "problem" of the elog client, since it simply replaces the data. In most cases this is what you want, but since I wanted to have the option to append to the acutal message I built a function to first read-back the entry and add to the message instead of replacing it.

I just played around a bit and found that the attachments will be even disconnected, if you do not specify the -f parameter but just edit a different part of this entry.

A work-around for this is tricky. I tried to write to the "Attachment" attribute directly (-a "Attachment=Filename'), since then you coud read back the data first and manually add the filenames again. But this does not work.

Since the attachments are not actually removed, the only option I see is to modify the logbook file entry on the server by manually re-adding the filenames to the "Attachment: " line. But 

Joseph McKenna wrote:

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


            

 

  68118   Mon Sep 21 10:48:31 2015 Reply Edmund Hertleedmund.hertle@kit.eduBug reportLinux2.9.0(elogd)Re: elog client overwriting attached files when editing existing log

Hey,

I think this is a "problem" of the elog client, since it simply replaces the data. In most cases this is what you want, but since I wanted to have the option to append to the acutal message I built a function to first read-back the entry and add to the message instead of replacing it.

I just played around a bit and found that the attachments will be even disconnected, if you do not specify the -f parameter but just edit a different part of this entry.

A work-around for this is tricky. I tried to write to the "Attachment" attribute directly (-a "Attachment=Filename'), since then you coud read back the data first and manually add the filenames again. But this does not work.

Since the attachments are not actually removed, the only option I see is to modify the logbook file entry on the server by manually re-adding the filenames to the "Attachment: " line.

Joseph McKenna wrote:

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


            

 

ELOG V3.1.5-3fb85fa6