Re: Error: Attribute <date> not supplied., posted by Barend on Tue Oct 22 10:54:51 2013
|
| David Pilgram wrote: |
| Barend wrote: |
|
Stefan/Andreas,
When I reply to an existing Logbook entry, I get the error page "Error: Attribute Audit Date not supplied. Please go back and enter the Audit Date field."
The configuration file uses:
Required Attributes = Audit No, Audit Date, Audit Type, Finding No, Finding Level, Section, MOE Procedure, Finding Details, Auditor, Deadline, Responsibility
Fixed Attributes Reply = Audit No, Audit Date, Audit Type, Finding No, Finding Level, Section, MOE Procedure, Finding Details, Auditor, Deadline, Responsibility
Type Audit Date = date
Type Deadline = date
The combination "Required Attributes" and "Fixed Attributes Reply" does not work for date-fields.
As soon as I disclose the date fields from either "Required Attributes" or "Fixed Attributes Reply" the error is no longer evident.
But I want the "Audit Date" and "Deadline" to entered during a new Record and they shall not be changed during a reply.
Is this a bug -or- do I have to change the configuration?
Thanks & regards, Barend
|
Hi Barend,
I can reproduce your point.
I've found various work-arounds, but possibly the best one is to remove "Audit Date" and "Deadline" from the Required Attributes line. True you won't get a warning saying that they were not entered for the first entry (if you didn't enter them, that is), but all subsequent replies run as you would want.
Another way is if you *preview* your entry, you can then submit it and that works. This seems to work by bring up a different page where you can edit all those Fixed Attributes. (I'm not sure that Preview is meant to do that, but it does and it's a work-around).
Or, if you remove "Audit date" and "Deadline" from the Fixed Attributes Reply (as you did) seems to work in the same way. But I see that you don't want the opportunity for these to be changed.
I note that if you get this error message and go back, the message that you may have written is erased (this is unusual, it doesn't do this if you have not supplied an attribute on the first entry, say).
So I suspect this is a bug, possibly not detected before; perhaps no-one had tried this combination. |
Hi David,
Thanks for the reply. I'll review the options and decide what is the best option to move forward.
Regards, Barend |
|
Re: Error with not existing user name, posted by Stefan Ritt on Tue Sep 24 16:59:11 2002
|
> Elogd v. 2.1.2:
>
> When trying to acces a password protected Log (global password file) with a
> non existing username one gets the response : cannot open file : <pw
> filename>
>
> Better would be a message like: wrong user or password!
Has been fixed in 2.2.0 |
|
Re: Error while trying to change password (elogd 2.1.0), posted by Stefan Ritt on Mon Aug 12 17:04:30 2002
|
> When logging in with a username and password; then trying to logout or
> change password one gets the following message:
>
> Error: Parameter value too big. Please increase VALUE_SIZE and recompile
> elogd ; Please use your browser's back button to go back
>
> (up to now I have not yet tried to recompile - may be it works then)
That's strange. This error should only occur if someone uses a user name or
password with more than 256 characters, which I hope is not the case. Have
you tried changing your password etc. in this forum? It also runs 2.1.0 on
Linux.
I made a version under
http://midas/cgi-bin/cvsweb/~checkout~/elog/elogd.c?rev=2.67&content-
type=text/plain
which has improved error output for this problem, maybe this helps. |
|
Re: Error while trying to change password (elogd 2.1.0), posted by Stefan Siegel on Wed Aug 14 13:44:12 2002
|
> > When logging in with a username and password; then trying to logout or
> > change password one gets the following message:
> >
> > Error: Parameter value too big. Please increase VALUE_SIZE and recompile
> > elogd ; Please use your browser's back button to go back
> >
> > (up to now I have not yet tried to recompile - may be it works then)
>
> That's strange. This error should only occur if someone uses a user name or
> password with more than 256 characters, which I hope is not the case. Have
> you tried changing your password etc. in this forum? It also runs 2.1.0 on
> Linux.
>
> I made a version under
>
> http://midas/cgi-bin/cvsweb/~checkout~/elog/elogd.c?rev=2.67&content-
> type=text/plain
>
> which has improved error output for this problem, maybe this helps.
Hi,
changed the VALUE_SIZE from 256 to 512. That seems to fix the problem.
Regards,
Stefan |
|
Re: Error when attempted to submit an entry, posted by Stefan Ritt on Wed Nov 13 16:31:28 2013
|
| Hung Dao wrote: |
| One of my users reported that he received this error when attempted to submit an editing entry. Basically he is only one to edit this entry. When go ahead to press the button, the entry is updated successfully. What cause and how to prevent this error not to populate? Thanks |
Please read the documentation in https://midas.psi.ch/elog/config.html und the option "Use Lock". If you don't need locking, just turn it off. |
|
Re: Error sending Email via "XXX.XXX.XXX.XXX", posted by Stefan Ritt on Thu Jun 28 17:12:11 2007
|
| JJ Sheppard wrote: | 220 Welcome to the @Mail v4.4 SMTP Server ( Exim )
EHLO server.XXXX.net
250-MX1.SPIDERHOST.COM Hello server.XXXX.net [XXX.XXX.XX.XX]
250-SIZE 10485760
250-PIPELINING
250-AUTH LOGIN
250 HELP
|
The problem there is that your SMPT server does not reply with
250 OK
which my server does. So elogd was waiting 3 seconds for "OK", and then aborted. I change the code (now in SVN revision 1871) to look for "250 " (with one blank at the end). You have to update from SVN, recompile and try again. Anyhow elogd only supports plain login authentication ("AUTH LOGIN"), which not all SMPT servers accept. You have to see. |
|
Re: Error sending Email via "XXX.XXX.XXX.XXX", posted by JJ Sheppard on Fri Jun 29 16:14:16 2007
|
| Stefan Ritt wrote: |
| JJ Sheppard wrote: | 220 Welcome to the @Mail v4.4 SMTP Server ( Exim )
EHLO server.XXXX.net
250-MX1.SPIDERHOST.COM Hello server.XXXX.net [XXX.XXX.XX.XX]
250-SIZE 10485760
250-PIPELINING
250-AUTH LOGIN
250 HELP
|
The problem there is that your SMPT server does not reply with
250 OK
which my server does. So elogd was waiting 3 seconds for "OK", and then aborted. I change the code (now in SVN revision 1871) to look for "250 " (with one blank at the end). You have to update from SVN, recompile and try again. Anyhow elogd only supports plain login authentication ("AUTH LOGIN"), which not all SMPT servers accept. You have to see. |
This is what I get now, Is this the Auth Login problem you were speaking of?
Email from elog@XXXXX.net to jsheppard@XXXXX.net, SMTP host XXX.XXX.XXX.XXX:
220-server.XXXXXX.net ESMTP Exim 4.66 #1 Fri, 29 Jun 2007 10:03:22 -0400
220-We do not authorize the use of this system to transport unsolicited,
220 and/or bulk e-mail.
EHLO server.tracstar.net
250-server.tracstar.net Hello server.XXXXXX.net [XXX.XXX.XXX.XXX]
250-SIZE 52428800
250-PIPELINING
250-AUTH PLAIN LOGIN
250-STARTTLS
250 HELP
AUTH LOGIN
Username:
XXXXXXXX
Password:
XXXXXXXX
535 Incorrect authentication data
==== Return ================================
HTTP/1.1 302 Found |
|
Re: Error sending Email via "XXX.XXX.XXX.XXX", posted by Stefan Ritt on Fri Jun 29 16:16:58 2007
|
| JJ Sheppard wrote: | This is what I get now, Is this the Auth Login problem you were speaking of?
Email from elog@XXXXX.net to jsheppard@XXXXX.net, SMTP host XXX.XXX.XXX.XXX:
220-server.XXXXXX.net ESMTP Exim 4.66 #1 Fri, 29 Jun 2007 10:03:22 -0400
220-We do not authorize the use of this system to transport unsolicited,
220 and/or bulk e-mail.
EHLO server.tracstar.net
250-server.tracstar.net Hello server.XXXXXX.net [XXX.XXX.XXX.XXX]
250-SIZE 52428800
250-PIPELINING
250-AUTH PLAIN LOGIN
250-STARTTLS
250 HELP
AUTH LOGIN
Username:
XXXXXXXX
Password:
XXXXXXXX
535 Incorrect authentication data
|
No. It looks like PLAIN LOGIN is supported, but your username/password is wrong. Ask your SMPT system administrator. |
|