> Hello,
> 
>    Thank you for such a great piece of software!
> 
>    When displaying the entries in a log book with Summary view, ELCode is not processed in 'Text'. I know 
there
> is an option called 'Allow HTML", but is there something similar for decoding ELCode in the Summary 'Text' 
field?
> 
> Thank you again,
>    - Dan

Decoding HTML (or ELCode which translates to HTML) in the summary field is difficult, since the text is 
truncated. 
Assume you have some code like

Text
<b>Text
  <i>Text
----- cut here
</i>
</b>

Sot he bold <b> and italics <i> tags are opened, but closed after the cutting line. In that case the whole page 
might render wrongly, because everything after the summary text will be displayed in bold and italics. To fix this I 
would have to scan the HTML code and close all open tags "by hand". But since there are very many possibilities, 
especially if one used multi-column tables, this is almost impossible without writing my own HTML parser which is 
beyond the scope of elog. So the only clean solution I have found so far is to strip off all HTML formatting and 
just showing plain text there.

That would be a lot of effort for very little gain. I appreciate your detailed response. 

Thank you,
   - Dan

> > Hello,
> > 
> >    Thank you for such a great piece of software!
> > 
> >    When displaying the entries in a log book with Summary view, ELCode is not processed in 'Text'. I know 
> there
> > is an option called 'Allow HTML", but is there something similar for decoding ELCode in the Summary 'Text' 
> field?
> > 
> > Thank you again,
> >    - Dan
> 
> Decoding HTML (or ELCode which translates to HTML) in the summary field is difficult, since the text is 
> truncated. 
> Assume you have some code like
> 
> Text
> <b>Text
>   <i>Text
> ----- cut here
> </i>
> </b>
> 
> Sot he bold <b> and italics <i> tags are opened, but closed after the cutting line. In that case the whole page 
> might render wrongly, because everything after the summary text will be displayed in bold and italics. To fix this I 
> would have to scan the HTML code and close all open tags "by hand". But since there are very many possibilities, 
> especially if one used multi-column tables, this is almost impossible without writing my own HTML parser which is 
> beyond the scope of elog. So the only clean solution I have found so far is to strip off all HTML formatting and 
> just showing plain text there.

The way I have ELOG configured it sends an email to supervisors based on which "Department " (attribute) was selected. Problem is that when the supervisor replies the department

is still selected and it sends a second email to the supervisor. Is there any way to supress the emails (automatically) on "Reply"?

No, but you can remove the "Department" with

Remove on reply = Department

this way the attribute vanishes, but that should be ok since you always have the link to the original entry which contains the department. 

We use eLOG with IE. Once we turned on SSL, it is no longer possible to "Export to CSV" and save the output.

The error that we get is:

Internet Explorer was not able to open this Internet site. The requested site is either unavailable or cannot be found. Please try again later.

This is documented on Microsoft's site: http://support.microsoft.com/kb/316431

It is considered a feature with no fix. Basically the browser is honoring a request from the server which is "Pragma: no-cache". Problem can be reproduced in IE versions 6 through 8.
 

I see the same problem with IE. The knowledge base says that one should remove the "no-cache" statement from the header, but that has strange side effects: Assume you export a logbook to a CSV file, and a few days later you export it again, since many things changed. But you browser will in that case not retrieve the new logbook, but read the old CSV file from the cache. But the browser does not tell you this, so you see an old version of the logbok without knowing this, which can be dangerous. So I better leave the "no-cache" in the header. The workaroung is not to click on "Save" on the file download dialog, but on "Open". You see then the CSV data inside the browser and can copy/paste it into a notepad document, then save it. 

 Ah, now this is humorous, when the client first came to me, that was almost exactly the work around I gave him, open it, CTRL-A to highlight it all, CTRL-C to copy it, Move to the excel spreadsheet, CTRL-V to paste it into Excel. Select Data, Text to Columns, and you have an Excel Spreadsheet.   They wanted me to post the change in function anyway, though I told Vamsi, "just watch, someone will post the same workaround that I already gave to the clients".  So you see why I find it amusing.  I would say Great Minds Think Alike, but that would be giving myself a bit too much credit (grin).  First, thank you for proving me right on my prediction and if you should happen to make a change that would get around this SSL change in behavior, it would make a group of manufacturing types that are not quite as comfortable with computers as we are, very happy.   Please let us know.

I can easily remove the "no-cache" from the header, but as I wrote you, people can then shoot themselves into the foot by getting an old document, and I guess they become even less happy then. So you tell me which way you prefer.