> the use of extendable options in the global section seem to "crash" elogd 
> when creating a new entry.
> My elogd.cfg is included
> the problem attribute is "Client"
> Should it be possible to have it extendable only in one specific logbook ?

Actually it was never foreseen to have extendable options in the [global]
section. I added now this functionality. The new windows version can be obtained
under

http://midas.psi.ch/elog/download/windows/elogd-snapshot.exe

Hi,

the use of extendable options in the global section seem to "crash" elogd 
when creating a new entry.
My elogd.cfg is included
the problem attribute is "Client"
Should it be possible to have it extendable only in one specific logbook ?

Are extendable and conditionnal "compatible" on the same set of attributes ?

Cheers,
Marc

> we've experienced a problem when using the safari browser to do a search in
> our elog. whenever you do a search, the logbook returns an error and the
> elog deamon crashes. when we first experienced this problem we were running
> version 2.3.9. however, an upgrade to version 2.5.2 doesn't seem to fix the
> problem. searches with other browsers (mozilla, internet explorer, ...) go
> off without a hitch.
> has anyone else observed a similar problem or have any ideas on how to
> resolve this issue.
> thanks for the help.

I finally found some time to address this problem. It was related to the way I
do the page redirection. The "Location:" in the HTTP header used a relative
path, although the standard requires an absolute (full) path, which I just
discovered. Although most browsers accept a relative path, the safari browser
obviously does not. 

I changed the redirection to absolute paths, the new version can be obtained
via CVS.

I implemented the feature to import the main entry text body from a CSV column labeled
"text". Please see the newest release
(http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.319) and let me know if this
works for you.

I had to add code to break apart long text bodies after 78 characters in order not to
get too long lines. Please note that the maximum body size in the CSV import is limited
to 500 characters.

> Is there any way to configure elog so that attribute fields can be edited 
> on more than line like the 'text' field? 
> 
> (This would be useful so that attributes could contain larger portions of 
> text including line breaks)

No, but this request is already on the wishlist
(http://midas.psi.ch/elog/wishlist.html) since some time. I added your vote.

> > However I'd like to import data from the CSV file, directly to the 'text' 
> > field, rather than just to one an attribute fields. Is it possible to do 
> > this?
> 
> Not yet, but I can implement it. Do you always have a column "text" in your
> CSV data or would you like to be able to select which column goes into the
> "text" field? Can you apend some sample CSV data so that I can have a look at it?

I've been trying an alternative approach which is basically to :

1. Import the data (not including the text field) into elog from a CSV file
2. Stop the elog server
3. Use a perl script to add each text entry to the appropriate record within the 
logbook file. 
(I.e. between the =============================== of the appropriate entry
and the next  '

Is there any way to configure elog so that attribute fields can be edited 
on more than line like the 'text' field? 

(This would be useful so that attributes could contain larger portions of 
text including line breaks)

thanks

Paul

> However I'd like to import data from the CSV file, directly to the 'text' 
> field, rather than just to one an attribute fields. Is it possible to do 
> this?

Not yet, but I can implement it. Do you always have a column "text" in your
CSV data or would you like to be able to select which column goes into the
"text" field? Can you apend some sample CSV data so that I can have a look at it?