ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
68738
|
Wed Feb 7 14:26:01 2018 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | V3.1.2-bd75964 | Re: Entries disappear after editing + UTF16 problem | Tell me your current seven digit number and I can check if your version is too old.
Peter K wrote: |
yes, that is exactly where I got this V3.1.2-bd75964 version!
Do you recommend to download it again from your site and compile?
Stefan Ritt wrote: |
The -bd... number must be from the .apk package, which I don't have control over. You have to check the elog git hash code. You see it at the bottom of each elog web page. For this forum server, it's ELOG V3.1.2-7933898 with 7 digit number at the end.
Peter K wrote: |
We installed our elog from .apk in November 2017.
Version V3.1.2-bd75964
I suppose it already contains List drafts feature.
Stefan Ritt wrote: |
You might have to update to the current elog version. This feature was implemented in Dec. 2016.
Stefan
Peter K wrote: |
Dear Stefan,
Thanks for quick reply.
I checked List drafts = 1 in config file - it does not show drafts in the list in my case.
Can it be blocked by any other option?
I have these options enabled:
Use Lock = 1
Save drafts = 1
List drafts = 1
Peter.
Stefan Ritt wrote: |
The message is not lost, but becomes a "draft". This works similar in most email systems. When you edit an email and son't send it, it stays in your "draft" email folder and does not show up in your "sent" folder. Same here. You are suppost to "submit" you entry, the "save" is just a temporary safety backup. If you do not submit (if you press BACK or your browser crashes), the entry is not submitted to the system, but stays around as a draft. If you create a new message, the system asks you to edit and finish your draft, so that it does not get lost. So always hit "submit" if you are finished editing a message, not just "save".
If you want to see the draft message, they are rendered in red in the normal message list if you have
List drafts = 1
in your config file. No ide where your cluttering comes from.
Stefan
Peter K wrote: |
I found a sequence which hides the message from the list.
In addition this sequence corrupts UTF encoding of the text.
- create new message
- submit it
- Edit this message again
- click SAVE and then exit the editor (click Logbook name in the header or BACK in the browser)
- message disappeared from the list!
- by clicking NEW message I found my lost one in the drafts, but all text was corrupted.
I've made small GIF presentation on this issue (attached, open in new window), may be this helps.
|
|
|
|
|
|
|
|
68739
|
Wed Feb 7 15:28:47 2018 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug report | Linux | V3.1.2-bd75964 | Re: Entries disappear after editing + UTF16 problem | Hi Stefan,
I think there is a misunderstanding: there is an ELOG commit with the GIT ID bd75964.
It is from Sep. 2016, so: Peter, you should download a newer version.
Cheers
Andreas
https://bitbucket.org/ritt/elog/commits/all?search=bd75964
Stefan Ritt wrote: |
Tell me your current seven digit number and I can check if your version is too old.
Peter K wrote: |
yes, that is exactly where I got this V3.1.2-bd75964 version!
Do you recommend to download it again from your site and compile?
Stefan Ritt wrote: |
The -bd... number must be from the .apk package, which I don't have control over. You have to check the elog git hash code. You see it at the bottom of each elog web page. For this forum server, it's ELOG V3.1.2-7933898 with 7 digit number at the end.
Peter K wrote: |
We installed our elog from .apk in November 2017.
Version V3.1.2-bd75964
I suppose it already contains List drafts feature.
Stefan Ritt wrote: |
You might have to update to the current elog version. This feature was implemented in Dec. 2016.
Stefan
Peter K wrote: |
Dear Stefan,
Thanks for quick reply.
I checked List drafts = 1 in config file - it does not show drafts in the list in my case.
Can it be blocked by any other option?
I have these options enabled:
Use Lock = 1
Save drafts = 1
List drafts = 1
Peter.
Stefan Ritt wrote: |
The message is not lost, but becomes a "draft". This works similar in most email systems. When you edit an email and son't send it, it stays in your "draft" email folder and does not show up in your "sent" folder. Same here. You are suppost to "submit" you entry, the "save" is just a temporary safety backup. If you do not submit (if you press BACK or your browser crashes), the entry is not submitted to the system, but stays around as a draft. If you create a new message, the system asks you to edit and finish your draft, so that it does not get lost. So always hit "submit" if you are finished editing a message, not just "save".
If you want to see the draft message, they are rendered in red in the normal message list if you have
List drafts = 1
in your config file. No ide where your cluttering comes from.
Stefan
Peter K wrote: |
I found a sequence which hides the message from the list.
In addition this sequence corrupts UTF encoding of the text.
- create new message
- submit it
- Edit this message again
- click SAVE and then exit the editor (click Logbook name in the header or BACK in the browser)
- message disappeared from the list!
- by clicking NEW message I found my lost one in the drafts, but all text was corrupted.
I've made small GIF presentation on this issue (attached, open in new window), may be this helps.
|
|
|
|
|
|
|
|
|
68740
|
Thu Feb 8 15:09:42 2018 |
| Peter K | pkravt@gmail.com | Bug report | Linux | V3.1.2-bd75964 | Re: Entries disappear after editing + UTF16 problem | Dear Stefan and Andreas,
We have updated our elog to V3.1.3-7933898, now I see the drafts in the list!
Thanks a lot for your help!
Andreas Luedeke wrote: |
Hi Stefan,
I think there is a misunderstanding: there is an ELOG commit with the GIT ID bd75964.
It is from Sep. 2016, so: Peter, you should download a newer version.
Cheers
Andreas
https://bitbucket.org/ritt/elog/commits/all?search=bd75964
Stefan Ritt wrote: |
Tell me your current seven digit number and I can check if your version is too old.
Peter K wrote: |
yes, that is exactly where I got this V3.1.2-bd75964 version!
Do you recommend to download it again from your site and compile?
Stefan Ritt wrote: |
The -bd... number must be from the .apk package, which I don't have control over. You have to check the elog git hash code. You see it at the bottom of each elog web page. For this forum server, it's ELOG V3.1.2-7933898 with 7 digit number at the end.
Peter K wrote: |
We installed our elog from .apk in November 2017.
Version V3.1.2-bd75964
I suppose it already contains List drafts feature.
Stefan Ritt wrote: |
You might have to update to the current elog version. This feature was implemented in Dec. 2016.
Stefan
Peter K wrote: |
Dear Stefan,
Thanks for quick reply.
I checked List drafts = 1 in config file - it does not show drafts in the list in my case.
Can it be blocked by any other option?
I have these options enabled:
Use Lock = 1
Save drafts = 1
List drafts = 1
Peter.
Stefan Ritt wrote: |
The message is not lost, but becomes a "draft". This works similar in most email systems. When you edit an email and son't send it, it stays in your "draft" email folder and does not show up in your "sent" folder. Same here. You are suppost to "submit" you entry, the "save" is just a temporary safety backup. If you do not submit (if you press BACK or your browser crashes), the entry is not submitted to the system, but stays around as a draft. If you create a new message, the system asks you to edit and finish your draft, so that it does not get lost. So always hit "submit" if you are finished editing a message, not just "save".
If you want to see the draft message, they are rendered in red in the normal message list if you have
List drafts = 1
in your config file. No ide where your cluttering comes from.
Stefan
Peter K wrote: |
I found a sequence which hides the message from the list.
In addition this sequence corrupts UTF encoding of the text.
- create new message
- submit it
- Edit this message again
- click SAVE and then exit the editor (click Logbook name in the header or BACK in the browser)
- message disappeared from the list!
- by clicking NEW message I found my lost one in the drafts, but all text was corrupted.
I've made small GIF presentation on this issue (attached, open in new window), may be this helps.
|
|
|
|
|
|
|
|
|
|
68741
|
Fri Feb 16 09:18:56 2018 |
| Matej Sedej | msedej@hotmail.com | Bug report | Windows | ELOG V3.1.3-fd7 | Problem with special character "č" | Hello!
First of all, thank you for this great piece of software! For now it seems to perfectly cover our need to log very basic events, there was a setting for everything we wanted to set.
However we have one problem and that is the saving of the letter "č" (Slovenian) into the log files. That is unicode character U+010C and U+010CD https://unicode-table.com/en/010C/. When writing to the log file it is replaced with "Č" and "č". Is there a known fix for this?
Thank you and best regards,
Matej |
68742
|
Fri Feb 16 09:36:18 2018 |
| Matej Sedej | msedej@hotmail.com | Bug report | Windows | ELOG V3.1.3-fd7 | Re: Problem with special character "č" | I see the same problem exists on this board as well. Actuall it appears only the attribute fields are affected. The č character was incorrectly written to the log file from the subject field above, but correctly from the body text below.
Matej Sedej wrote: |
Hello!
First of all, thank you for this great piece of software! For now it seems to perfectly cover our need to log very basic events, there was a setting for everything we wanted to set.
However we have one problem and that is the saving of the letter "č" (Slovenian) into the log files. That is unicode character U+010C and U+010CD https://unicode-table.com/en/010C/. When writing to the log file it is replaced with "Č" and "č". Is there a known fix for this?
Thank you and best regards,
Matej
|
|
68743
|
Fri Feb 23 21:27:12 2018 |
| Ales Novak | Cortana.Alert@gmail.com | Bug report | Windows | V3.1.3-fd7f1e2 | BSOD | Hi,
I have been using elog for a few years and it is a wonderfull software and has been one that I can't go without. So thank you very much for making it.
After about a year, I upgraded to the latest version. I noticed that it causes the system to crash. It doesn't seem to happen that often.
I have installed this on 2 machines, one Windows 10 and one on Windows 7. Over the last week I got one BSOD on each OS.
The elogs have different configs and logbooks. One is a simple elog that doesn't have any attachments or anything funky. Just straight text.
Please see attached a screenshot of the Memory.DMP which has happned seconds after an schedule restarted the elog service on my PC.
I will keep monitoring and see if will happen again. But I thought I log it here anyway.
Thanks.
Cheers.
Ales. |
Draft
|
Mon Feb 26 18:16:35 2018 |
| Stefano Lacaprara | stefano.lacaprara@pd.infn.it | Bug report | Linux | 3.1.1 | Re: inactive users | Hi,
sorry to bother again on this issue, but it is causing me some trouble, as many of my users are using the "SetNone" button in their config page, and doing so they deactivate their account, which I have to re-activate manually.
The warning about "Are you sure you want to deactivate your own account ..." is actually triggered only when someone toggle the "active" radio button, but not when the "SetNone" function is used. In that case no warning is present, and the user just deactivate his/her account. I'm sure that this is not the intended behavior.
I attach a modified version of elogd.c (based on git c1866af75bb2fe62aa868c4cf562f43a08e4b499 ) with the modified javascript I proposed earlier in this thread.
best,
Stefano |
68745
|
Mon Feb 26 18:27:09 2018 |
| Stefano Lacaprara | stefano.lacaprara@pd.infn.it | Bug report | Linux | 3.1.3 | Re: inactive users | Hi,
sorry to bother again on this issue, but it is causing me some trouble, as many of my users are using the "SetNone" button in their config page, and doing so they deactivate their account, which I have to
re-activate manually.
The warning about "Are you sure you want to deactivate your own account ..." is actually triggered only when someone toggle the "active" radio button, but not when the "SetNone" function is used. In that
case no warning is present, and the user just deactivate his/her account. I'm sure that this is not the intended behavior.
I attach a modified version of elogd.c (based on git c1866af75bb2fe62aa868c4cf562f43a08e4b499 ) with the modified javascript I proposed earlier in this thread.
best,
Stefano |
|