ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
540
|
Tue May 11 11:18:24 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.5.2 | Re: Extendable options |
> The snapshot version you sent me seems to be locked onto port 80 and does not honor
> the port directive in elog.cfg....
Thank you, I fixed that and updated the file. |
539
|
Tue May 11 11:08:33 2004 |
| Marc Neiger | m.neiger@synergie-inf.com | Bug report | Windows | 2.5.2 | Re: Extendable options |
> > Is it possible to have a conditionnal attribute depend on an extendanble one ?
>
> In principle yes, but I never tried it...
The snapshot version you sent me seems to be locked onto port 80 and does not honor
the port directive in elog.cfg.... |
538
|
Tue May 11 10:44:55 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.5.2 | Re: Extendable options |
> Is it possible to have a conditionnal attribute depend on an extendanble one ?
In principle yes, but I never tried it... |
537
|
Tue May 11 10:42:44 2004 |
| Marc Neiger | m.neiger@synergie-inf.com | Bug report | Windows | 2.5.2 | Re: Extendable options |
Hi Stefan,
Many thanks, it works. I'm impressed by your reactivity ! thanks again.
Is it possible to have a conditionnal attribute depend on an extendanble one ?
> > 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 |
536
|
Mon May 10 21:57:49 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.5.2 | Re: Extendable options |
> 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 |
535
|
Mon May 10 00:00:06 2004 |
| Marc Neiger | m.neiger@synergie-inf.com | Bug report | Windows | 2.5.2 | Extendable options |
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 |
534
|
Wed May 5 17:38:12 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | | Linux | 2.5.2 | Re: safari browser issue |
> 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. |
533
|
Sat May 1 00:21:20 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Other | 2.5.2 | Re: CSV importing |
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. |