Submitted as a question because some folks may consider this a bug in IE (but not MS obviously because IE8 does the same).  When you upload a new open XML attachment (Office 2007 file extension, docx, ppts, xlsx, etc) the attachment is not recognized properly in IE and it tries to download as a zip file (since the OOXML is actually is a zipped set of XML docs).  This is something that is widely recognized on the Internet ( http://www.google.com/search?hl=en&q=docx+internet+explorer+zip&aq=1&oq=docx+internet ) but is typically resolved by adding the mime extensions at the web server level. 

Are there any plans to add the new mime extensions to the elogd.c source? (Instead of forcing users to use FireFox or Right click, save-as and rename?

http://www.bram.us/2007/05/25/office-2007-mime-types-for-iis/

Regards,

rbsterli

   {
   ".AI", "application/postscript"}, {
   ".ASC", "text/plain"}, {
   ".BZ2", "application/x-bzip2"}, {
   ".CFG", "text/plain"}, {
   ".CHRT", "application/x-kchart"}, {
   ".CONF", "text/plain"}, {
   ".CSH", "application/x-csh"}, {
   ".CSS", "text/css"}, {
   ".DOC", "application/msword"}, {
   ".DVI", "application/x-dvi"}, {
   ".EPS", "application/postscript"}, {
   ".GIF", "image/gif"}, {
   ".GZ", "application/x-gzip"}, {
   ".HTM", "text/html"}, {
   ".HTML", "text/html"}, {
   ".ICO", "image/x-icon"}, {
   ".JPEG", "image/jpeg"}, {
   ".JPG", "image/jpeg"}, {
   ".JS", "application/x-javascript"}, {
   ".KPR", "application/x-kpresenter"}, {
   ".KSP", "application/x-kspread"}, {
   ".KWD", "application/x-kword"}, {
   ".MP3", "audio/mpeg"}, {
   ".OGG", "application/x-ogg"}, {
   ".PDF", "application/pdf"}, {
   ".PNG", "image/png"}, {
   ".PS", "application/postscript"}, {
   ".RAM", "audio/x-pn-realaudio"}, {
   ".RM", "audio/x-pn-realaudio"}, {
   ".RM", "audio/x-pn-realaudio"}, {
   ".RM", "audio/x-pn-realaudio"}, {
   ".RPM", "application/x-rpm"}, {
   ".RTF", "application/rtf"}, {
   ".SH", "application/x-sh"}, {
   ".TAR", "application/x-tar"}, {
   ".TCL", "application/x-tcl"}, {
   ".TEX", "application/x-tex"}, {
   ".TGZ", "application/x-gzip"}, {
   ".TIF", "image/tiff"}, {
   ".TIFF", "image/tiff"}, {
   ".TXT", "text/plain"}, {
   ".WAV", "audio/x-wav"}, {
   ".XLS", "application/x-msexcel"}, {
   ".XML", "text/xml"}, {
   ".XSL", "text/xml"}, {
   ".ZIP", "application/x-zip-compressed"},

 Ok, I added the MIME extensions in ELOG Rev. 2196. The forum runs already the updated version, so can you try with the demo attachments from your entry?

 It looks good from here!  Thanks!!

Best Regards,

Rich

Hi.  I'm pretty new to ELOG, so I'm not sure if I'm doing something wrong.

I have a bunch of fields set so that after an entry has been submitted, they cannot edit certain fields.  When I click the edit button, everything looks restricted as it should be, but if I click Preview, the user is then able to change the fixed attributes.

Is there anyway to remove the preview button inside the edit page, or is anyone else having this issue?

Thanks,

Allen

Hi

I am having a little problem with e-log that I can easily reproduce.

I have defined a number of constraints on my e-log fields and I am testing what happens when the user does not respect them.

So this only happens when I am not observing the input formats or the mandatory fields.

This is the GDB trace. This is not very verbose, so I must learn to use the other tracers, I guess.

Soren

It would be best if I could reproduce your problem. So can you start from a very simple configuration file, add your constraints until the problme happens, and then send me the config file? 

Hi

The problem is not exactly what I thought, but I did track it down. Here is a logbook definition that reliably creates a segmentation fault in e-log. This logbook's only useful purpose is in fact to create a segmentation fault:

You select "New", then "Select", without entering anything.

--------------

Login user = Admin

Attributes = Link

Change Link = <a href="https://$Link"">$Link</a>

---------------

I would be able to create some more debugging information of course, if needed.
 

Regards

Soren

I had finally the same problem. This is due to a bug indeed inside is_script(). It has been fixed in revision 2201.