Elog v2.7.8 does not show substituted attributes while editing or replying, posted by Dennis Seitz on Thu Aug 19 22:58:45 2010
|
Since we updated to 2.7.8 we've found a problem.
Previously, when we used
Subst on reply subject = Re: $subject
The new "Re: " text would appear in the "subject" field while the user was editing their reply, and they could edit or delete it.
Since 2.7.8, however, it does not appear while editing, but shows up only after the user submits their entry. We would prefer that this appears while the user is editing, because in some cases we want the users to have the option to modify this text. Was this intentional? Is there a way to restore the previous functionality?
Thank you! |
Elog v2.6.2-1722 appears to have broken "Suppress default [0|1|2|3]" option on Windows XP box, posted by Gregory M. Caughey on Wed Oct 11 11:37:03 2006
|
Hi Stefan!
Been running Elog-2.6.2-1714 successfully for a while and yesterday decided to download and experiment with the latest Elog-2.6.2-1722 build. I want to report a possible bug involving the "Suppress default" option when running build 2.6.2-1722 on a Windows XP laptop. I installed 2.6.2-1722 into a development folder and copied my current production 'elogd.cfg' file and other custom files to the development folder. Test postings produced the following results:
1.) The "Suppress default [0|1|2|3]" option causes the [] Suppress Email notification to display or not display as expected.
2.) However, email notifications will be sent under all circumstances regardless of which parameter selected.
3.) Downgrading to Elog-2.6.2-1714 produces the expected behavior.
I am running Windows XP with all current upgrades and security patches and Internet Explorer 7 - version: 7.0.5700.6
Regards, Greg |
Elog stopped working, posted by Gillian Sabberton on Tue Sep 8 14:36:10 2009
|
We have been running elog for a couple of years now and this morning it stopped working.
We have tried to rstart it and it says successful start but still does not run, when doing a restart it says stop failed start success.
Does anyone have any ideas.
thanks
|
|
Elog stopped working, posted by John Becker on Wed Mar 29 14:48:40 2017
|
Dear all,
I have elog version 3.12-bd75964 installed on an Ubuntu OS. We started working with it yesterday and today I was informed that the users could not connect to the elog. When I tried it was also not possible to get to the elog website. After restarting the Ubuntu machine everything was back to normal.
Is there a log I can check to find out why the elog stopped working?
Regards,
John |
|
Elog stability with multiple users, posted by Alan Grant on Wed Feb 18 04:57:32 2015
|
Are there any known or reported daemon stability issues with an increase of concurrent users logged in to view and search entries, while the elog client is also adding 5 to 10 new entries every minute during a peak 2-hour period each day? |
|
Elog source code giving errors when compiling about missing header files, posted by rahul bhandari on Wed Dec 21 20:15:19 2016
|
I downloaded the source code from the git repository which contained the new fix that was made for the missing username-crash error. I tried compiling the elogd.c file using a GCC compiler and it gave an error about missing header files. It first gave an error about netdb.h file and when I commented that header file call, it gave further errors for other header files. I do not really understand why it gives an error about that. |
|
Elog on Windows Server 2008 R2, 64 bit, posted by Alan Grant on Fri Mar 16 23:59:10 2012
|
Any known issues running in Win Server 2008 R2, 64 bit environment? We sometimes lose connection with the Elog app (ssl) and wonder if due to 64bit or other factor in this set up. A forum search does not explicitly reveal any clues however I did find an entry from someone posting a similar question without a response yet (#67061). |
|
Elog on FreeBSD, posted by Truupe on Mon Aug 5 20:45:15 2024
|
Anyone using elog on FreeBSD nowadays? I know it used to be in the ports tree about 10 years ago but seems to be abandoned. Tried to compile from source on 14.1, but no luck there. |