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.
|
|
|
|
|
|
|
|
|