Re: User/Admin privlege question, posted by Alexandre Camsonne on Fri Jul 2 15:18:20 2004
|
Hi,
I also have this problem, when a non admin user logs in he does not have access to
the config file but if he logs out he can then access the config file as non logged
user.
I also tried to upgrade to version 2.5.3 but running under this version does not ask
for passwords so I reverted to 2.5.2.
Besides these few details, your software is great !
Thank you,
Alexandre
> > 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 |
Re: User/Admin privlege question, posted by Stefan Ritt on Wed Jul 7 17:43:22 2004
|
> I also have this problem, when a non admin user logs in he does not have access to
> the config file but if he logs out he can then access the config file as non logged
> user.
If he logs out, how can he access a logbook at all? He should be presented a login
screen, nothing else...
> I also tried to upgrade to version 2.5.3 but running under this version does not ask
> for passwords so I reverted to 2.5.2.
Better first let's fix this problem. Under what circumstances does 2.5.3 not ask for
passwords? Maybe you can get the newest version from CVS (see download page) and try
again, I had problems when using the -DHAVE_CRYPT functionality, but I guess you did not
have that, do you?
So once you tried the latest snapshot, and still have problems, describe them carefully,
send me your configuration file, and I will have a look.
- Stefan |
An "options"-list starting with a " character is handled incorrectly , posted by Bartjan Wattel on Mon Jul 12 15:21:27 2004
|
An options list that starts with a double-quotes character (") is handled
incorrectly.
Try the line:
Options Student name = "Doe, John", "Foo, Bar".
The ELOG list will have four entries, namely:
- Doe
- John
- "
- Foo, Bar |
Re: An "options"-list starting with a " character is handled incorrectly , posted by Stefan Ritt on Mon Jul 12 15:54:11 2004
|
> Options Student name = "Doe, John", "Foo, Bar".
I fixed this bug. Please obtain the newest snapshot (see download page). |
'Full' mode gives incorrect results when searching, posted by Bartjan Wattel on Wed Jul 14 11:45:46 2004
|
Hi,
I was just searching your online discussion forum for entries with the
word 'password' in the subject. I noticed that the 'Full' option in
the 'full/summary/threaded' line displays the results of all entries in the
logbook, and not only the entries with the word 'password' in the subject.
I think there is an error in the URL, because when looking for the word
password in the subject, the URL for the 'Full' option is:
http://midas.psi.ch/elogs/Forum/page1?mode=full&reve&npp=8&Subject=password
If I change the word 'reve' in this URL to 'reversed=1', the results are
correct
Bartjan Wattel |
Re: 'Full' mode gives incorrect results when searching, posted by Stefan Ritt on Wed Jul 14 12:12:35 2004
|
Thanks for pointing out this bug. I fixed it. New version under CVS. |
Possible Formatting bug: Summary view, posted by Steve Jones on Wed Jul 14 22:52:18 2004
|
I've run into a situation where the SUMMARY view of a logbook will extend
beyond the righthand border, thus requiring the user to scroll right. This
does not occur in FULL or THREAD mode. Long lines in the TEXT attribute
appear to be "pushing" the display too far to the right. Limiting the
number of displayed summary lines works unless the first line is too long.
A temporary fix for this is to set summary lines = 0 |
Re: Possible Formatting bug: Summary view, posted by Stefan Ritt on Thu Jul 15 09:44:08 2004
|
> A temporary fix for this is to set summary lines = 0
Right, that's the only way. I would call this "permanent fix" (;-) |