| Steve Jones wrote: | Stefan, not a problem. ITMT, any idea how I can manually clear this "lock"? Is it embedded in the logbook itself?
| Stefan Ritt wrote: | Sorry about my unusual slow response, but I'm pretty busy these days. I hope I will be able to address this problem in a two weeks from now.
| Steve Jones wrote: | Stefan, any ideas on this problem?
| Quote: | Our eLog is set to create logbook entry locks and after 30minutes prevent one from re-editing an entry, thus forcing a REPLY to be created.
SCENARIO: When an *attempt* is made to edit a logbook after the 30minute timer, one gets the message that EDITING is prevented and to use the browser "Back" button.
PROBLEM: The display now shows that particular entry to be locked, even though the attempt to edit was blocked. It appears that the lock flag is set prior to the "Edit" attempt being blocked and thus the lock flag is never "unset". |
|
|
|
|
1173
|
Sat Jun 4 12:21:21 2005 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.5.9 | Re: reverse sort option does not work for quick filter |
| Heiko Scheit wrote: | The 'reverse sort' option does not work for quick filter searches. In the
URL there is always written 'reverse=0'. For normal 'Find' it works OK. |
I don't understand the problem. If I take the example elogd.cfg from the distribution, it sorts in reverse order, since the file contains Reverse sort=1. If I apply a quick filter, the result is still sorted in reverse order (entry ID from high to low). If I set Reverse sort=0, the even after applying a quick filter, the entries are sorted with their ID from low to high. Applying a quick filter should not put a reverse=0 into the URL, so it's strange to me where this comes from. Can you try to reproduce the problem with the demo elogd.cfg? |
|
1174
|
Sat Jun 4 12:25:57 2005 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.5.9 | Re: elog crashes when admin tries to register new users |
| Heiko Scheit wrote: | When pasting the URL for the registration of new users (with 'Self register = 3') elog
crashes with segmentation fault. I don't have the time currently to give you more
debuging information but maybe you can have a look the same. It crashes after
the user is registered. The Email is sent, too. |
I cannot reproduce this problem either. The only difference I see is that I use thunderbird as my email client, where I don't have to copy/paste the activation URL into my browser, but just click on it. If maybe the copy/paste operation adds an additional CR/LF or so, that could be a problem. Can you check again? A stack trace of the crashed elogd would help as well. |
|
1175
|
Sat Jun 4 13:06:08 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | 2.5.9 | Re: Logbook locking issue |
| Steve Jones wrote: | | Stefan, not a problem. ITMT, any idea how I can manually clear this "lock"? Is it embedded in the logbook itself? |
I would recommend to remove the Restrict edit time = 0.5 temporarily from your config file, then edit this entry, the clicking Back instead of Submit (since you don't really want to edit the entry). This removes the lock, and you can re-enable the Restrict edit time = 0.5 in the config file.
| Quote: | Our eLog is set to create logbook entry locks and after 30minutes prevent one from re-editing an entry, thus forcing a REPLY to be created.
SCENARIO: When an *attempt* is made to edit a logbook after the 30minute timer, one gets the message that EDITING is prevented and to use the browser "Back" button.
PROBLEM: The display now shows that particular entry to be locked, even though the attempt to edit was blocked. It appears that the lock flag is set prior to the "Edit" attempt being blocked and thus the lock flag is never "unset". |
I fixed this problem and committed it to CVS. It will be contained in the next release. |
|
1177
|
Sat Jun 4 16:37:04 2005 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Bug report | Linux | 2.5.9 | Re: reverse sort option does not work for quick filter | [quote="Stefan Ritt"][quote="Heiko Scheit"]The 'reverse sort' option does not work for quick filter searches.
In the
URL there is always written 'reverse=0'. For normal 'Find' it works OK.[/quote]
I don't understand the problem. If I take the example elogd.cfg from the distribution, it sorts in reverse
order, since the file contains [i]Reverse sort=1[/i]. If I apply a quick filter, the result is still sorted in
reverse order (entry ID from high to low). If I set [i]Reverse sort=0[/i], the even after applying a quick
filter, the entries are sorted with their ID from low to high. Applying a quick filter should not put a
[i]reverse=0[/i] into the URL, so it's strange to me where this comes from. Can you try to reproduce the problem
with the demo elogd.cfg?[/quote]
I played with the quick filter settings somewhat. Here is what I get.
I can't really make sense of it, but maybe you can figure out what
happens. Below, the first line always contains the 'Quick filter'
config setting. The lines below show the URL after searching with the
quick filter for the 1st, 2nd,... attribute listed in the quick filter
setting. (The common base of the URL was removed. Shown is
everything after the last '/'.) Each 'quick search' was started from
the 'List' or 'Back' page, i.e. the URL ended with a '/'.
As you can see below the result depends on the number and on the order
(!) of the attributes. Only a few give the desired result (marked
with # OK). Incidentally the option 'Date, Something' works fine,
which is the combination found in the demo config file. :)
Quick filter = Subject, Date, Login
?Subject=sd&Login= # OK
?last=1&&reverse=0
?Login=sdf&reverse=0
Quick filter = Subject, Login, Date
?Subject=scd&reverse=0
?Login=sdf&reverse=0
?last=1&reverse=0
Quick filter = Date, Subject, Login
?last=1&&reverse=0
?Subject=sd&Login= # OK
?Login=sd&reverse=0
Quick filter = Subject, Date
?Subject=sd # OK
?last=1&reverse=0
Quick filter = Date, Subject
?last=1&Subject= # OK
?Subject=ddsd # OK
Quick filter = Login, Date
?Login=sch # OK
?last=31&reverse=0
Quick filter = Subject, Login
?Subject=dsd&Login= # OK
?Login=sd&reverse=0
Quick filter = Login, Subject
?Login=sd&Subject= # OK
?Subject=sd&reverse=0 |
|
1189
|
Thu Jun 9 15:20:04 2005 |
| Heiko Scheit | h.scheit@mpi-hd.mpg.de | Bug report | Linux | 2.5.9 | Re: elog crashes when admin tries to register new users |
| Stefan Ritt wrote: |
| Heiko Scheit wrote: | When pasting the URL for the registration of new users (with 'Self register = 3') elog
crashes with segmentation fault. I don't have the time currently to give you more
debuging information but maybe you can have a look the same. It crashes after
the user is registered. The Email is sent, too. |
I cannot reproduce this problem either. The only difference I see is that I use thunderbird as my email client, where I don't have to copy/paste the activation URL into my browser, but just click on it. If maybe the copy/paste operation adds an additional CR/LF or so, that could be a problem. Can you check again? A stack trace of the crashed elogd would help as well. |
The following appended after the base (!) URL results in a segmentation fault
?cmd=Activate&new_user_name=test1&new_full_name=Test1
It works fine, if a specific logbook is given. So
http://my.ho.st/?cmd=Activate&new_user_name=test1&new_full_name=Test1
is not OK, while
http://my.ho.st/myLogBook/?cmd=Activate&new_user_name=test1&new_full_name=Test1
is OK. |
|
1195
|
Thu Jun 16 22:37:06 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.5.9 | Re: reverse sort option does not work for quick filter | | I finally found some time to fix this problem. The fix is under CVS. |
|
1198
|
Fri Jun 17 22:33:29 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.5.9 | Re: elog crashes when admin tries to register new users |
Thanks for that info. It helped me debugging things. The problem is that the "activation" URL does not contain a logbook if there is a global password file. I have never tried that so of course it crashes 
I tried to fix this and committed the changes to CVS. Can you try with that version? |
|