How to lock a specific entry?, posted by Manoel Couder on Tue Sep 14 17:48:52 2021
|
Hi All,
I am using elog to track technical changes in an experiment but also to log what experimentalist are doing during an experiment. For the latter,
I would like to be able to lock those entries from being further edited after the expertiment if finished. Is there a way to do that? |
Re: How to lock a specific entry?, posted by Stefan Ritt on Tue Sep 14 18:18:03 2021
|
You can either lock all entries or none. So I would propose you set up two logbooks, one for technical changes which is not locked and one for what experimentalists
are doing which is locked. Locking can be done a certain time after an entry has been made (like 1h, 1d, 1 month etc.). Or you simply make the logbook
read-only. |
|
Large log file size, posted by Alan Grant on Mon Aug 30 03:08:15 2021
|
| Can the size of the application log file affect performance? |
|
Re: Large log file size, posted by Stefan Ritt on Mon Aug 30 08:41:14 2021
|
If the logbook files are getting big, searching text in entries can take quite some time. But if you have a log file logging all activities, that should
not slow down elog since the server just appends at the end of that file which is a quick operation.
Alan |
Adding entries without being logged in stopped working with attachments, posted by Andreas Luedeke on Sat Aug 28 21:32:09 2021
|
Hi Stefan (et al),
we have several logbooks that allow to add new entries without logging in first.
That still works, as long as these entries don't have any attachments. |
|
Logging Main page entries, each with multiple ongoing events , posted by Alan Grant on Wed Jul 21 16:16:29 2021
|
Is there any way to log child events on the detail pages for a fixed number of entries on the main page? For example, I have 15 vehicles to enter on
the main page, ID'd by Vehicle Number. Within each of those entries I will be logging ongoing repair service entries with certain attributes.
So how might I design this concept without having repeating vehicle entries on the main page for every service event, and preferably without |
|
Deny option and Guest commands, posted by Janusz Szuba on Mon Jul 19 18:41:29 2021
|
Hi,
I have a logbook with guest access and guest can also enter a new entry (in config: Guest List Menu commands = New, Find, Select, Login).
For other reason in a global section, I put |
|
Drop attachments here..., posted by Xuan Wu on Wed Jun 23 03:48:22 2021
|
| The function of "Drop attachments here..." is only for root user? I'd like it could be used by all users. |
|
Re: Drop attachments here..., posted by Sebastian Schenk on Mon Jun 28 14:53:44 2021
|
I can't confirm this behavoiur. In our instance, every user can use the attachment function of the elog.
Either through "Drag&Drop" or "Browse&Upload" in the entry editor.
What do you mean by "root" user? |
|
Re: Drop attachments here..., posted by Xuan Wu on Mon Jun 28 18:41:31 2021
|
I just used my own account to test the "Drag&Drop" function in this forum , and it failed. In our case, we need to upload
ten more images into logbook at once, it's more effective to use "Drag&Drop" than "Browse&Upload" feature for "Browse&Upload"
only can choose one attachment at once, but "Drag&Drop" can choose several attachments at once. The admin user can use this |
|
Re: Drop attachments here..., posted by Sebastian Schenk on Tue Jun 29 15:21:06 2021
|
In my testings I didn't found this behaviour, but my collegues also reported this issue.
So I searched for the difference between my test setup and the production logbooks.
I believe the "restrict edit = 1" config option may be responsible for this behaviour. |
|
Re: Drop attachments here..., posted by Sebastian Schenk on Tue Jun 29 20:13:36 2021
|
I could figure out the bug. A fix can be found in this commit.
https://bitbucket.org/merrx/elog/commits/c3e3c4af9666006558aaf26d8f4841800e69f9af
Sebastian |
|
Re: Drop attachments here..., posted by Stefan Ritt on Tue Jun 29 20:20:38 2021
|
| Looks good, I merged the pull request. |
|
Re: Drop attachments here..., posted by Sebastian Schenk on Wed Jun 30 13:50:08 2021
|
Thanks for the merge.
I found a more general solution, as there could be the posibility to have the author as "select" or "radio box" input in the
form, where the fix breaks. |
|
Re: Drop attachments here..., posted by Xuan Wu on Wed Jun 30 04:38:21 2021
|
Excellent, Thanks!
Sebastian
Schenk wrote:
I could figure out the bug. A fix can be found in this commit. |
|
Timezome problem, posted by Maxim on Wed Jun 23 15:28:00 2021
|
Good afternoon!
The elog does not see the time zone. It displays UTC + 0. When I transfer old entries to a new compiled log, they are displayed 3 hours earlier
(my time zone is UTC + 3). When creating a new record, it creates them in the UTC + 0. |
|
Problem with a self-compiled code., posted by Maxim on Mon May 31 14:51:39 2021
|
Dear, sir! There is a problem with a configuration file.
The code was compiled by Cygwin (gcc-core, gcc-g++, make, gdb, libssl-dev). After a compilation a reference to our own css-file was written
in configuration file and css-file was included in a folder “themes/default” of the project. |
|
Re: Problem with a self-compiled code., posted by Sebastian Schenk on Thu Jun 3 16:02:02 2021
|
Hello Maxim,
I just stumbled on a similar issue. Also with a self-compiled elogd on Ubuntu.
We also use a custom css and by clicking on the "New" or "Reply" or "Duplicate" the elog generates the entry editor. |
|
Re: Problem with a self-compiled code., posted by Maxim on Wed Jun 23 14:08:15 2021
|
Good afternoon Sebastian!
Thank you very much for your help.
Sebastian |