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.

The problem is that in running elog-3.1.4-1 (and upper versions) css-file name in a code of a page has some random symbols before file-name, for example: <link rel="stylesheet" type="text/css" href="ø9öÿeLogOUK.css">. It was found that the problem is resolved if a string “Password file=passwd” is deleted, but in this case it is impossible to set passwords to the users.

Here is an example of configuration file which is taken from the forum and just one string (CSS=elogOUK.css) has added to the code

[global]

; port under which server is listening

Port = 8080

CSS = eLogOUK.css

[Accelerator]

Comment = Accelerator Logbook

; use user level password access

Password file = passwd

Login expiration = 1000

Admin user = ritt

Self register = 1

; look and feel

Guest menu commands = Back, Find, Login, Help

Guest find menu commands = Find, Login, Help

Date format = %B %d, %Y

; attributes

Attributes = Author, Author Email, Category, Subject

Options Category = Routine entry, Shift summary, Problem, Fix, Question, Info, Other

Extendable attributes = Category

Required Attributes = Category, Subject

Thread display = $Subject, entered by $author on $Entry date

Quick filter = Date, Category

; title as shown in the browser

Page Title = Accelerator Logbook - $subject

; preset author and email

Preset Author = $long_name

Preset Author Email = $user_email

; these attributes cannot be changed

Locked Attributes = Author, Author Email

; only author can change its own entry

Restrict edit = 1

; options for reply

Subst on reply subject = Re: $Configuration Name

Remove on reply = Author, Author Email

; No Email notification

Suppress Email to users = 1

____________________________________________________________________

What can be done to resolve this problem?

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.
On the first load of this page the link to the css file is sometimes corrupted by having some garbage characters in it.
<link rel="stylesheet" type="text/css" href="ƒŒüthemes/name.css">

I found the bug in the code and made a PR on the bitbucket. Here is the commit to fix it yourself.
https://bitbucket.org/merrx/elog/commits/cea193ded7161bb6d1f67725ca109d2d4341128a

Best wishes,
Sebastian

Good afternoon Sebastian!
Thank you very much for your help.

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.

Compilation occurs in Cygwin.

Version elog – 3.1.4-3.

Please help solve this problem.

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 splitting the information between two linked logbook tabs?

Can the size of the application log file affect performance?

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.

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 edit time = 0" in this specific logbook behaves differently to the admin setting as it simply sets the time to 0. Is this behavior intended or a bug? I guess a workaround is to specify the edit limitation not in global but in all logbooks seperately.