You make a valid point!

My perspective is from my lab's specific use case, in which we often post plots of data in the body of the text, and it is useful for the ELOG-generated thumbnails to link to the full resolution plot. In previous versions, I believe this was the behavior. It would be convenient for my users if this continued to be the case, but I understand that it is not neccesarily the appropriate default behavior for all users of ELOG. 

The automatic hiding behavior is what I'm after, and I've discovered that it is only a problem for PDF attachments. I have reproduced this on the demo logbook on git revision f828049. 

I've taken a look at the source you mentioned, but as far as I can tell, it is just looking for the opening of the img tag in the HTML source, and I'm not sure why that is different for a PDF.

Hm, looking through the source, there are many many places where PDF files are treated differently than strictly image filetypes (PNG, etc.). This makes sense in the context of multi-page documents. 

Still, I like using PDFs for vector plots... I suppose I should also confess to the following modification I've made to my ELOG for treating PDFs like images in drag-and-drop uploading. 

--- a/scripts/ckeditor/plugins/dndfiles/plugin.js
+++ b/scripts/ckeditor/plugins/dndfiles/plugin.js
@@ -142,7 +142,7 @@ CKEDITOR.plugins.add( 'dndfiles', {
                                                                return;

                                                        if(src.indexOf(".png") >= 0 || src.indexOf(".jpg") >= 0 || src.indexOf(".jpeg") >= 0
-                           || src.indexOf(".gif") >= 0 || src.indexOf(".svg") >= 0) { // This is an image
+                           || src.indexOf(".gif") >= 0 || src.indexOf(".svg") >= 0 || src.indexOf(".pdf") >= 0) { // This is an image
                                                                html += '<a href = ' + src + '><img src = "' + thumb + '">' + '</a>';
                                                        } else {        // this is not an image
                                                                // Server appends 14 characters in front of the name so we should remove them

Hi,

Is it possible to attach multiple files at one time?  Right now I have to attach each individually, click submit, then confirm, then re-select the next file...

This is a pain if one is attaching many files as I often want to do.  It would be nice to be able to select groups of files together using Ctrl and/or Shift, and even to attach a whole directory recursively.

I looked through previous threads but did not find this question asked there.

Thanks,

Eric

 Hi Stefan,

Okay thanks for letting me know.  That is unfortunate now.

Is there no way also to select multiple files with shift or ctrl?  Is there any usable workaround that you can see?

Thanks,

Eric

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

I am running elogd 2.5.7-1 built Feb 14 2005, 09:55:19 revision 1.558

Any assistance would be greatly appreciated!

-Erich-

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

Here is the command line I am using to start the daemon:

elogd -v -D -n <myhost> -p 8080 -l <myhost>/cgi-bin/elog/logbooks -c
/usr/local/server/apache/cgi-bin/elog/elogd.cfg

With the -v argument, here are the messages I get in /var/log/messages:

elogd 2.5.7-1 built Feb 14 2005, 09:55:19 
Feb 14 14:38:28 onion elogd[34579]: revision 1.558
Feb 14 14:38:28 onion elogd[34579]: Config file  :
/usr/local/server/apache/cgi-bin/elog/elogd.cfg
Feb 14 14:38:28 onion elogd[34579]: Resource dir : /usr/local/server/apache/cgi-bin/elog/
Feb 14 14:38:28 onion elogd[34579]: Logbook dir  :
/usr/local/server/apache/cgi-bin/elog/logbooks/
Feb 14 14:38:28 onion elogd[34579]: Falling back to default group "elog"
Feb 14 14:38:28 onion elogd[34579]: Group "elog" not found
Feb 14 14:38:28 onion elogd[34579]: Falling back to default group "nogroup"
Feb 14 14:38:28 onion elogd[34579]: Falling back to default user "elog"
Feb 14 14:38:28 onion elogd[34579]: User "elog" not found
Feb 14 14:38:28 onion elogd[34579]: Falling back to default user "nobody"
Feb 14 14:38:28 onion elogd[34579]: Indexing logbook "demo" ... 
Feb 14 14:38:28 onion elogd[34579]: 
Feb 14 14:38:28 onion elogd[34579]:   ID   1, 011108a.log, ofs     0, thead, MD5=
Feb 14 14:38:28 onion elogd[34579]: E4
Feb 14 14:38:28 onion elogd[34579]: 25
Feb 14 14:38:28 onion elogd[34579]: 4C
Feb 14 14:38:28 onion elogd[34579]: B8
Feb 14 14:38:28 onion elogd[34579]: AD
Feb 14 14:38:28 onion elogd[34579]: 4E
Feb 14 14:38:28 onion elogd[34579]: 88
Feb 14 14:38:28 onion elogd[34579]: 68
Feb 14 14:38:28 onion elogd[34579]: 08
Feb 14 14:38:28 onion elogd[34579]: 91
Feb 14 14:38:28 onion elogd[34579]: C9
Feb 14 14:38:28 onion elogd[34579]: 4D
Feb 14 14:38:28 onion elogd[34579]: 1E
Feb 14 14:38:28 onion elogd[34579]: B7
Feb 14 14:38:28 onion elogd[34579]: CB
Feb 14 14:38:28 onion elogd[34579]: C3
Feb 14 14:38:28 onion elogd[34579]: 
Feb 14 14:38:28 onion elogd[34579]: After sort:
Feb 14 14:38:28 onion elogd[34579]:   ID   1, 011108a.log, ofs     0
Feb 14 14:38:28 onion elogd[34579]: ok
Feb 14 14:38:28 onion elogd[34579]: Server listening on port 8080 ...

I am still getting the exact same error in my Apache log.

Any more ideas?

-Erich-