Hello users,

When I configure an attribute with "Type <attribute>= date", in the new entry form a clic on the calendar symbol does nothing.

Reading the source code I see it's trying to open a window named "cal.html" through javascript (function opencal) but this file doesn't exist anywhere in source elog files.

Thanks

Just last week I've downloaded the latest version of ELOG, compiled and installed it, and the date picker just works fine.

In my case it was an update of an existing installation. Can you provide a bit more information about your case: I guess it was a first time installation? Was is ELOG V3.1.2-754330e or a different GIT version?

Stefan, could you please add an attribute of type "datetime" and "date" to one of the demo logbooks? Currently there is non. Maybe to elog:Database? Then we can check if it is a client problem.

Cheers, Andreas

What is the input format expected by the elog client for a required Datetime defined field when inserting a record? (Eg: October 26, 2016 = ? in the field's data parameter).

I have read some prior posts on this and the indication is that the input needs to use epoch time, however even when I enter 1477493161 or 0 the client still flags the variable data as missing. If this is in fact the format I shoud be using then I can provide a sample input and output message to illustrate my problem.

UPDATE:

As I continue to test and troubleshoot this problem I noticed something peculiar: the Datetime defined field that the client is rejecting when I attempt a record insert is listed as a Required attribute. However, when I just remove it from the Required list the record including the epoch time is inserted without any problems.

I am now unsure if my configuration is deficient somewhere, vs a problem with the client program code.

Hi Alan,

I have no idea if this helps but the Date and Time formats in the config file internally interconnect, as I discovered in trying to define them separately.  Define one, and the other is defined.

I only mention this as I spent some hours trying to sort out the issue, only to learn it was a "feature" that Stefan didn't want to correct as it may affect too many others.  I can understand that, and made a different solution to what I wanted to do.

UPDATE:

As I continue to test and troubleshoot this problem I noticed something peculiar: the Datetime defined field that the client is rejecting when I attempt a record insert is listed as a Required attribute. However, when I just remove it from the Required list the record including the epoch time is inserted without any problems.

I am now unsure if my configuration is deficient somewhere, vs a problem with the client program code.

Hi,

I have been using ELOG for a while and I love it.  It is a default installation on Debian Lenny and ELOG 2.7.8.  I am having problems with the deamon script, I can stop the service by doing /etc/init.d/elog stop but I can't started.  When I do /etc/init.d/elog start I get this error: "Starting ELOG daemon: elogdCannot open "elogd.cfg": No such file or directory"

Somewhere there is a bad path to the elogd.cfg which is in "/usr/local/elog"

I would appreciate any help I can get.

Thank you.

Here is the scrip:

[code]

#!/bin/sh
# Init script for ELOG.
# Recai Oktas <roktas@omu.edu.tr>

PATH=/sbin:/bin:/usr/sbin:/usr/local/bin
DAEMON=/usr/local/sbin/elogd
NAME=elogd
DESC="ELOG daemon"

# Always run as daemon.
ARGS="-D"

# Admin might change some command line options without touching this script.
if [ -f /etc/default/elog ]; then
        . /etc/default/elog
fi

test -f $DAEMON || exit 0

set -e

case "$1" in
        start)
                echo -n "Starting $DESC: $NAME"
                start-stop-daemon --start --quiet --pidfile /var/run/$NAME.pid \
                        --exec $DAEMON -- $ARGS >/dev/null
                echo "."
                ;;
        stop)
                echo -n "Stopping $DESC: $NAME"
                start-stop-daemon --oknodo --stop --quiet --pidfile /var/run/$NAME.pid \
                        --exec $DAEMON -- $ARGS >/dev/null
                echo "."
                ;;
        reload)
                # Do nothing since ELOG daemon responds to
                # the changes in conffile directly.
                ;;
        restart|force-reload)
                echo -n "Restarting $DESC: $NAME"
                start-stop-daemon --stop --quiet --pidfile \
                        /var/run/$NAME.pid --exec $DAEMON -- $ARGS >/dev/null
                sleep 1
                start-stop-daemon --start --quiet --pidfile \
                        /var/run/$NAME.pid --exec $DAEMON -- $ARGS >/dev/null
                echo "."
                ;;
        *)
                N=/etc/init.d/$NAME
                echo "Usage: $N {start|stop|restart|reload|force-reload}" >&2
                exit 1
                ;;
esac

exit 0

[/code]