If the older elog has some customized file such as logbooks, elogd.cfg, elog.css, images and so on, What's the best way to update elog to newer release? Is it the only way to copy these files to the new release? |
We have been hosting logbook far (geographically and in internet hops) from our experimental site. Recently we have (finally!) gotten reliable on-site internet, and would like to host the log book on-site.
I have a suspicion that some combination of the -C, -m, and -M flags will allow me to migrate the logbook automagically and with a minimum risk of trouble from concurrent operation on the logbook, and to maintain the existing version as a mirror of the new official on-site version. But documentation is not being very helpful. Can someone say a few more words about what these options do?
I've been experimenting as I compose this and have a suggestion for language that might be useful somewhere in the documentation:
In this context "to clone" means to copy the configuration file and all data files associated with a log book so that I can host an identical logbook on a new host (that is this is the command to migrate a logbook). After cloning the two installation are identical, but no effort is made to keep them so: if you continue to run both copies post made to one will not be reflected in the other.
Is this correct?
I'm still not clear on what the -m and -M options do. |
Hello.
Today I noticed that when I use category filter in the top, right of Elog I got different results, that depends on that if I select Category and Subcategory or just Subcategory option.
What I mean.
- When I select category Software (in Polish "Oprogramowanie") and subcategory Antywirus I got results that have only this subcategory specified (screenshot Category-Software_and_Subcategory-Antywirus.png)
- But when I write by myself Antywirus (which is subcategory of Software) in subcategory option (category leave as default), then I got results that have this, and other subcategories specified (screenshot Subcategory-Antivirus.png).
In my opinion in first example Elog shoud also displays all entries that have Antywirus subcategory specified. Not only when it is the only subcategory.
Sorry, for my english, but I have hope that you can understand what I mean.
Daniel |
Hi there. I have been testing a set-up of elog behind an Apache reverse proxy using the Webserver auth method. Apache has been configured for LDAPS with Active Directory allowing us to restrict Elogs by AD group, something not able to be done with the LDAP module.
Testing with Elog 3.1.4 (on Windows) and also Elog 3.1.5 (compiled on Ubuntu 20.04) I experience an issue that when the user logs in for the first time using the above they get the self registration box asking for name and email, and then once they hit save they get an error that says: "Error: Command "Config" not allowed". Once the error is dismissed it never comes back, but its confusing for users who call for help when they first see it.
Is there a way to skip the self registration with the Webserver auth method? and if not is there a reason for the error?
Attached is a copy of the error and an elog config file. Any ideas?
PS. As a side piece the logout options for Webserver needs some enhancement, maybe an option to close the web browser or tab so that it does not retain the logged in cookies. |
[global]
port = 8080
SSL = 0
Page title = Company X
Entries per page = 25
List page title = Company X
Login page title = Company X
Logbook tabs = 0
Menu commands = Back, New, Find, Download, Logout
List Menu commands = New, Find, Logout
Password file = password.pwd
Max content length = 100000
Allow password change = 0
Enable attachments = 0
Show attachments = 0
Hide attachments = 1
List after submit = 1
Logout to main = 0
Allowed encoding = 5
Default encoding = 1
Welcome title = Electronic LogBook
Summary line = 5
Summary line depth = 100
Show top groups = 0
Search all logbooks = 0
Refresh = 300
Login expiration = 0
Reply string =
Suppress default = 2
Thread display = $category entered by $author on $Entry time
Thread icon = Icon
Preset on reply author = $long_name
All display limit = 300
Start page = ?last=31
Bottom text =
Botton text login =
Resolve host names = 1
Suppress Email on edit = 3
[demo]
Theme = default
Hidden = 1
Authentication = File
Comment = General Linux Tips & Tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
Logout to URL = https://intranet.xyz/
[elog]
Hidden = 1
Authentication = Webserver
LDAP register = 0
Self register = 0
Theme = default
Comment = Elog Site
Preset Author = $long_name
Locked Attributes = Author
Attributes = Category, Codes, Synopsis, Event Date, Author
Options Synopsis = Yes, No
Style Synopsis Yes = background-color:yellow
Style Medical Yes = background-color:green
Type Event Date = datetime
Preset Event Date = $datetime
Date format %A %B %d %Y %H:%M
List Display = ID, Event Date, Category, Codes, Synopsis, Date, Author
MOptions Category = Test 1, Test 2
MOptions Codes = MED, ACH
Required Attributes = Author, Event Date, Codes
Style Codes MED = background-color:green
Page Title = Company X
Reverse sort = 1
Quick filter = Date, Category, Codes
Sort Attributes = Event Date
Logfile = Elog.log
Logging level = 3
Logout to URL = https://intranet.xyz/
Bottom text =
|
Hello,
Tried to use the copy to version, just to create a new copy of a old case in
the same logbook
(e.g, support logbook, user with an old problem, to copy it to a new entry)
What I want is to have the Entry time to be updated to the time it was
copyed, not the original entry time. Moved To should perhaps retain its
original time?
Somethings that is possible or a new feature that has to be implemented?
Thanks for this great software Stefan!
Best regards
Michael Husbyn |