Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 389 of 808  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Emaildown Category OS ELOG Version Subject
  68728   Wed Jan 31 09:06:10 2018 Question Peter Kpkravt@gmail.comBug reportLinuxV3.1.2-bd75964Entries disappear after editing + UTF16 problem

I found a sequence which hides the message from the list.
In addition this sequence corrupts UTF encoding of the text.

  1. create new message
  2. submit it
  3. Edit this message again
  4. click SAVE and then exit the editor (click Logbook name in the header or BACK in the browser)
  5. message disappeared from the list!
  6. 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.

 

 

 

Attachment 1: elog_problem.gif
elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif elog_problem.gif
  68732   Thu Feb 1 14:55:24 2018 Reply Peter Kpkravt@gmail.comBug reportLinuxV3.1.2-bd75964Re: Entries disappear after editing + UTF16 problem

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.

  1. create new message
  2. submit it
  3. Edit this message again
  4. click SAVE and then exit the editor (click Logbook name in the header or BACK in the browser)
  5. message disappeared from the list!
  6. 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 Reply Peter Kpkravt@gmail.comBug reportLinuxV3.1.2-bd75964Re: 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.

  1. create new message
  2. submit it
  3. Edit this message again
  4. click SAVE and then exit the editor (click Logbook name in the header or BACK in the browser)
  5. message disappeared from the list!
  6. 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 Reply Peter Kpkravt@gmail.comBug reportLinuxV3.1.2-bd75964Re: 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.

  1. create new message
  2. submit it
  3. Edit this message again
  4. click SAVE and then exit the editor (click Logbook name in the header or BACK in the browser)
  5. message disappeared from the list!
  6. 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 Reply Peter Kpkravt@gmail.comBug reportLinuxV3.1.2-bd75964Re: 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
Release 3.1.2-1
2016-09-05
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.

  1. create new message
  2. submit it
  3. Edit this message again
  4. click SAVE and then exit the editor (click Logbook name in the header or BACK in the browser)
  5. message disappeared from the list!
  6. 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.

 

 

 

 

 

 

 

 

 

 

 

 

  520   Thu Apr 1 20:21:26 2004 Question PJ Meyerpjm@pjmeyer.orgQuestionWindows1.35 to 2.51"Upgrading" from 1.35 to 2.52 fails
Have a working copy of 1.35 running on NT4 server.
Went to upgrade to latest version.
Stopped service, installed the 2.52 version, restarted service and when 
trying to connect get nothing but server not found, dns errors, etc.
Copy back the 1.35 elogd.exe and everything is fine - I can connect and add 
entries to log.
Copy 2.52 elogd.exe and nothing.

So being the bright boy, I unistalled E-log, went through the registry and 
yanked everything out that referenced ELOGD, rebooted, installed 2.52, made 
the necessary registry changes, started service and nothing. 

Stopped service and copied 1.35 Elogd.exe back into folder, started service, 
and everything works.

Any ideas on why 1.35 works like a charm but 2.52 won't? I've tried stepping 
back to 2.10 version before giving up.

This is a server that is patched to latest and runs quite well with 1.35.
  521   Fri Apr 2 02:41:36 2004 Question PJ Meyerpjm@pjmeyer.orgQuestionWindows1.35 to 2.51Re: "Upgrading" from 1.35 to 2.52 fails
tuens out that the first log file was causing the problem. Elconv would just hang 
on trying to convert it. renamed it, reran elconv, reload service and 2.51 elogd 
and all was working as it should.


> Have a working copy of 1.35 running on NT4 server.
> Went to upgrade to latest version.
> Stopped service, installed the 2.52 version, restarted service and when 
> trying to connect get nothing but server not found, dns errors, etc.
> Copy back the 1.35 elogd.exe and everything is fine - I can connect and add 
> entries to log.
> Copy 2.52 elogd.exe and nothing.
> 
> So being the bright boy, I unistalled E-log, went through the registry and 
> yanked everything out that referenced ELOGD, rebooted, installed 2.52, made 
> the necessary registry changes, started service and nothing. 
> 
> Stopped service and copied 1.35 Elogd.exe back into folder, started service, 
> and everything works.
> 
> Any ideas on why 1.35 works like a charm but 2.52 won't? I've tried stepping 
> back to 2.10 version before giving up.
> 
> This is a server that is patched to latest and runs quite well with 1.35.
  830   Mon Dec 6 20:05:58 2004 Question PJ Meyerpjm@pjmeyer.orgBug reportWindows Login/Password request appears twice
Have set up 3 top level groups, each with their own password file.
Ever since users have to 'login' twice to get to the appropriate elog.
You click on top level group, get to log book and click on the one you want 
and get login/password dialog box, click ok and and you get it again and 
then you finally get into the elog book.

Anything I can check on this behavior?
ELOG V3.1.5-3fb85fa6