> I am trying to run eLog under Apache 2 on my FreeBSD 5.3 server.  I started
> the daemon with "elogd -n <my hostname> -p 8080" and when I connect to my
> server on that port, I get a 500 server configuration error.  The Apache log
> contains this:
> 
> malformed header from script. Bad header=Please specify hostname.: elog

- make sure your proxy definition in httpd.conf is correct and it uses port 8080
- start elogd with the "-v" flag to see the communication between Apache and elogd
- maybe you might need an "URL = http://<my hostname>/<elog dir>/" in the config
file

> No luck.  I have the proxy definition in my httpd.conf file.  I have the URL parameter
> in my elogd.cfg file.

Can you show me the proxy definition? I hope you don't treat elogd as a CGI script...

As I wrote you by mail, I implemented your idea in the following way. As you
say, it's only working on Gecko based systems. I did not implement additional
configuration parameters, but made it through the CSS file:

- adding a new CSS style "attachmentframe" around all attachments
- adding class "attachmentframe" to the 'default.css' like:

.attachmentframe {
  border:1px solid grey;
  border-top:1px solid lightgrey;
  border-left:1px solid lightgrey;
  background-color:white;
  padding:5px;
}

.attachmentframe img {
    max-width:100%;
}

The latter restricts the image size to 100%, which is the width of the 
browser window. I like it that, but of course you can write 200px or 
anything else. Please find the modified elogd.c and default.css under CVS.

Have a look at http://midas.psi.ch/elogs/Contributions/10

> There is a problem with the 'Show Attributes' option
> causing the 'Format ...' options to be ignored.
> 
> See attachment for patch.

Thanks a lot. I applied your patch and committed the changes to CVS.

> If you have a space in a logbook name and you enable password list, then 
> the "List" menu option forces you to the login page each time.
> The URL says "aaa+bbb", but when you do not have passwords enabled, the 
> URL is "aaa bbb"

Thanks for reporting this. I fixed it in the current CVS version.

> 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> ?

> When creating/updating entries in elog, excluding the main text field are 
> there any limits on the size of the other fields?

Yes, this is controlled by the variable NAME_LENGTH in elogd.c, which is
currently set to 1500 characters. You can try to increase this and recompile,
but at some point you will produce a stack overflow and elogd will crash. So
the current length is a compromise.

- Stefan