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

Is there a way to restrict other author to edit the custom input form submitted?

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

Have you tried

Message height = ...

unit is number of text lines.

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 
 

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

Hi all, 

I'm following config guide and so far so good. The only issue I run into is when enabling SSL.

Guide says - One can replace this certificate and key with a real certificate to avoid browser pop-up windows warning about the self-signed certificate.

Can you please tell me a more details regards this part? I have acquired security certificate and replaced contents of SSL folder. 

Now elogd.exe gets error 1067.

Any help would be highly appreciated.

Thanks!

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

Has anyone developed a report tool for elog?  I would like to be able to sort certain items and send them to either a printer, or an email (external to my own use).

If not, any ideas on an easy means of doing this?  I write a lot of Perl, so that would be an option for me if the text is easily obtained.

Thanks

Switch to the "summary" display (try it with this forum). You get headers (like "category"). Clicking on it sorts by that attribute. Then display "all" entries, or use the "find" option to search in certain time periods, then just print the web page.

Alternatively, expeort logbook entries as CSV files, load them into a spreadsheet program, and do the sorting and printing there.

Stefan

I don't see an "export" option in the documentation, only "import."  Printing the web page is probably not what I want.

Click on "Find", select "Export to CSV", optionally select filter criteria, then press "Search".

Stefan

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

We have been using elog on Windows 10 for a long time. Today, after a Windows update, the elogd service started crashing (error 1067, unexpected termination). It ran fine just before the Windows update (which took > 1 hour, so it was a major one). Uninstalling and re-installing did not help, including replacing my elogd.cfg with the default. Installing on another PC (that also has this update) fails in the same way. I have a good backup of my logbook.

Any suggestions?

Hi all,

I try to implement a shift check list for our facility. The attributes called "a1, a2, b1, b2 etc" are used in original shiftcheck.html， However, we would like to use "1.1, 1.2, 2.1, 2.2 etc". So I try to change the name of checkbox in shiftcheck.html and the attributes in elogd.cfg file to "1.1, 1.2, 2.1, 2.2 etc". The elog web page can display the attributes like "1.1, 1.2...", but the checked value of "on" seems not working. And I have used wirshark to monitor the http package, the request message seems correct, but the service response seems can't deal with attributes like "1.1, 1.2...", so is there a way to work around?

An attribute is similar to a variable. Do you know any programming language that allows to start a variable with a digit? I don't.

The solution is very obvious: start your attributes with a letter.

Cheers, Andreas

That's true. Thanks for your explanation.

Cheers, Xuan

We have a possible bug with elog that the ID for an elog entry at over 99,999 entires reads as 10,000... 

68792/1 Illistrates the problem, we use this ID often to cross reference from out datalog...

Is this a know bug we can find a fix for? We are using:  elogd 2.9.2 built Jul 14 2015, 18:58:06 revision

I am not sure I understand your bug report.

I can easily create IDs greater than 100'000 (see attached picture), but that is not your problem, or is it?

Cheers, Andreas

Hi Andreas, I'm working on the same experiment as Joseph who submitted the bug report.

You are right, IDs greater than 10^5 are created no problem. The issue is with the internal elog link, in this case of the form elog:SequencerEvents/XXXXX  The link generated uses only the first 5 digits of the message ID, and therefore links to the wrong message. In the two attachments you can see our sequencer event number 100098, first displaying the message where all of the ID is displayed and secondly in "full" view of the elog front page. Here, the "ID" column contains a link with the string: elog:SequencerEvents/10009. Our problem is that we often use this string to paste into other elogs and generate a link to the sequencer event message. However, since the string uses too few digits, we end up with a link to the wrong message

Well, in my example the ID link worked just fine.

There could be a string length limitation, but it could be as well the way you are creating the ID that is the source of the problem: I would need the part of your elogd.cfg that defines how you format your ID in order to try to reproduce your problem.

Cheers, Andreas

ah yes, that was a helpful clue. Our elogd.cfg file led me to a .js file which redefines the ID to the elog:SequencerEvents/XXXXX format and it indeed had a silly hard coded length of that string.

Since I am pretty sure this is our code, I think it is safe to say that this is not a bug in the elog

Thank you all for your kind responses. Please consider this thread resolved: no bug in elog

As Andreas said we have to reproduce the problem. What is special in your case is the elog:SequencerEvents/XXXXX. This is non-standard and must be created through your configuration of elog or by an external script. I just guess that you have something like

Preset ID = elog:SequencerEvents/#####

which causes elog to preset the ID with the above string. Can it be that you just put five hashmarks in the preset?

Stefan