Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 399 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subject
  66629   Thu Nov 26 13:12:23 2009 Reply Bertram MetzBertram.Metz@gefanuc.comQuestionOther2.7.7Re: elogd.cfg for this forum
> Hi Stefan,
> 
> I'm interested in the current configuration file for this discussion forum. Could you please post it to the
> 'config examples' logbook?
> 
> Thanks,
> Bertram

Sure, here it is!
Attachment 1: elogd.cfg
[Forum]
; general options
Password file = <xxx>
CSS = forum.css
Login expiration = 1000
Allow delete = stefan
Self register = 2
Comment = Discussion forum about ELOG
Display mode = threaded
Guest menu commands = Back, Find, Login, Help
Guest list menu commands = Find, Login, Help
Number Attachments = 1
Message comment = <img src=icons/icon6.gif> Please enter only serious messages here, for testing use the <a href="../Linux+Demo">Linux</a> Logbook:
Entries per page = 8
Reverse sort = 1
Restrict edit = 1

; Attributes
Attributes = Icon, Author, Author Email, Category, OS, ELOG Version, Subject
Options Category = Info, Bug report, Bug fix, Question, Request, Comment, Other
Style Category Info = background-color:lightblue;color:red
IOptions Icon = icon1.gif, icon2.gif, icon3.gif, icon4.gif, icon5.gif, icon6.gif, icon7.gif, icon8.gif, icon12.gif, icon13.gif, icon14.gif
MOptions OS = Linux, Windows, Mac OSX, All, Other
Icon comment icon1.gif = Entry
Icon comment icon2.gif = Reply
Icon comment icon3.gif = Idea
Icon comment icon4.gif = Warning
Icon comment icon5.gif = Question
Icon comment icon6.gif = Cool
Icon comment icon7.gif = Smile
Icon comment icon8.gif = Angy
Icon comment icon12.gif = Blink
Icon comment icon13.gif = Disagree
Icon comment icon14.gif = Agree
Required Attributes = Author, Author Email, Subject, Icon, OS, ELOG Version, Category
Preset on reply subject = Re: $subject
Thread display = $subject, posted by $author on $Entry time
RSS title = $subject, posted by $author on $Entry time
Thread icon = Icon
Date format = %B %d, %Y
Preset Author = $long_name
Preset Author Email = $user_email
Preset on reply Author = $long_name
Preset on reply Author Email = $user_email
Preset on reply Icon = icon2.gif
Locked Attributes = Author
Quick filter = Date, Category, Subtext

; Combine attributes into singles lines
Format Author = 1
Format Author email = 1, attribname, attribvalue, 30, 256
Format OS = 1
Format ELOG Version = 1, attribname, attribvalue, 10, 10
Format Subject = 0, subjname, subjvalue

; Email notification
Email message body = 1
Display Email recipients = 0
Omit Email to = 1
Use Email from = noreply@psi.ch
Use Email subject = ELOG Forum: "$Subject" posted by $Author
Email encoding = 4
  66628   Tue Nov 24 10:38:26 2009 Question Bertram MetzBertram.Metz@gefanuc.comQuestionOther2.7.7elogd.cfg for this forum
Hi Stefan,

I'm interested in the current configuration file for this discussion forum. Could you please post it to the
'config examples' logbook?

Thanks,
Bertram
  66627   Mon Nov 23 13:17:53 2009 Agree David PilgramDavid.Pilgram@epost.org.ukQuestionLinux2.7.7-2266Re: Attachments and images of attachments
> > Hi Stefan,
> > 
> > I attached a 12 page (22kB) pdf file - no images - to an entry, but elog only converted the first 8 pages to
> > images (.png).  This is reproducable, i.e. a different small multipage pdf file produced the same number of images.
> > 
> > The size of the pdf file does not seem to be a problem, a single page pdf file with a lot of images in it
> > attached as expected.
> > 
> > Is this correct, or a defined limitation?
> 
> This is a defined limitation. Sometimes people attach whole books in PDF form to an entry, and you don't want to end up 
> with hundreds of images cluttering your browser. If you want to see the full document, just load it into your PDF viewer.

Thanks, Stefan (why is this answer down under my name!?)

I couldn't find reference to this in the documentation.  In the case I referred to, I'll have to play with the pdf so that
the six pages I actually want displayed are.
  66626   Mon Nov 23 12:32:14 2009 Reply David PilgramDavid.Pilgram@epost.org.ukQuestionLinux2.7.7-2266Re: Attachments and images of attachments
