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/##### |
|
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 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: 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: 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. |
|
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 |
|
Re: number of entries in Login user list, posted by Stefan Ritt on Thu Jun 14 13:17:33 2018
|
Well, many arrays based on MAX_N_LIST are created on the heap memory, and if you exceed that, elogd simply crashes. There are compile options to increase
the stack and heap size, but that depends on the operating system and the compiler. The value of 100 has been proven to work everywhere. If you increase
it, you're on your own. |
|
Re: edit templates from config page, posted by Stefan Ritt on Thu Jun 14 13:20:26 2018
|
> Dear all,
> I have some logbook which uses preset text depending on some option values, and uses text files for this.
>
|