Stefan,

I finally got it installed on a server at work (only took a year to work through all the red tape). I have seven logbooks up and running and only one is giving me trouble. It is an On-Line Help book where I wanted to store documents that could be referenced by our staff. It is the simplest of my logbooks (see config file below) but when I hit the "Submit" button it crashes the program. I can not see the error myself but the server guys are telling me that that we are getting an "Internal error, no valid header!" error. The only other thing that I can think to mention is that the entry that is crashing the program is a 60k Microsoft word table that I had cut and pasted into elog.

Thank you, Mike

[OnlineHelps]
Write Password = SWNlQ3ViZQ==
;DISPLAY
Theme = default
Display mode = threaded
Mode Commands = 0

Thread display = --------------  $Title  --------------
Comment = On-Line Helps

Attributes = Title

Required Attributes = Title
Page Title = ELOG - $subject
Reverse sort = 0
 

Ah, that rings a bell. We recently had problems with large tables. Can you try the current version if you get the same problem? 

Is there any way I can limit the ammount of characters in the Subject line?

Thank you,

 Use the

Format Subject = ...

option as described in the manual. The last parameter is the "maximum number of characters allowed".

Is there a way, option, feature to setup the text section only to be scrollable when viewing a log entry, such that the header (meta info) section stays fixed?

Unfortunately no.

Well, I tinkered a bit with a journal entry display page and found that without having to suggest the flavor-of-the-month web design mantra of "replace table layout with CSS only",  just a few CSS tweaks can enable exactly what I am desiring.

For your consideration, here are the tweaks I made to get a fixed header and footer section with a scrollable journal entry section in the middle:

1. moved the journal entry content and footer line (elog version info) out of the layout table structure, into their own div sections;
2. in the style sheet, added attribute "position:fixed" to the "frame table" section;
3. in the style sheet, added attribute sections for journal entry content and footer div sections:
   1. #content: overflow:auto;position:fixed;top:230px;bottom:30px;width:100%;
   2. #footer:  text-align:center;bottom:0;position:fixed;width:100%;

Now as I'm not a web designer by trade and not intimately familiar with CSS nuances, I used the time honored method of documentation lookup with trial and error.

In any case, it worked and displays exactly the way I wanted; please do consider this for a future elog release.

Bill

Apparently you downloaded an ELOG page and modified it manually. Can you send me the modified page, it then would be easier for me to implement it (I can shorten "my" trial and error phase..)

Yes, you are correct, I did simply take a sample page from logs and tinker with the html and css file, with the changes enumerated previously.  I have attached the tweaked sample html elog log page and css file, along with a few of the standard elog png files to complete the page with some semblance of the normal display.

 Yes it's on my personal to-do list, but don't know when I will find some time.

I am using the following commands to display the text of all of the entries at once (so that you can read them without having to click on each entry).

Display mode = threaded
Expand Default = 3

Problem is that the information on the page is packed so tightly together (no white space) that it can be hard to read. Especially with single line entries.

Is it possible to automatically append a new line to a routine entry?

THANK YOU for your assistances.

Please tell me how to share my elog with people.

 Connect your PC to the internet and tell everybody the URL. Make sure the Windows Firewall allows remote access.

If I open an elog entry as read-only then attachments show as links which can be clicked to open the attachment.  However, if I open an entry using Edit then attachments show as text with a delete button - I would expect to be able to read attachments when editing an entry but there may be some good reason for not being able to.

Also, on attachments, if I click on the attachment icon (paperclip) on the list page the URL encodes "/" as "%2f", e.g.

http://xxx.xxx.xxx.xxx:8080/Change_Log/..%2FChange_Log%2F090205_123135%2FCHANGE_CONTROL_NOTICE_050209.doc and I get the following error:

"Invalid URL: Change_Log/..%2FChange_Log%2F090205_123135%2FCHANGE_CONTROL_NOTICE_050209.doc" .  If I then change all occurrences of "%2f" to "/" the link works.

We don't use attachments very often but occasionally they are just what you need - and so is elog!

great piece of software - many thanks for sharing it

Steve

You have an old version of elog, this bug has been fixed some time ago. Have a look for example at https://midas.psi.ch/elogs/Linux+Demo/.

If you click on a peperclip there, the attachment is shown correctly. 

 Thanks - just downloaded and compiled the latest version and all is well

I got this error message when trying to upload 17K text file as attachment.  Any idea why ? It's a fresh installed elog and not much configuration done yet.

Thanks

No, no idea. I usually put several MB attachments into elogs without problems. Can you try with the demo logbook https://midas.psi.ch/elogs/Linux+Demo/. Maybe you have an old version of elog? 

 No problem attaching big files on F10 or CentOS 4.7.   The one that is having issue was on JeOS-8.0.4 - Ubuntu ;-).  All tested with ELOG version 2.7.5 build 2130.

 Correction.  The OSes are OK.  But don't use Opera when uploading big files.

What I would like to do is:

If attribute "A" and attribute  "B" - send email to person #1

If attribute "A" and attribute  "C" - send email to person #2

(I apologize if this in the documentation. I have looked at the "Email" section and have either missed it or don't understand it. Thank you for the help)

This is not implemented, you only can test on a single attribute. There might be a possibility with conditional attributes, but I have never tried this out.

Your suggestion worked GREAT (like always)

 Could you post an example of what you used?

 Sorry, it took me so long to respond. I didn't notice your request.

Attributes = Instrument, Notify Lead Tech

Options Instrument = Olympus, Beckman

Options Notify Lead Tech = Yes{a}, No {b}

{a}Email Instrument Olympus = John@lab.net         (i.e. if it is "Yes" and  "Olympus" - John gets an email)

{a}Email Instrument Beckman = Mary@lab.net         (i.e. if it is "Yes" and  "Beckman" - Mary gets an email)

 Sorry, it took me so long to respond. I didn't notice your request.

Attributes = Instrument, Notify Lead Tech

Options Instrument = Olympus, Beckman

Options Notify Lead Tech = Yes{a}, No {b}

{a}Email Instrument Olympus = John@lab.net         (i.e. if it is "Yes" and  "Olympus" - John gets an email)

{a}Email Instrument Beckman = Mary@lab.net         (i.e. if it is "Yes" and  "Beckman" - Mary gets an email)