Re: Entry merging, posted by Stefan Ritt on Fri May 14 08:57:07 2010
|
Eric Krise wrote:
Is there a way to merge existing entries from several logbooks into a single logbook? |
|
Re: Entry merging, posted by Eric Krise on Fri May 14 16:50:53 2010
|
Stefan Ritt wrote:
|
|
Re: Entry Submission Help, posted by Stefan Ritt on Mon Sep 25 21:09:58 2006
|
[quote="kcmin"]1. When an entry is submitted is it possible to have it return to the submit page instead of a summary of the entry. In the ELog.cfg syntax
on the site it mentions something about this. However It says something about a file being present in the resource directory. I am not sure what to do
here.[/quote]
|
|
Re: Entries disappear after editing + UTF16 problem, posted by Stefan Ritt on Thu Feb 1 10:34:42 2018
|
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 |
|
Re: Entries disappear after editing + UTF16 problem, posted by Peter K on Thu Feb 1 14:55:24 2018
|
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. |
|
Re: Entries disappear after editing + UTF16 problem, posted by Stefan Ritt on Fri Feb 2 08:31:35 2018
|
You might have to update to the current elog version. This feature was implemented in Dec. 2016.
Stefan
Peter |
|
Re: Entries disappear after editing + UTF16 problem, posted by Peter K on Tue Feb 6 10:15:29 2018
|
We installed our elog from .apk in November 2017.
Version V3.1.2-bd75964
I suppose it already contains List drafts feature. |
|
Re: Entries disappear after editing + UTF16 problem, posted by Stefan Ritt on Tue Feb 6 10:23:26 2018
|
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. |