Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 718 of 808  Not logged in ELOG logo
    icon2.gif   Re: Attribute not updated, posted by Midas User on Tue Jun 9 15:28:53 2015 
> I saw in the doc that an attribute cant be bigger than 100 char. but I couldn't figure the maximum size for options...  I'm wondering if the issue comes from the browser not refreshing correctly or if its elog..

The number of possible options is limited in elog to 100. This is defined by MAX_N_LIST in elogd.h. You can try to increase it and recompile elogd, but no guarantee that this works.

The reason that it *sometimes* work is really a bug, I should do better limit checkings...

/Stefan
    icon2.gif   ELOG Forum: drafts cannot be deleted, posted by Stefan Ritt on Tue Jun 9 17:09:22 2015 
> Another strange thing: the draft got submitted when I hit the "Back" button after reopening it.

Well, this is a problem indeed. When edit entries now, drafts gets saved regularly, overwriting your original entry. This is a limitation of the elog database, which cannot do full versioning. So "Back" is actually the same as "Commit without email notification". Or better "Commit some ten seconds ago". Now I 
don't know what the best solution is. I'm tempted to just remove the "Back" button and replace it with a "Delete" button. So people can either submit an entry or delete it completely. Any thoughts?
Entry   Problem with a draft message, posted by David Pilgram on Tue Jun 9 17:17:11 2015 

Hi Stefan,

I had started to write a completely different bug report, but then realised I had not checked a detail.  I had written about one sentence.  So I decided to abort the message, and hit the "back" button.  Only I found that this had created a new entry in the elog listings.  I immediately went in and deleted it, but I had expected the "Back" button to have aborted the entry (as it does in 2.9.x) not to submit the entry!

It doesn't seem to have created an email, though.  And for the sake of all your users, I'd not want to experiment here on the matter too much!

    icon2.gif   Re: Problem with a draft message, posted by David Pilgram on Tue Jun 9 17:21:25 2015 

Just to comment that I submitted the entry below by pressing the "Back" button!

David Pilgram wrote:

Hi Stefan,

I had started to write a completely different bug report, but then realised I had not checked a detail.  I had written about one sentence.  So I decided to abort the message, and hit the "back" button.  Only I found that this had created a new entry in the elog listings.  I immediately went in and deleted it, but I had expected the "Back" button to have aborted the entry (as it does in 2.9.x) not to submit the entry!

It doesn't seem to have created an email, though.  And for the sake of all your users, I'd not want to experiment here on the matter too much!

 

    icon2.gif   Re: Problem with a draft message, posted by David Pilgram on Tue Jun 9 17:23:27 2015 

Just to comment that the expected emails that one would have expected with the last two entries have either
been held up or simply have not been generated and sent - both the preceeding entries were submitted by using the "Back" button, this time I'll use the "Submit" button, which should generate a email.

David Pilgram wrote:

Just to comment that I submitted the entry below by pressing the "Back" button!

David Pilgram wrote:

Hi Stefan,

I had started to write a completely different bug report, but then realised I had not checked a detail.  I had written about one sentence.  So I decided to abort the message, and hit the "back" button.  Only I found that this had created a new entry in the elog listings.  I immediately went in and deleted it, but I had expected the "Back" button to have aborted the entry (as it does in 2.9.x) not to submit the entry!

It doesn't seem to have created an email, though.  And for the sake of all your users, I'd not want to experiment here on the matter too much!

 

 

    icon2.gif   Re: Problem with a draft message, posted by Stefan Ritt on Tue Jun 9 19:35:28 2015 

Just read what I wrote at elog:67983

David Pilgram wrote:

Just to comment that the expected emails that one would have expected with the last two entries have either
been held up or simply have not been generated and sent - both the preceeding entries were submitted by using the "Back" button, this time I'll use the "Submit" button, which should generate a email.

David Pilgram wrote:

Just to comment that I submitted the entry below by pressing the "Back" button!

David Pilgram wrote:

Hi Stefan,

I had started to write a completely different bug report, but then realised I had not checked a detail.  I had written about one sentence.  So I decided to abort the message, and hit the "back" button.  Only I found that this had created a new entry in the elog listings.  I immediately went in and deleted it, but I had expected the "Back" button to have aborted the entry (as it does in 2.9.x) not to submit the entry!

It doesn't seem to have created an email, though.  And for the sake of all your users, I'd not want to experiment here on the matter too much!

 

 

 

    icon2.gif   Re: Problem with a draft message, posted by David Pilgram on Tue Jun 9 20:26:00 2015 

I missed or don't remember that post.  My vote is replace "Back" with "Delete" - or "Abort"

Stefan Ritt wrote:

Just read what I wrote at elog:67983

David Pilgram wrote:

Just to comment that the expected emails that one would have expected with the last two entries have either
been held up or simply have not been generated and sent - both the preceeding entries were submitted by using the "Back" button, this time I'll use the "Submit" button, which should generate a email.

David Pilgram wrote:

Just to comment that I submitted the entry below by pressing the "Back" button!

David Pilgram wrote:

Hi Stefan,

I had started to write a completely different bug report, but then realised I had not checked a detail.  I had written about one sentence.  So I decided to abort the message, and hit the "back" button.  Only I found that this had created a new entry in the elog listings.  I immediately went in and deleted it, but I had expected the "Back" button to have aborted the entry (as it does in 2.9.x) not to submit the entry!

It doesn't seem to have created an email, though.  And for the sake of all your users, I'd not want to experiment here on the matter too much!

 

 

 

 

    icon2.gif   Re: Path disclosure on unfound file, posted by Stefan Ritt on Wed Jun 10 09:12:06 2015 Screen_Shot_2015-06-10_at_9.11.38_.png

What URL did you use? If I try here on this forum I get:

which looks fine to me.

 

Bruce Bush wrote:

Greetings,

  Running elog 3.1.0 on CentOS 6.6.  When I try to access a nonexistent file, elog reveals a path in the 404 page.  For example:

Not Found

The requested file /usr/local/elog/themes/default/blortblortblort7854.htm was not found on this server


ELOG version 3.1.0
 
  Is there any way to use a custom 404 page with elog, or to make it stop displaying the file information?
 
Thank you,
bb
 
 

 

 

ELOG V3.1.5-3fb85fa6