HELP - URGENT - odd ELOG behaviour, posted by Sara Vanini on Wed Jun 1 15:05:59 2011
|
|
Re: ELOG deamon stuck in find_thread_head(), posted by Soren Poulsen on Wed Jul 6 12:06:01 2011
|
Soren Poulsen wrote:
|
Global Synchronization with 2.9.0, posted by Steve Nahn on Wed Nov 9 20:15:38 2011
|
Hi
I just updated my mirror server, which I just use as a backup to my main server, to 2.9.0 and found that after logging in (the selection
page is not protected, but the individual logbooks are) and coming back to the selection page I no longer get the "Synchronize all logbooks" |
Re: Truncation of the displayed text in Summary view of the list of entries, posted by Olivier Callot on Wed Mar 14 15:08:17 2012
|
Stefan Ritt wrote:
|
FCKEditor doesn't show up in Windows 8?, posted by John Haggerty on Wed Feb 20 02:45:45 2013
|
After installing ELOG on a new Windows 8 machine, I found everything working fine... until I went to make a new entry. New entries work... but
the FCKEditor toolbars do not show up. I tried a variety of things (start as a service, start not as a service, run as administrator), but nothing
made the toolbar appear that I coumd find. The ELCode editor toolbar appears, but the nifty FCKEditor toobar never appears. I could not figure |
kerberos authentication NOT working, posted by Fabio Sella on Wed Oct 30 17:57:38 2013
|
Hi guys,
we configured a kdc server using OPENLDAP as backend. We installed on it elog and configured the Kerberos Authentication on one logbook as follows:
Authentication = Kerberos, File |
Max Logbooks for Email notify, posted by Oliver Kleinau on Wed Apr 8 11:40:27 2015
|
Hi,
we've got 109 logbooks in Elog. Whenever I set a notify for all logbooks in configuration menu it is limited to 73 entrys. After saving the
changes the rest of the entrys are cut off. |
Problem with autosave functionality when combined with no 'edit' button, posted by Thomas Lindner on Tue May 5 07:33:50 2015
|
We recently tried upgrading the ND280 elog instance to elog 3.1.0. [1] We seem to have some problems with this 'auto-save' functionality.
Specifically, it doesn't seem to play nice with the fact that we prefer to disable user's ability to edit old messages. So we have (up to
now), had the following set of commands specified in elogd.ccfg |