Re: Compiling elog 2.0.4 on Solaris, posted by Stefan Ritt on Tue Aug 6 16:14:42 2002
|
> > > > Comiling elogd 2.0.4 under Solaris obviously fails with
> > > >
> > > > gcc -o elog elog.c -lsocket -lnsl
|
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.
|
|
Re: problem with required attributes, posted by Stefan Ritt on Wed Aug 7 15:51:18 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.
|
|
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
|
|
Re: Edit an existing message overwrites attributes with preset values, posted by Stefan Ritt on Fri Aug 9 12:50: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.
|
|
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.
|
|
Re: Edit an existing message overwrites attributes with preset values, posted by Stefan Ritt on Fri Aug 9 14:59:17 2002
|
> 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
|
|
self-registration, posted by tony summerfelt on Fri Aug 9 21:10:20 2002
|
i seem to be unable to find a clear explanation of how to enable self-registration in the docs.
just to be sure i grepped the doc directory, but the two references to it were in the changelog and the faq.
|