Re: Bug with Drafts and Language German, posted by Andreas Luedeke on Mon Aug 21 12:16:05 2017
|
I've quickly checked: there are a couple more commands in the source code that are not language encoded. I guess some of them needs correction.
> egrep -n "cmd=[A-Za-z]" elogd.c
10293: rsprintf(" r.open('GET', '?jcmd=Unlock&edit_id=%d', true);\n", message_id); |
CSS reference in Email for private logbooks, posted by Andreas Luedeke on Mon Aug 21 14:27:50 2017
|
We operate ELOG in an intranet. Many logbooks do send out emails; several use HTML content formatting.
If I watch HTML formatted emails
from the intranet, then everything is fine.
If I try to read them from home, my email client hangs when it tries to read the CSS file from
out intranet (URL: https://elog-gfa.psi.ch/SLS/elog.css).
Is there a way to set a URL for the email CSS?
Then I could simply |
New elog setting for large attachments, posted by Stefan Ritt on Mon Mar 26 16:32:43 2018
|
Most mail delivery systems have a maximum size for attachments. In the past, if an elog attachment was larger than this size, the email server refused
to accept this email and no notification is sent. Now one can specify the maximum allowed email attachment size with
Max email attachment size = <n> |
|
Re: CSS reference in Email for private logbooks, posted by Stefan Ritt on Fri Dec 21 14:04:41 2018
|
I changed the code ot include the CSS file directly in the email body. So no need any more for external CSS files. I dropped the "Email CSS URL"
option as well.
Stefan |
|
elog program does not respect "Allow edit" list, posted by Heinz Junkes on Mon Mar 11 11:18:02 2019
|
| submissions via the elog - program can overwrite entries even if the user has no edit rights |
|
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. |
|
Re: elog program does not respect "Allow edit" list, posted by Heinz Junkes on Wed Apr 24 10:21:58 2019
|
Thanks for the answer. The real problem is that you can overwrite existing entries even if you have set an entry to "read only", i.e. you have
forbidden further editing.
Heinz |