Re: elog.css and lock.png fail to load with top groups, posted by Stefan Ritt on Thu Apr 4 12:12:58 2019
|
Looks more like a bug to me. Will investigate.
Stefan
Ben |
|
Re: How to edit Elog landing pages., posted by Stefan Ritt on Thu Apr 4 12:53:09 2019
|
Per default, all pages are created dynamically by elogd directly from its C code. So nothing to change easily except hacking the code. There is one exception
which is the start page you found already. To change any other page, you have to modify the C code. There is one more (dirty) trick: You can sneak in JavaScript
code on every page via the "bottom text" option. This code can then modify the DOM tree and changes pages, but you need to program this in JavaScript. |
|
Re: Can't subscribe email to logbooks in different top groups, posted by Stefan Ritt on Fri Apr 12 15:43:42 2019
|
Top groups should use separate password files, otherwise things can mess up.
Stefan
Ben |
|
Re: Pinned entry, posted by Stefan Ritt on Tue Apr 23 10:00:48 2019
|
This is not directly possible, but you can configure it with a trick. Create an attribute "pinned", make it of type "boolean", and
set the start page such that it sorts using the "pinned" attribute:
Atributes = ..., Pinned |
|
Re: Pinned entry, posted by Giuseppe Cucinotta on Tue Apr 23 11:02:32 2019
|
Thank you very much! It worked great!
Beppe
Stefan |
|
Re: elogd Service exited with abnormal code: 1, posted by Stefan Ritt on Tue Apr 23 14:26:51 2019
|
This kind of behavior we typically see if some elog entry is corrupt. After a few hours you might access this corrupt entry by accident, and then the
server stops. If you see however this behavior on a fresh logbook with no corrupt entries, then the problem must lie somewhere else.
Do you see the same problem running under linux? |
|
Re: elog program does not respect "Allow edit" list, posted by Heinz Junkes on Wed Apr 24 09:43:02 2019
|
Since there's no answer to that.
I am the only one with the problem? Did I just configure something wrong?
Thanks Heinz |
|
Re: elog program does not respect "Allow edit" list, posted by Stefan Ritt on Wed Apr 24 10:15:23 2019
|
There are two ways:
1) Use different password files for different logbooks. Each password file contains only those users which have access to that logbook.
2) Use "Login user = <usr list>" to restrict access to certain users in that list. |