Re: exit status of elog, posted by Stefan Ritt on Mon Jul 8 10:42:38 2002
|
> The exit status of elog is always 1. It should be zero for
> a successful submission.
Has been fixed in 2.0.4 |
|
Re: exclude access to a number of users in one logbook, posted by Stefan Ritt on Tue Apr 30 09:34:52 2019
|
You have a look here: elog:68936
| Nikolas Patronis wrote: |
|
How can I exclude the access of a number of users in one (out of two) logbooks running in the same server and URL?
|
|
|
Re: error: "HTML encoding not allowed" , posted by Stefan Ritt on Mon Dec 17 09:18:51 2012
|
| julia wrote: |
|
Hi all,
I'm absolutely new with ELOG and have only basic programming skills...
I'd like to use ELOG, so I have installed it in my computer to start playing with it (I installed version 2.7.0-1953 because with the latest one I got an error with the elogd.cfg file). I've been able to open the Demo logbook but wasn't able to submit a new entry into it. I get the following error:
"HTML encoding not allowed"
Could you please explain me how I could solve this problem?
I thank you in advance for your help.
|
Version 2.7.0 is very old and has knows problem. Better go with the current version and fix the problem with the elogd.cfg file. |
|
Re: error when searching for POST, posted by Stefan Ritt on Wed Oct 5 13:07:51 2005
|
This bug has been fixed in the current CVS version. |
|
Re: error message from this forum, posted by Stefan Ritt on Wed May 18 19:52:41 2005
|
| Heiko Scheit wrote: | Just after submitting the last message, the following error message was displayed:
Error sending Email via "mailsend.psi.ch": malformed address: synergie-infcom> |
Sombody used an invalid formed email address, like user<at>domain<dot>com, on which the SMTP server complained. I would like to note here that the email addresses registered in this forum are not published in any way, so there is no risk to get spam from that (except the normal elog notifications, which can be turned off easily). |
|
Re: error message "Command Config is not allowed" after registering, posted by Mark Bergman on Wed Feb 15 17:13:08 2012
|
| Mark Bergman wrote: |
|
After registering, elog displays a page with the message:
Error: Command "Config" is not allowed for user ""
However, the registration is successful. This causes confusion, and results in users registering multiple times.
In the elogd.conf file, I have the directive:
Allow Config = bergman
Any suggestions?
|
I loathe the idea of 'bumping' up one's own posting, but here I go...
Has anyone seen this issue, or have any solution? We've got people who register 8 or more times, since they see the "Error" message with each registration. |
|
Re: error message "Command Config is not allowed" after registering, posted by Mark Bergman on Wed Apr 2 19:17:31 2014
|
| Mark Bergman wrote: |
|
After registering, elog displays a page with the message:
Error: Command "Config" is not allowed for user ""
However, the registration is successful. This causes confusion, and results in users registering multiple times.
In the elogd.conf file, I have the directive:
Allow Config = bergman
Any suggestions?
|
Is anyone else seeing this? It's very confusing to new users.
|
Re: error message "Command Config is not allowed" after registering, posted by Mark Bergman on Tue Sep 6 20:09:07 2016 
|
| Mark Bergman wrote: |
|
After registering, elog displays a page with the message:
Error: Command "Config" is not allowed for user ""
However, the registration is successful. This causes confusion, and results in users registering multiple times.
In the elogd.conf file, I have the directive:
Allow Config = bergman
Any suggestions?
|
Well, 5 years after opening this issue, with no responses here, I finally got into the source code and fixed it.
The problem seems to be if eLog is configured to prohibit users (non-administrators) from the "Config" option...but on the initial self-registration, the code goes to the Config screen for the user anyway...resulting in the false error message.
So, I [badly] hacked eLog to fix that, add some debugging/log messages, and to correct a typo.
Attached is the patch against release 3.1.1-1. Try not to cringe too much at my code. :) |