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 |
|
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. |
|
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 |
|
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 |
|
Restrict edit time = 0 behavior intended?, posted by Chris Körner on Mon Nov 15 11:35:55 2021
|
Hi,
I have set the options "Restrict edit time = 24" and "Admin restrict edit time = 0" in [global]. This way can only edit entries
for 24 hours while the admin can forever. I now want a single logbook where all users have unlimited time to edit entries. However, setting "Restrict |