Re: Elog crashes with null Username, posted by Xuan Wu on Fri Apr 21 08:19:05 2017
|
No, We are using the released version 3.1.2
How to use the current git revision or is it a long time to wait for the next release?
| Alan Grant wrote: |
|
Are you using the current git revision Xuan?
| Xuan Wu wrote: |
|
We also meet this issue occasionally, so how can we get rid of this?
| Stefan Ritt wrote: |
|
Ups. This bug must have lingered there since the beginning of time. Funny that nobody noticed in the last ten years or so. I have fixed it in the current git revision.
| Alan Grant wrote: |
|
I haven't found any reporterd issues in the forum similar yet, but it appears there is a bug in Elog when logging into logbooks. If I leave Username and Password null and click Submit the daemon crashes. We've been having this problem off and on and after some verbose logging level 3 I was drawn to these recurring lines in the log:
16-Dec-2016 18:20:22 [172.23.113.4] {SER Reports} LOGIN user "" (attempt)
16-Dec-2016 23:15:52 [] Server listening on port 8080 ..
16-Dec-2016 23:18:05 [172.23.113.4] {Daily Request Log} LOGIN user "dmorrison" (attempt)
|
|
|
|
|
|
Re: Elog crashes with null Username, posted by Xuan Wu on Fri Apr 21 12:18:57 2017
|
Awesome！It's appreciated. Many Thanks!
| Stefan Ritt wrote: |
|
I made a new release for you 3.1.3
| Xuan Wu wrote: |
|
No, We are using the released version 3.1.2
How to use the current git revision or is it a long time to wait for the next release?
| Alan Grant wrote: |
|
Are you using the current git revision Xuan?
| Xuan Wu wrote: |
|
We also meet this issue occasionally, so how can we get rid of this?
| Stefan Ritt wrote: |
|
Ups. This bug must have lingered there since the beginning of time. Funny that nobody noticed in the last ten years or so. I have fixed it in the current git revision.
| Alan Grant wrote: |
|
I haven't found any reporterd issues in the forum similar yet, but it appears there is a bug in Elog when logging into logbooks. If I leave Username and Password null and click Submit the daemon crashes. We've been having this problem off and on and after some verbose logging level 3 I was drawn to these recurring lines in the log:
16-Dec-2016 18:20:22 [172.23.113.4] {SER Reports} LOGIN user "" (attempt)
16-Dec-2016 23:15:52 [] Server listening on port 8080 ..
16-Dec-2016 23:18:05 [172.23.113.4] {Daily Request Log} LOGIN user "dmorrison" (attempt)
|
|
|
|
|
|
|
about attachment, posted by Xuan Wu on Fri Jan 12 09:54:41 2018
|
Hi all,
Some elog users of our site(CSNS) mentioned some advice about attachment:
1.Can imagemagick create thumbnail for .bmp file now?
2.Can re-sort the attachments after attachments uploaded by dragging or clicking up/down arrow or anything except deleting and re-upload attachment again?
3.Can add some description under the thumbnail of uploaded attachment? I've suggested them adding the description to the name of attchment or writing the detail in the text area. They are seem not very satisfied with this solution.
Any advice and suggestion will be appreciated.
Cheers |
about shiftcheck, posted by Xuan Wu on Tue May 15 04:41:23 2018 
|
Hi all,
I try to implement a shift check list for our facility. The attributes called "a1, a2, b1, b2 etc" are used in original shiftcheck.html， However, we would like to use "1.1, 1.2, 2.1, 2.2 etc". So I try to change the name of checkbox in shiftcheck.html and the attributes in elogd.cfg file to "1.1, 1.2, 2.1, 2.2 etc". The elog web page can display the attributes like "1.1, 1.2...", but the checked value of "on" seems not working. And I have used wirshark to monitor the http package, the request message seems correct, but the service response seems can't deal with attributes like "1.1, 1.2...", so is there a way to work around? |
|
Re: about shiftcheck, posted by Xuan Wu on Wed May 16 02:20:24 2018
|
That's true. Thanks for your explanation.
Cheers, Xuan
| Andreas Luedeke wrote: |
|
An attribute is similar to a variable. Do you know any programming language that allows to start a variable with a digit? I don't.
The solution is very obvious: start your attributes with a letter.
Cheers, Andreas
| Xuan Wu wrote: |
|
Hi all,
I try to implement a shift check list for our facility. The attributes called "a1, a2, b1, b2 etc" are used in original shiftcheck.html， However, we would like to use "1.1, 1.2, 2.1, 2.2 etc". So I try to change the name of checkbox in shiftcheck.html and the attributes in elogd.cfg file to "1.1, 1.2, 2.1, 2.2 etc". The elog web page can display the attributes like "1.1, 1.2...", but the checked value of "on" seems not working. And I have used wirshark to monitor the http package, the request message seems correct, but the service response seems can't deal with attributes like "1.1, 1.2...", so is there a way to work around?
|
|
|
|
shiftcheck restrict edit, posted by Xuan Wu on Thu May 24 08:53:50 2018
|
Hi all,
There are options "Restrict edit" and "Restrict edit time" for general logbooks, but it seems not work for shiftcheck logbook. I think the function only author can change their own entry is necessary for shiftcheck too. Any suggestion would be hightly appreciated.
Cheers,
Xuan |
|
Re: shiftcheck restrict edit, posted by Xuan Wu on Wed Jun 6 02:41:32 2018
|
Is there a way to restrict other author to edit the custom input form submitted?
| Xuan Wu wrote: |
|
Hi all,
There are options "Restrict edit" and "Restrict edit time" for general logbooks, but it seems not work for shiftcheck logbook. I think the function only author can change their own entry is necessary for shiftcheck too. Any suggestion would be hightly appreciated.
Cheers,
Xuan
|
|
elog hanged when uploading photo failed, posted by Xuan Wu on Wed Feb 27 02:34:46 2019
|
Hi all,
We came across a problem recently when clicking "Upload" button, then elog hanged and never being accessed. I have checked the elog logs and find that it seems that elog didn't get the path of the picture for some reason. So is it a bug or our operation isn't correct? |
|