| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68950
|
Tue Apr 30 09:34:52 2019 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 3.1.3 | Re: exclude access to a number of users in one logbook |
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?
|
|
|
67400
|
Mon Dec 17 09:18:51 2012 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.0-1953 | Re: error: "HTML encoding not allowed" |
| 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. |
|
1426
|
Wed Oct 5 13:07:51 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug fix | Other | V2.5.9-2 | Re: error when searching for POST |
This bug has been fixed in the current CVS version. |
|
1153
|
Wed May 18 19:52:41 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | | ? | Re: error message from this forum |
| 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). |
|
67199
|
Wed Feb 15 17:13:08 2012 |
| Mark Bergman | mark.bergman@uphs.upenn.edu | Question | Linux | 2.90 | Re: error message "Command Config is not allowed" after registering |
| 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. |
|
67685
|
Wed Apr 2 19:17:31 2014 |
| Mark Bergman | mark.bergman@uphs.upenn.edu | Question | Linux | 2.90 | Re: error message "Command Config is not allowed" after registering |
| 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.
|
|
68419
|
Tue Sep 6 20:09:07 2016 |
| Mark Bergman | mark.bergman@uphs.upenn.edu | Question | Linux | 2.90 | Re: error message "Command Config is not allowed" after registering |
| 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. :) |
|
65745
|
Mon Feb 18 07:03:29 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | | Re: error "Cannot retrieve host name: No error" using command line in Windows |
| Dan Gawarecki wrote: |
|
I automatically install software on 3 machines in our lab, and at the end of the process, use eLOG to record relevant information for each machine (all running Windows XP) via the command line program elog.exe. 2 of the machines log their info correctly, but on third machine, I get the following error:
Cannot retrieve host name: No error
The error is not very clear (i.e., the error is "no error"?), and furthermore, operationally, the error makes no sense to me, for the three machines are supposedly configured the same.
|
The error is produced by the C routine "gethostbyname". This routine tries to obtain the IP address of your host max13 and fails. The error "no error" is the error passed to elog from the underlying operating system, so please blame Windows for that. I guess you have a problem that on the machine you get the error you have some DNS problem, so this machine does not know max13. Try to "ping" max13 or do a "nslookup max13" to verify this. Maybe you have to add your domain after max13, or put this machine explicitly into \Windows\System32\drivers\etc\hosts.
| Dan Gawarecki wrote: |
|
I am not sure which version of eLOG is being used, but the size of the elog.exe is 139,264.
I suggest a new option be added to display the version information, or display the version info whenever eLOG is execute, or display the version info when "-?" option is used.
|
I added some version information being displayed with the "-?" option. This feature will be contained in the next release. |