Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 780 of 806  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
    icon2.gif   Re: Export entries to XLS or CSV?, posted by Andreas Luedeke on Thu Jul 4 15:27:13 2013 elog-2.9.2-2481_cvs3patch.diff

Jim Tinlin wrote:

Stefan Ritt wrote:

Andreas Luedeke wrote:

 

Yes, you're right: the text field is only exported in XML and Raw mode.
It is questionable how EXCEL should cope with HTML or ELCode output from the text fields.
But I admit that this would be a useful feature for logbooks that only use plain text entries. And it is simple to implement.
 
I've attached a patch to elogd.c from elog-2.9.2-2081 that adds a third CVS mode 'CSV (";" separated) + Text'.
(This string has not yet been added to the localization.)
As far as I've tested it works fine to import the text to OpenOffice and EXCEL, even with multiple text lines and HTML code in the text.
Of course the spreadsheet programs just display the HTML source.
 
Stefan, do you think this should be added to the official branch? 
Detect language » English
 
 
Detect language » English
 

Hi Jim, can you confirm that this works for you? If so, I'm willing to incorporate the patch into the distribution. 

 Has this been added yet?

I don't have the means to create an executable for Windows, if someone does I can give it a try...it sounds/looks like it will work.

Thanks!

Hi Jim, I've incorporated the patch to our production server about a week ago.
I've agreed with Stefan that he'll add it, when it proved to run stable for a while.
Until now it appears to work fine. I think Stefan will add it to the distribution soon.
But I won't touch any Windows systems, you'll need to wait for someone else to compile it for you.
Maybe some skilled Windows user want to give it a try: i've attached the changes in the elogd.c file from v2.9.2-2481,
the modified file can be currently downloaded from http://people.web.psi.ch/luedeke/public/tmp/elogd.c
 
Detect language » English
 

Andreas

 
Detect language » English
 
 
Detect language » English
 
 
Detect language » English
 
    icon2.gif   Re: Export entries to XLS or CSV?, posted by Stefan Ritt on Fri Feb 21 13:25:55 2014 

Andreas Luedeke wrote:

Jim Tinlin wrote:

Stefan Ritt wrote:

Andreas Luedeke wrote:

 

Yes, you're right: the text field is only exported in XML and Raw mode.
It is questionable how EXCEL should cope with HTML or ELCode output from the text fields.
But I admit that this would be a useful feature for logbooks that only use plain text entries. And it is simple to implement.
 
I've attached a patch to elogd.c from elog-2.9.2-2081 that adds a third CVS mode 'CSV (";" separated) + Text'.
(This string has not yet been added to the localization.)
As far as I've tested it works fine to import the text to OpenOffice and EXCEL, even with multiple text lines and HTML code in the text.
Of course the spreadsheet programs just display the HTML source.
 
Stefan, do you think this should be added to the official branch? 
Detect language » English
 
 
Detect language » English
 

Hi Jim, can you confirm that this works for you? If so, I'm willing to incorporate the patch into the distribution. 

 Has this been added yet?

I don't have the means to create an executable for Windows, if someone does I can give it a try...it sounds/looks like it will work.

Thanks!

Hi Jim, I've incorporated the patch to our production server about a week ago.
I've agreed with Stefan that he'll add it, when it proved to run stable for a while.
Until now it appears to work fine. I think Stefan will add it to the distribution soon.
But I won't touch any Windows systems, you'll need to wait for someone else to compile it for you.
Maybe some skilled Windows user want to give it a try: i've attached the changes in the elogd.c file from v2.9.2-2481,
the modified file can be currently downloaded from http://people.web.psi.ch/luedeke/public/tmp/elogd.c
 
Detect language » English
 

Andreas

 
Detect language » English
 
 
Detect language » English
 
 
Detect language » English
 

This patch is now officially in the GIT repository. 

icon4.gif   POODLE vulnerability, posted by Stefan Ritt on Fri Oct 24 12:51:00 2014 elogd.patch

IMPORTANT SECURITY ANNOUNCEMENT

Recently the POODLE vulnerability has been announced: http://en.wikipedia.org/wiki/POODLE 

ELOG is prone to this vulnerability if it runs directly the SSL protocol and can be accessed from the internet. If ELOG runs behind an Apache proxy, and the Apache server has been correctly configured (disabled the SSLv23 protocols), ELOG is safe as well.

To fix this vulnerability, ELOG needs to be recompiled after the attached patch has been applied. This prohibits ELOG to fallback to the insecure SSLv2 & v3 protocols and only use the safe TLSv1 protocol.

If you do not know how to recompile ELOG, please do not run ELOG directly accessible from the internet until the next binary release has been published.

/Stefan Ritt

icon4.gif   parse a correctly the username in save_user_config when using Webserver authentication, posted by Christof Hanke on Wed May 6 15:13:11 2015 parse_http_user_correctly.patch

Hi Stefan,

 

When we use Webserver authentication, we have the correct username already in the variable http_user.

The old way of copying this http_user to "user" is wrong since we don't use the size of http_user.

Instead, just encode the http_user variable directly.

See attached patch against git HEAD.

