Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 338 of 807  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  66618   Tue Nov 17 13:44:04 2009 Reply Stefan Rittstefan.ritt@psi.chRequestLinux2.7.7-2264Re: Re: Re: List View: Attachments icon

Steve Williamson wrote:
Thanks for all of the contributions - all I meant in my original suggestion was that I'd like to be able to define which column(s) should hold the Attachments paperclip in the Full and Summary List Views, which I use all the time, to reduce the need to scroll horizontally on every page. This would be similar to being able to specify where the Edit control appears by specifying the Edit attribute in the "List Display" list.
... and I really didn't want to ruin another of Stefan's weekends or confuse anybody!


Ok, now I got it. I will put that request on the wish list. For the moment, you can restrict the number of attributes shown in the list view with "List display = ...". This way you can maybe display less so that your table gets narrower and you save some scrolling.
  66617   Tue Nov 17 12:29:24 2009 Reply Steve WilliamsonStephenWilliamson@Barnsley.gov.ukRequestLinux2.7.7-2264Re: Re: List View: Attachments icon
Thanks for all of the contributions - all I meant in my original suggestion was that I'd like to be able to define which column(s) should hold the Attachments paperclip in the Full and Summary List Views, which I use all the time, to reduce the need to scroll horizontally on every page. This would be similar to being able to specify where the Edit control appears by specifying the Edit attribute in the "List Display" list.
... and I really didn't want to ruin another of Stefan's weekends or confuse anybody!
  1742   Thu Mar 2 14:35:54 2006 Reply Alexandre Gauthiersupernaut@underwares.orgBug reportLinux2.6.1-1622Re: Re: Inline images URL not working

Stefan Ritt wrote:

Alexandre Gauthier wrote:
Whenever I try to insert an inline picture by using the
elog:1741/1
paths with ELCode, the link becomes "logbookname2/1" (Where logbookname is the name of my logbook) and hence, doesn't work. I recall that it worked once. The image did not display, but the URL seemed correct...


The problem has been fixed in version 2.6.1-3, so just upgrade.


Alexandre Gauthier wrote:
EDIT: i inserted a space in the elog URL above because regardless of the code brackets, it would still get interpreted.


You have to put a "\" in front of everything which should not get converted into a link, so elog:1741/1 does not get interpreted.


Hello Smile

This is what I have done, I checked out the trunk from subversion and built it inside my powerpc QEMU. I just updated the executables and the elcode.js file, and now it works.

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

  257   Fri Mar 21 16:52:12 2003 Reply Recai Oktasroktas@omu.edu.trInfo  Re: Re: Elog and SSL
Ooops, I destroyed the original post, now how can we fix this :)
  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.

  66621   Tue Nov 17 19:31:46 2009 Reply Heinzmanncatman333@web.deBug reportWindows2.7.7 2246Re: Re: 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:


 

 Hi,

I´m using 2.7.7 rev 2246 and tested it with my logbooks without any problems. But today I had no chance to reach them anymore. Strange.

Regards,

 

Michael

 

  1974   Tue Oct 10 16:15:21 2006 Reply Ben Shepherdbjs54@dl.ac.ukRequestAll2.6.2-1714Re: Re: 'Inline' button for attachments

Stefan Ritt wrote:

Ben Shepherd wrote:
Hi,

and it does exactly what you want.

cool! thanks.
ELOG V3.1.5-3fb85fa6