ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
69709
|
Tue Nov 7 22:07:24 2023 |
| Matteo Mannini | thanksmatteo.mannini@unifi.it | Question | Linux | 3.1.3 | Re: Restricting entries view by user |
Dear Stefan,
thanks to the answer you gave to my colleague.
Now, attempting to follow your suggestion... If we will create several logbooks, one for each user,
1) there is a way to automatically duplicate all the entries in anoter "global" elog without loosing them and keeping them updated between the global and the individual logbooks?
2) alternatively how I could activate a search in all these user logbooks (and only in this set of logbooks without searching in the others logbook present in the same file conf)? shall I gnereate a separated elog instance only for this set of logbooks? how to let this search to all option available only to a reduced number of "superusers" that are not "administrators?
thanks
Matteo
Stefan Ritt wrote: |
No, this is not possible with the current version of Elog, so indeed everybody needs their own logbook.
Stefan
Leonardo Tacconi wrote: |
Good morning,
I would like to ask you whether it is feasible to establish a logbook that limits access to entries, enabling each user to view only their own.
Although creating a logbook per user is an apparent solution, it does not meet my requirements.
Thank you in advance.
Leonardo
|
|
|
69708
|
Thu Nov 2 11:46:42 2023 |
| Stefan Ritt | No, stefan.ritt@psi.ch | Question | Windows | 3.1.3 | Re: Restricting entries view by user |
No, this is not possible with the current version of Elog, so indeed everybody needs their own logbook.
Stefan
Leonardo Tacconi wrote: |
Good morning,
I would like to ask you whether it is feasible to establish a logbook that limits access to entries, enabling each user to view only their own.
Although creating a logbook per user is an apparent solution, it does not meet my requirements.
Thank you in advance.
Leonardo
|
|
69707
|
Thu Nov 2 11:38:36 2023 |
| Leonardo Tacconi | leonardo.tacconi@unifi.it | Question | Windows | 3.1.3 | Restricting entries view by user |
Good morning,
I would like to ask you whether it is feasible to establish a logbook that limits access to entries, enabling each user to view only their own.
Although creating a logbook per user is an apparent solution, it does not meet my requirements.
Thank you in advance.
Leonardo |
69706
|
Tue Oct 24 08:12:38 2023 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | latest | Re: Cannot send Emails |
ELOG has not change in the last years in that respect, but I know that mailer get more and more picky about encryption etc. So you probably have to convince your mailer to accept the pw as it comes from ELOG, or do not require a pw for that specific client.
Stefan
John wrote: |
Hello, my sending of emails was working a while back but I have not checked on it in a few months and found out I am getting authentication errors sending to my MTA (mailer). I was using a base64 to encode the pw but now my mailer (gandi.net) rejects it. Has anything changed over the last couple of years with Elogs code that would be affecting this? I just upgraded (Linux) and changed my testing grounds to non-production and the same problem exists. Thing is I CAN send using other programs, but not with Elog. It is impertive I figure this out or have a work around.. but a 'work around' does not seem like a possible task since all the work (forums and such) will be via my Elog server.
Thanx, John
|
|
69705
|
Mon Oct 23 20:35:54 2023 |
| John | john@secondcomingtechnologies.com | Question | Linux | latest | Cannot send Emails |
Hello, my sending of emails was working a while back but I have not checked on it in a few months and found out I am getting authentication errors sending to my MTA (mailer). I was using a base64 to encode the pw but now my mailer (gandi.net) rejects it. Has anything changed over the last couple of years with Elogs code that would be affecting this? I just upgraded (Linux) and changed my testing grounds to non-production and the same problem exists. Thing is I CAN send using other programs, but not with Elog. It is impertive I figure this out or have a work around.. but a 'work around' does not seem like a possible task since all the work (forums and such) will be via my Elog server.
Thanx, John |
69704
|
Mon Oct 23 16:15:06 2023 |
| Stefan Ritt | Usestefan.ritt@psi.ch | Question | Linux | 3.1.4 | Re: read-only elog server |
Use
Menu commands = List, Find, Help
to remove all command which let you create or edit entries (New, Reply, Edit, ...)
Then do the same with "List menu commands = ..."
/Stefan
Germano Massullo wrote: |
Good day. I am writing this post to ask how I can turn an elog website into a read-only version that will stay online for historical documention purposes.
I tried to search on Elog documentation but I had no success
Thank you and have a nice day
|
|
69703
|
Mon Oct 23 15:20:32 2023 |
| Germano Massullo | germano.massullo@cern.ch | Question | Linux | 3.1.4 | read-only elog server |
Good day. I am writing this post to ask how I can turn an elog website into a read-only version that will stay online for historical documention purposes.
I tried to search on Elog documentation but I had no success
Thank you and have a nice day |
69702
|
Wed Oct 11 23:09:36 2023 |
| Laurent Jean-Rigaud | lollspam@free.fr | Question | Linux | V3.1.4-2e0f4719 | Re: Fail to upload enclosure in ELOG |
Ok, i reply to myself as i could resolve the problem by changing the alpine Linux image to Debian light.
After debugging, the problem seems to be the compilation option used for alpine packets, which is not fully compatible when running on NAS Intel cpu.
The problem disappeared with Debian light, which should be less "aggressive" for optimization. I think the core is generated during imagemagick lib call (png, jpeg,pdf, ...).
Cheers
Laurent Jean-Rigaud wrote: |
Hi,
I currently testing last ELOG version from git in a docker with LDAP activated (https://hub.docker.com/r/usinagaz/elog-ldap). The goal is to use it on Synology NAS server, associated with local LDAP server.
The reverse proxy is done by embedded DSM nginx, according to FDQN associated to ELOG service (elog.corp.com). In Docker, URL is set to elog.corp.com.
All is good, but when I post any enclosure in any elog post, the elogd exits and docker is automatically restarted. The browser shows an error 405 generated by nginx server.
Do you have any idea of the cause of this problem ?
Thanks for help.
Laurent
|
|