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.

elog running on a redhat 9 box
safari running on panther

> 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.

Hello,

For some reason if I define a "login user" that is allowed the configure
option he is also allowed to change the configuration file. According to the
documentation it seems like this should NOT be the case. Any ideas as to
what the problem might be? 

Thanks in advance for any help/advice.

Ralph 

> For some reason if I define a "login user" that is allowed the configure
> option he is also allowed to change the configuration file. According to the
> documentation it seems like this should NOT be the case. Any ideas as to
> what the problem might be? 

Unfortunately I cannot reproduce your problem. This leaves few possibilites:

- any login user CAN change his/her full name, email address etc. but only admin
users can change ALL OTHERS as well. Admin users should see a "change elogd.cfg"
button on the config page, whil normal users will not

- are you sure you logged out as admin user and loggin in again as non-admin
user? Under some circumstances, the browser keeps old cookies which can confuse
things. Best is if you delete all browser cookies and try again (Tools/Internet
Options/Delete Cookies in IE).

- Stefan

I'm trying to configure this thing to be able to filter on a set of 
criteria, choose select, choose toggle all, and then choose "Move to 
Complete Work Requests".

I've been able to select a specific logbook entry and move it, and I've 
been able to filter and select and toggle, but I can't figure out how to 
get the Move To option to show up on the main logbook menu....

what am I missing?

robin

> I've been able to select a specific logbook entry and move it, and I've 
> been able to filter and select and toggle, but I can't figure out how to 
> get the Move To option to show up on the main logbook menu....

To be able to move entries between logbooks, you have to enable the "move to"
command with the option "Menu commands" like:

Menu commands = Back, New, Edit, Delete, Reply, Find, Config, Move to, Help

Having done this, the menu "Move to xxx" should show up when you select an
individual entry, where xxx is the name of the other logbook(s). If you so a
"Select" on several entries, a new button should show up which lets you move
all selected entries to the other logbook(s). See elog:/1 for an example. If
you do not observer this behaviour, please let me know.

Hi Stefan 
YOu have been a great help on the Elog problem solving .
I have another sort of bug , when i have a attribute type as date.
And i have fixed the attribute on reply , i actually get a string of 
number when i reply , and the date becomes not the orginal date in the 
first message.

So the way i work ard is that i did not place the date field in the fixed  
attribute reply which i will run the risk of pple modifying that entry .
Can this be fix?

Thanks 

> Hi Stefan 
> YOu have been a great help on the Elog problem solving .
> I have another sort of bug , when i have a attribute type as date.
> And i have fixed the attribute on reply , i actually get a string of 
> number when i reply , and the date becomes not the orginal date in the 
> first message.
> 
> So the way i work ard is that i did not place the date field in the fixed  
> attribute reply which i will run the risk of pple modifying that entry .
> Can this be fix?

Yes, I fixed this. Revision 1.412 under CVS, new snapshot for Windows at the
download page.