ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
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.
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
68737
|
Wed Feb 7 14:22:23 2018 |
| Peter K | pkravt@gmail.com | Bug report | Linux | V3.1.2-bd75964 | Re: Entries disappear after editing + UTF16 problem | 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.
|
|
|
|
|
|
|
68736
|
Tue Feb 6 10:23:26 2018 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | V3.1.2-bd75964 | Re: Entries disappear after editing + UTF16 problem | 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.
|
|
|
|
|
|
68735
|
Tue Feb 6 10:15:29 2018 |
| Peter K | pkravt@gmail.com | Bug report | Linux | V3.1.2-bd75964 | Re: Entries disappear after editing + UTF16 problem | 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.
|
|
|
|
|
68734
|
Fri Feb 2 08:31:35 2018 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | V3.1.2-bd75964 | Re: Entries disappear after editing + UTF16 problem | 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.
|
|
|
|
68733
|
Fri Feb 2 00:02:54 2018 |
| Yves | vanhaarlemyves@gmail.com | Question | Windows | 2.9.2->3.1.3 | Re: v3.1.3 does not work with logbooks from v2.9.2? - solved | Hi Andreas,
Thanks - you pointed me in the right direction. It appears that my logbooks were a combination of the two versions. I had all the year-directories (version 3) but also all the entry files in the main logbook directory. Seems version 2 does not care but version 3 does not like it. After carefully checking and removing all the logbook files in the main directory version 3 now works.
Cheers,
Yves
Andreas Luedeke wrote: |
Hi Yves,
just my two pence, maybe they help you to figure out what's going on:
versions 2.* had all entries of one logbook in one directory. Version 3.* create a subdirectory for each year. This had been added for me: if you use AFS for logbook storage, then you have a limit on how many files you can put into a single directory.
So the first time you start elogd 3.* with data from an elogd 2.* it should move all your logbook entries into sub-directories for each year. If that would have happened, you would not be able to use these logbook directories with the 2.9.2 version.
Maybe your logbook client is not allowed to create sub-directories? Although I would guess that it then would just throw an error message and stop.
Cheers, Andreas
Yves wrote: |
I have just upgraded elog from 2.9.2 -> 3.1.3.
3.1.3 runs fine with new logbooks. However, when trying to run 3.1.3 with my logbooks created with 2.9.2 things stop working.
Here is the command I run for testing [attachment 1]: first of all it takes a very long time (~ 10 minutes) for it to index the logbooks. When finished indexing I try it out in a web browser - it takes infinite time to load: no error message appears but also no logbook. After an hour or so elogd crashes without an error message.
When running 2.9.2 on the same machine, all runs wel (attachment 2)
cfd file: (I only left in one logbook - they are all configured the same)
[global]
port = 18080
Logging level = 3
Max content length = 500000000
Date format = %A, %d %B %Y
[Logrun - Amptek]
Theme = default
Comment = Logrun Amptec
Reverse sort = 0
Quick filter = Date, Type
Any ideas on how to solve this?
|
|
|
|