> > Is there any way to include the text of a log message in the CSV export? 
> > Anyway to include a pointer to the attachment?
> 
> The text of a log message is usually several lines long. To my knowledge, CSV
> only allows single line values, that's why I excluded the text field from the
> CSV export. This is different in the XML export, which supports multi-line
> values. If you teach me however how multi-line values can be represented in
> CSV format, I could easily add that.
> 
> As for the attachment, do you just need a name, or a URL back to the logbook?
> Should the pointer be in the form "http://elog.server/logbook/attachment.jpg"
> or in HTML form like <a href="http:/...">attachment</a> ?

I will attempt to use an active x script in a DTS package on SQL Server to parse
the xml and load it into the database. I can see where CSV has it's limitations.

We have about 10 logbooks running on the same Elog that all get fair use. Many people have turned off new entry emails because they were filling up inboxes, but are still interested in what's new. I saw the option to add "?last=1" to the start page, although I'm afraid using it might cause confusion over how to get to the older posts.

I was trying to figure out a way of creating a "digest" of sorts, a list of entry subjects posted in the past day or week, something similar to what's generated by "?last=1?mode=threaded", but for every logbook (similar layout to the selection page with nested logbooks). This could either be a page, or a regular email.

Is there way to generate such a cross-logbook page? What about a scheduled email formatted based on a given filter?

PS: The elog has been invaluable to us, a big thanks to all involved!

 Perfect! I didn't not know there was RSS support. I will probably use something like rss2email, but this is exactly what I needed. Thanks!

I don't remember the details, but originally had the same trouble. I think a "/" at the end of a url got me somewhere. 
I have defined...

URL = http://somewhere.edu/elog

...in the config file, and my redirect looks like this:

Redirect /elog http://somewhere.edu/elog/
ProxyPass /elog/ http://somewhere.edu:8080/
ProxyPassReverse /elog/ http://somewhere.edu:8080/

If I have a couple of attachments in a log book entry, I can link to that entry "http://example.edu/elog/Sandbox/7", I get the appropriate log in page, and after logging it, it takes me to the entry.

However, if I link directly an attachment, "http://example.edu/elog/Sandbox/7/1", I receive a plain log in page that doesn't have the stylesheet applied, and logging in, I am directed to " http://example.edu/elog/Sandbox/7/" which throws an invalid error. If I am already logged in the browser, it links correctly. 

I assume the problem must stem from messed up relative URL somewhere, hence the lack of stylesheet, or from the redirect incorrectly handling the /. (Looking at the source for the two login pages, the only difference is "<input type=hidden name=redir value="7">" versus "<input type=hidden name=redir value="7/1">". ) But that reaches the end of my ability...

This breaks the attachment links in emails.

Any help would be much appreciated!

I'm not of the skill level to help, but for what its worth, running Ubuntu 12.04, used alien to install the latest RPM with only two little snags. I had to create a link from libssl.so.1.0.0 to libssl.so.6, which is a trick I've pulled with other software, not sure what the proper fix is. I also had to make similar changes to the init script.

Hi,

I wonder if it is possible to set a minimum default value for the height of the text box when submitting new entries. If I understood well, by default the text box height automatically resizes in order that all the elements of the page are visible. Actually for our needs having a minimum height of the text box fixed (for instance 500px)  is by far more useful of viewing the attachment box (we know it is down scrolling the page :) ). We know it is possible to resize the text box using the mouse but doing this every time one creates a new entry can be annoying. Setting a default minimum size would be more confortable. Is it possible to do this?

Thank you 

Beppe

I tried with Message Height = 100 inside the conifguration of my logbook, but nothing changed as you can see in the first picture...

What I'm looking for is a way, if possible, to start by default with a wider message box, someting like fig2. For our purpose, using wide tables, it would be very useful to have a wider message box in order to have a full look to the message content, and also having it by default without modifying it by hand with the mouse every time we submit something to elog.

Beppe