> Hi Stefan,
> 
> I attached a 12 page (22kB) pdf file - no images - to an entry, but elog only converted the first 8 pages to
> images (.png).  This is reproducable, i.e. a different small multipage pdf file produced the same number of images.
> 
> The size of the pdf file does not seem to be a problem, a single page pdf file with a lot of images in it
> attached as expected.
> 
> Is this correct, or a defined limitation?

This is a defined limitation. Sometimes people attach whole books in PDF form to an entry, and you don't want to end up 
with hundreds of images cluttering your browser. If you want to see the full document, just load it into your PDF viewer.
  66625   Mon Nov 23 11:53:22 2009 Question David PilgramDavid.Pilgram@epost.org.ukQuestionLinux2.7.7-2266Attachments and images of attachments
Hi Stefan,

I attached a 12 page (22kB) pdf file - no images - to an entry, but elog only converted the first 8 pages to
images (.png).  This is reproducable, i.e. a different small multipage pdf file produced the same number of images.

The size of the pdf file does not seem to be a problem, a single page pdf file with a lot of images in it
attached as expected.

Is this correct, or a defined limitation?
  66624   Fri Nov 20 19:32:22 2009 Reply David Spindlerdsspindler@gmail.comBug reportWindows2.7.7 2246Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5

David Spindler wrote:

Stefan Ritt wrote:

David Spindler wrote:

I upgraded 2.7.5 rev 2175 to 2.7.7 rev 2246 last Thursday. I tested it with several logbooks with no problems. However I received a rep[ort today that it was down. I discovered whenever I tried to open a logbook entitled "Equipment Reservation" in the folder "EquipmentReservations" Elog would crash. I checked the elog.log file with no entries in it other than showing when it was restarted. I backed up to 2.7.5 and had no porblems with the same logbook. I repeated the upgrade to 2.7.7 with the crash problem returning. I am now back on 2.7.5 with no problems.

 

I just decided to try 2.7.6 rev 2239 and had the same results as 2.7.7.

 

This is running under Win2K with SP4 as an automatic service on port 80.

 

I am also running Elog V2.7.4-2118 on a different port (8080) simultaneously with no problems.

 

If you wish I will send the elog.cfg file. Anything else I can do to help, please let me know.

I need to reproduce your problem. Therefore I need the configuration and the xxxxxxa.log file containing the offending entries. You can strip it down to the minimum needed to do the crash. 

 In the process of trying to reduce it to a minimum I discovered that the entry that appears to be causing the crash is this:


 

Sorry for the delay.

 

1: The offending log file.

 

 

  66623   Wed Nov 18 13:54:25 2009 Cool soren poulsensoren.poulsen@cern.chQuestionLinux2.7.6Re: Re: Export and save problem with IE7

Stefan Ritt wrote:

soren poulsen wrote:

Hi

Would it be possible to use the "Export to:" function with IE7 on the Forum logbook, and save the logbook.

I can do the export but saving the file with IE7 does not work. Saving the file with Firefox, Chrome, Safari works.

This makes me think that E-log is good and IE7 is bad ?

Soren 

Right   

It seems to be a well known probmel with IE: http://classicasp.aspfaq.com/files/directories-fso/how-do-i-send-the-correct-filename-with-binarywrite.html 

So I tried all variations there, but none of them worked. The interesting thing is that it works if you use it locally, but not with the forum (which has an additional "/elogs" in the URL).

 

 

 Problem resolved.

  66622   Wed Nov 18 13:51:55 2009 Reply soren poulsensoren.poulsen@cern.chQuestionWindows2.7.6-2236Re: Re: Elog & SSL Export to CSV , Problem

Stefan Ritt wrote:

Chuck Brost wrote:

Stefan, would it be possible to make the following change so that the document is not cached and at the same time it is possible to save it.

The change would entail replacing the "Pragma: no-cache" directive with an "Expires: " <HTTP-date> where <HTTP-date> is the same as Date header value. Please see section 14.21 of http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html

Hopefully there are no other side effects to this change.

ok, so I removed the "Pragma: no-cache". With IE it looks fine now, and if I repeat it two times it always gets is from elog and not from the cache due to the "Expires:" statement. The "no-cache" came from old days when some browsers did not yet support the "Expires" tag. I hope that this is better now, so let's see when we get the first complaints. The modification is in SVN revision 2265.

 This seems to work fine.

ELOG V3.1.5-3fb85fa6