If

1. Elog is configured to use webserver authentication, and
2. the user reported by the webserver does not exist in the password file, and
3. the "Guest Menu commands" configuration is set in "elogd.cfg", and
4. a logbook is accessed,

then Elog returns with a redirect (302) to the logbook itself, causing the loop.

The fix here is to remove the "Guest Menu commands" configuration from "elogd.cfg".

Source code location: https://bitbucket.org/ritt/elog/src/30ada1df634529c8011c27275c52a05b01b7b3d6/src/elogd.cxx#lines-27599

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.

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

I suspect that this might be a Debian packaging issue; however no one replied to my help request on the Debian forums so I try posting the question also here. I insatlled Elog on my Debian Jessie machine, I can open it with a browser but when entering a new post just a simple plain text editing box is shown instead of the WYSIWYG editor, and no drag and drop area for attachments is shown. When I start the elog service with "systemctl start elog" I get this suspect message in the journal: "FCKedit NOT detected". Indeed, I see that the elog installation creates a symlink which I guess is supposed to point to the fckeditor installation, which nevertheless is missing:

root@static-3-080:/usr/share/elog/scripts# ll fckeditor
lrwxrwxrwx 1 root root 15 Oct 25  2014 fckeditor -> ../../fckeditor
root@static-3-080:/usr/share/elog/scripts# ll ../../fckeditor
ls: cannot access ../../fckeditor: No such file or directory

Is this a Deban misconfiguration or a bug in Elog? thanks

Hi all,

I'm experiencing an issue on Kubuntu 24.04 where the WYSIWYG editor (in HTML mode) doesn't appear at all. This happens across multiple browsers (tested with Firefox and Chromium). The editor area is simply blank, without any visible toolbar or editable content area.

Has anyone encountered this on Kubuntu or found a workaround? Any tips would be appreciated!

Thanks in advance,
Pawel

Is it possible to make the logbook summary screen sort differently
 
For example on a customer name field it displays as follows :-

AEF
AXA
Abc
Acd
Ade
Aef
aaa
aab

Its sorting alphabetically but is putting upper case characters before 
their lower case equivalents, which in a customer list where lots of 
initials are used its making the list look non sorted rather than truely 
based on the character regardless of case.

Thanks in advance.

Something to add to the wishlist:

- Type <attribute> = user

This would define an attribute as being of the type "user" which is a list
of login id's as defined in a password file or on the "Login user =" line. 
In a dataentry form the presence of this ATTRIBUTE would result in a
picklist of loginid's and/or fullnames.