This may be due to how I have my config file setup

Example:

Attributes = A, B
Options B = Please Select A
Options A = One{1}, Two{2}
{1} Options B = 1, 2,
{2} Options B = 3, 4,
 

Uppon closer inspection, removing the option to preset the secondary attribute as a Option list dosn't do anything for the find page.

This:

Attributes = A, B
Options A = One{1}, Two{2}
{1} Options B = 1, 2
{2} Options B = 3, 4

Still fails to set attribute B to a option list on  the find page. 

We have elog-2.7.5-1.i386 on SL 5

If I create an elog entry using the web interface, and include an inline image,  email is sent with a zero-length named attachment - the MIME header is present, but no content.

In the config file, Email Format = 47, though I also tried with format = 63.

Is this a bug that was fixed in a later version, or a configuration error (or a new bug) ?

Probably us not having ImageMagick installed. elog was able to attach pdf's, xpm's and xbm's to email, but not jpeg's or png's, though they inlined OK in HTML on the server.

It seems OK, I think, after installing ImageMagick and restarting.

Hi

I want to display an image on the title page and have put the following code into the elogd.cfg:

Welcome Title = <img src="pictures/ln2.jpg"><p><font size = 5 color=white>Welcome to My Project Log</font>

I have put the picture "ln2.jpg" in a pictures folder I have created in the root ELOG directory however the image does not show up. Any assistance would be great :)

Thanks in advance

Adam

While it is possible to print a logbook using the standard web browser print command in the Full or Summary view, a dedicated print function allowing the user to print out a hardcopy of a particular logbook would be very helpful.

Cheers

Adam

P.S. Thankyou for the response in elog:65671

I am in the process of setting up a new ELOG logbook.  I checked out rev2280 from svn.savannah.psi.ch.  I knew I wanted to encrypt passwords, so when I compiled, I used flags

USE_SSL=1

and

USE_CRYPT=1

I am running Red Hat enterprise linux 3, glibc-devel-2.3.2-95.50, openssl-devel-0.9.7a-33.25

Everything seemed to be working fine--I was able to set up logbooks using both a password file as well as write passwords and make entries to the logs.  Then I tried to use the command line 'elog' to make an entry which failed to both logbooks.

/opt/elog/pro/elogd -c /opt/elog/pro/dansce_fancy.cfg -l Demo1 -w <mypassword>

Would change the password in dansce_fancy.cfg and I could make entries through the web interface, but

elog -h acouture -s -p 8081 -w <mypassword> -l Demo1 -a Author="Aaron Couture" -a Type=Routine  -m Sampleinfo.txt -x -n 1

failed with

Error: Invalid user name or password

I got the same behaviour when I used a logbook with a user/password pair defined in a password file.

When I looked at the output from running elogd with the -v flag, I could see that everything was being received on the server side, but that the password did not agree with the write password in dansce_fancy.cfg

I then recompiled elog with

USE_SSL=1

USE_CRYPT=

And then the elog command line entries worked, both with write passwords and a password file (after recreating the password file and the write password).  Looking at the elog.c source code, it appears that it does not know to use crypt rather then base64_encode when USE_CRYPT is true.  elogd.c defined different behaviour if USE_CRYPT is defined.

Thanks,

Aaron Couture