Christof

 

    icon2.gif   Re: parse a correctly the username in save_user_config when using Webserver authentication, posted by Stefan Ritt on Tue Jun 9 15:44:49 2015 

Hi Christof,

thanks for the patch, I merged it into the current HEAD.

/Stefan

Christof Hanke wrote:

Hi Stefan,

 

When we use Webserver authentication, we have the correct username already in the variable http_user.

The old way of copying this http_user to "user" is wrong since we don't use the size of http_user.

Instead, just encode the http_user variable directly.

See attached patch against git HEAD.

Christof

 

 

icon5.gif   Draft saved is treated as an entry edit, posted by Daniel Sajdyk on Fri Aug 28 21:01:42 2015 entry.png

Hello.

In Elog i have attribute called "Zmieniano" (eng. changed)  which should store how many times entry was edited. If entry was not edited it should have only preset value "oryginalny wpis" (eng. oryginal entry), but when I edit it, it should have also date, time, and person who make edit (this is made by "Subst on Edit Zmieniano = $Zmieniano<br>- Zmiana $date przez $long_name z $remote_host)". 

From version V3.1.1-3f311c5 I have problem with that. 

When I add entry, and entry is auto saved, then auto save is shown in the attribute "Zmieniano" (eng. changed) as an next edit, which I dont want. Entry from attached screenshot was not edited, but in "Zmieniano" (eng. changed) attributes it has two values:

  • Oryginalny wpis (eng. oryginal entry),
  • Zmiana 27.08.2015, 10:52 przez Daniel Sajdyk z serwerownia.sr.lez (eng. Changed 27.08.2015.... ) 

The second value is autosave time. 

Is this a bug?

 

Regards

Daniel. 

 

    icon2.gif   Re: Draft saved is treated as an entry edit, posted by Andreas Luedeke on Mon Aug 31 09:38:38 2015 

Hi Daniel,

this is an undesired side effect of a new feature. I wouldn't call it a bug ;-)

There is no straight forward way for elog to distinguish between a "Submit" and an automatic save. Therefore the "... on edit = ..." kicks in when an entry is saved automatically.

I guess Stefan can figure out a workaround, but for the moment I would sugest that you just switch off the auto save feature -- if you want to keep your save history:

Save drafts = 0

Cheers
Andreas
 
Daniel Sajdyk wrote:Save drafts = 0

Hello.

In Elog i have attribute called "Zmieniano" (eng. changed)  which should store how many times entry was edited. If entry was not edited it should have only preset value "oryginalny wpis" (eng. oryginal entry), but when I edit it, it should have also date, time, and person who make edit (this is made by "Subst on Edit Zmieniano = $Zmieniano<br>- Zmiana $date przez $long_name z $remote_host)". 

From version V3.1.1-3f311c5 I have problem with that. 

When I add entry, and entry is auto saved, then auto save is shown in the attribute "Zmieniano" (eng. changed) as an next edit, which I dont want. Entry from attached screenshot was not edited, but in "Zmieniano" (eng. changed) attributes it has two values:

  • Oryginalny wpis (eng. oryginal entry),
  • Zmiana 27.08.2015, 10:52 przez Daniel Sajdyk z serwerownia.sr.lez (eng. Changed 27.08.2015.... ) 

The second value is autosave time. 

Is this a bug?

 

Regards

Daniel. 

 

 

    icon2.gif   Re: Draft saved is treated as an entry edit, posted by Daniel Sajdyk on Mon Aug 31 13:12:09 2015 

Hi Andreas and thank you very much for explanation ;)

So, we'll have to wait for new version which will correct this.

 

Cheers

Daniel.

Andreas Luedeke wrote:

Hi Daniel,

this is an undesired side effect of a new feature. I wouldn't call it a bug ;-)

There is no straight forward way for elog to distinguish between a "Submit" and an automatic save. Therefore the "... on edit = ..." kicks in when an entry is saved automatically.

I guess Stefan can figure out a workaround, but for the moment I would sugest that you just switch off the auto save feature -- if you want to keep your save history:

Save drafts = 0

Cheers
Andreas
 
Daniel Sajdyk wrote:Save drafts = 0

Hello.

In Elog i have attribute called "Zmieniano" (eng. changed)  which should store how many times entry was edited. If entry was not edited it should have only preset value "oryginalny wpis" (eng. oryginal entry), but when I edit it, it should have also date, time, and person who make edit (this is made by "Subst on Edit Zmieniano = $Zmieniano<br>- Zmiana $date przez $long_name z $remote_host)". 

From version V3.1.1-3f311c5 I have problem with that. 

When I add entry, and entry is auto saved, then auto save is shown in the attribute "Zmieniano" (eng. changed) as an next edit, which I dont want. Entry from attached screenshot was not edited, but in "Zmieniano" (eng. changed) attributes it has two values:

  • Oryginalny wpis (eng. oryginal entry),
  • Zmiana 27.08.2015, 10:52 przez Daniel Sajdyk z serwerownia.sr.lez (eng. Changed 27.08.2015.... ) 

The second value is autosave time. 

Is this a bug?

 

Regards

Daniel. 

 

 

 

ELOG V3.1.5-3fb85fa6