problem with required attributes, posted by Stefan Siegel on Wed Aug 7 15:43:28 2002
|
When an entry is submitted with an required attribute missing one gets to
the resubmit page. When you the click your browsers back button all
previously filled attribute field are blank.
Is there a workaround to get the old text back?
used versions:
Elog 2.0.5
Netscape 4.76
Best regards,
Stefan |
Edit an existing message overwrites attributes with preset values, posted by Stefan Siegel on Fri Aug 9 12:40:23 2002
|
Hello,
Is there a possibility to prevent elog to overwrite attribute values when
editing an old message? The old values are overwriten with the preset
options for that attribute.
But sometimes you will preserve attribute text and /or options from the old
message.
Thank you for your help. Regards,
Stefan |
Re: Edit an existing message overwrites attributes with preset values, posted by Stefan Siegel on Fri Aug 9 13:04:58 2002
|
> > Is there a possibility to prevent elog to overwrite attribute values when
> > editing an old message? The old values are overwriten with the preset
> > options for that attribute.
> > But sometimes you will preserve attribute text and /or options from the
old
> > message.
>
> The option "Fixed attributes = ..." will do the job.
Ok, but is there a possibility to preserve the fields of the old message, but
still be able to edit it. This would be a nice feature in the case of an entry
with lots of attributes (set to something different then the preset values).
After submiting the message you realize : one option was wrong and now you
want to edit it without changing the other options again.
Is this possible?
Thank you and best regards,
Stefan |
Error while trying to change password (elogd 2.1.0), posted by Stefan Siegel on Mon Aug 12 11:01:51 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)
Regards,
Stefan |
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 |
Problem with konqueror and pulldown menu (in config menu), posted by Stefan Siegel on Fri Aug 16 10:14:19 2002
|
Hi ,
currently I am running Elog 2.1.1; when using a konqueror browser (ver.
2.2.1, kde 2.2.1) the admin user cannot access in the Config menu the Login
infos for other users except himself. The pulldown menu "Select user" is
shown, but when the admin selects another user the info fields (Login name,
full name, email) are not updated. They still show the attribute values for
the admin user himself.
Is there a solution available?
Thanks (also for this very useful tool) and regards,
Stefan |
documentation fro elconv, posted by Stefan Siegel on Fri Aug 16 11:21:20 2002
|
Hi,
is there a documentation for the elconv tool available?
Regards,
Stefan |
Error with not existing user name, posted by Stefan Siegel on Wed Sep 11 18:37:27 2002
|
Hi,
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!
Regards,
Stefan |