Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
 Back  |  Find  |  Login  |  Help 
icon5.gif   elogd crash on sorting the entries by an datetime attribute, posted by stefano bonaldo on Thu Dec 15 11:12:09 2016 
    icon2.gif   Re: elogd crash on sorting the entries by an datetime attribute, posted by Stefan Ritt on Thu Dec 15 13:59:14 2016 Screen_Shot_2016-12-15_at_13.58.56_.png
       icon2.gif   Re: elogd crash on sorting the entries by an datetime attribute, posted by Stefano Bonaldo on Thu Dec 15 14:44:32 2016 
          icon2.gif   Re: elogd crash on sorting the entries by an datetime attribute, posted by Stefan Ritt on Fri Dec 16 09:27:26 2016 Screen_Shot_2016-12-16_at_9.26.51_.png
             icon2.gif   Re: elogd crash on sorting the entries by an datetime attribute, posted by Stefan Ritt on Fri Dec 16 09:55:20 2016 
                icon14.gif   Re: elogd crash on sorting the entries by an datetime attribute, posted by Stefano Bonaldo on Fri Dec 16 14:44:19 2016 
    icon2.gif   Re: elogd crash on sorting the entries by an datetime attribute, posted by Alan Grant on Thu Dec 15 15:42:06 2016 
       icon2.gif   Re: elogd crash on sorting the entries by an datetime attribute, posted by Stefano Bonaldo on Fri Dec 16 02:44:53 2016 
Message ID: 68508     Entry time: Thu Dec 15 15:42:06 2016     In reply to: 68502     Reply to this: 68509
Icon: Reply  Author: Alan Grant  Author Email: agrant@winnipeg.ca 
Category: Bug report  OS: Mac OSX  ELOG Version: 3.1.2 
Subject: Re: elogd crash on sorting the entries by an datetime attribute 

Hi Stefano.

This may or may not have anything to do with your specific problem but I notice you have the single word "date" as part of your attribute name and Date is actually a reserved word in Elog. Although your attribute is not exclusively called "date" I have found that even using "date" as an isolated word within an attribute name (eg: Record date vs Record_date) can cause some issues. In my case, it caused a problem with the elog client when trying to update records which was only resolved when I changed the name of the attribute to Date/Time Received from Date and Time Received. Long story short, I avoid using any reserved words as part of attribute names.

Alan.

stefano bonaldo wrote:

Hello,

I'm facing with a crash, which happen when I sort the entries by a datetime attribute (sort or rsort) and then i change the display mode from Full, Summary and Threaded.

For example, the elogd crashes when I try to connect from the Full display to Summary in sort mode. The issue presents for example by entering with the following URL:

http://host.name.com:8080/65+nm/?mode=summary&sort=Record+date

Can you please help me?

Here I reduced my elogd.cfg at minimum and I still get this issue:

[global]
port = 8080

[65 nm]
Attributes = Record date

Type Record date = datetime
Preset Record date = $date
List Display = Record date
Start page = ?sort=Record date

 

ELOG V3.1.5-3fb85fa6