The message height option only works if you select either "ELCode" or "plain" for encoding (this can also be made as default in the config file). For the HTML editor, the size is set internally and I don't have any influenc on it.

Stefan

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 
 

This comes from the openSSL library which elog includes. I tried myelf and found that a chained certificate is not correctly interpreted by the openSSL library. Most people anyhow don't use SSL inside elog, but run an Apache server in front of elog. This is anyhow better since Apache has an industry-strength security with regular updates. Much better than relying on OpenSSL.

Stefan

Have you tried

Message height = ...

unit is number of text lines.

Stefan

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

Hi all,

There are options "Restrict edit" and "Restrict edit time" for general logbooks, but it seems not work for shiftcheck logbook. I think the function only author can change their own entry is necessary for shiftcheck too. Any suggestion would be hightly appreciated.

Cheers,

Xuan

Here's a little example for a query for this logbook:

You can easily process this output with perl, to create reports. I use it for example to create counts for specific enties, like "Bug reports" that are not "closed", and show the results in some other user interfaces.

Cheers, Andreas

Hi, 
  I have an elogbook which sends notifications to subscribers, plus, if the "Type" is "New Run", it sends the notification to a different mailing addeess and with a different subject (which need to be parsed by 
a script, but that's not relevant). All works fine: the snippet of config is below.

Attributes = Subject, Author, Type
Options Type = New Run{1}



Email All = all@experiment.org
Use Email Subject = [demo] $Subject from $Author

Email Type "New Run" = new-run@experiment.org
{1} Use Email Subject = NEWRUN

However, I'd like that the notification is always sent to all@experiment.org for all entries with the standard subject, and *also* to new-run@experiment.org in case of new run with the customized one.
Apparently with the config that I'm using this is not happening, and the "new run" are only sent to new-run@experiment.org (w/ subject NEWRUN).
I could easily add the generic address in addition to new-run@experiment.org, ie:

Email Type "New Run" = new-run@experiment.org, all@experiment.org

but in this case the subject would be "NEWRUN", while I'd like it to be "[demo] $Subject from $Author".

Any idea about how this can be done?

thanks in advance, Stefano