shiftcheck restrict edit, posted by Xuan Wu on Thu May 24 08:53:50 2018
|
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. |
Re: shiftcheck restrict edit, posted by Xuan Wu on Wed Jun 6 02:41:32 2018
|
Is there a way to restrict other author to edit the custom input form submitted?
Xuan
Wu wrote:
Hi all, |
|
text area height, posted by Giuseppe Cucinotta on Fri Jun 1 17:08:48 2018
|
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 |
|
Re: text area height, posted by Stefan Ritt on Tue Jun 5 10:12:06 2018
|
Have you tried
Message height = ...
unit is number of text lines. |
Re: text area height, posted by Giuseppe Cucinotta on Tue Jun 5 15:06:18 2018 
|
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 |
|
Re: text area height, posted by Stefan Ritt on Tue Jun 5 21:37:26 2018
|
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 |
|
Enabling SSL, posted by Pasti on Fri May 18 08:04:37 2018
|
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. |
|
Re: Enabling SSL, posted by Stefan Ritt on Tue Jun 5 12:28:27 2018
|
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. |
|
Report Generating Tool?, posted by Hal Goldfarb on Mon May 21 09:41:57 2018
|
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. |
|
Re: Report Generating Tool?, posted by Stefan Ritt on Mon May 21 21:37:36 2018
|
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. |
|
Re: Report Generating Tool?, posted by Hal Goldfarb on Tue May 22 06:55:21 2018
|
I don't see an "export" option in the documentation, only "import." Printing the web page is probably not what I want.
Stefan
Ritt wrote:
Switch to the "summary" display (try it with this forum). |
|
Re: Report Generating Tool?, posted by Stefan Ritt on Tue May 22 11:11:43 2018
|
Click on "Find", select "Export to CSV", optionally select filter criteria, then press "Search".
Stefan
Hal |
|
Re: Report Generating Tool?, posted by Andreas Luedeke on Wed May 23 16:19:48 2018
|
Here's a little example for a query for this logbook:
curl -f -s -k "https://elog.psi.ch/elogs/Forum/?jcmd=Search&mode=CSV1&last=7&Category=^Question%24"
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 |
|
both "email <attribute> <value" and "email all" at the same time, posted by Stefano Lacaprara on Wed May 23 14:44:08 2018
|
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
|
elogd service crashes after windows update, posted by Tom Roberts on Fri May 18 00:57:33 2018
|
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. |
|
about shiftcheck, posted by Xuan Wu on Tue May 15 04:41:23 2018
|
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 |
|
Re: about shiftcheck, posted by Andreas Luedeke on Tue May 15 10:35:32 2018
|
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 |
|
Re: about shiftcheck, posted by Xuan Wu on Wed May 16 02:20:24 2018
|
That's true. Thanks for your explanation.
Cheers, Xuan
Andreas |
|
Elog ID entry bug at >99999 entries, posted by Joseph McKenna on Fri May 4 14:43:35 2018
|
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 |
|
Re: Elog ID entry bug at >99999 entries, posted by Andreas Luedeke on Fri May 4 16:05:32 2018
|
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 |
|
Re: Elog ID entry bug at >99999 entries, posted by Chris Rasmussen on Sat May 5 11:22:50 2018
|
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 |
|
Re: Elog ID entry bug at >99999 entries, posted by Andreas Luedeke on Sat May 5 20:55:23 2018
|
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. |
|
Re: Elog ID entry bug at >99999 entries, posted by Chris Rasmussen on Mon May 7 18:10:20 2018
|
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 |
Re: Elog ID entry bug at >99999 entries, posted by Joseph McKenna on Tue May 8 16:17:28 2018
|
Thank you all for your kind responses. Please consider this thread resolved: no bug in elog
Chris
Rasmussen wrote:
ah yes, that was a helpful clue. Our elogd.cfg file led me to a |
|
Re: Elog ID entry bug at >99999 entries, posted by Stefan Ritt on Mon May 7 14:24:18 2018
|
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/##### |