> I have a play with the Preset text setting and see what I can come up with. By the
> way there is a spelling mistake in the config.html page. In the Conditional
> Attributes section you use the Preset text setting as an example but have spelt it
> as "Prset text ="

Thanks, fixed.

Hi 

Is there a repository of elog configuration files for newbies to lookup and
learn ? I have seen the 'contributions' elog - useful as it is ... it is not
much. I would appreciate if someone can point out such a site where people
have contributed their elog configuration files.

Thanks,
AnandO.

> Is there a repository of elog configuration files for newbies to lookup and
> learn ? I have seen the 'contributions' elog - useful as it is ... it is not
> much. I would appreciate if someone can point out such a site where people
> have contributed their elog configuration files.

Have a look at the elog:Config+Examples. The configuration of this Forum for
example is there, covering most of the available options.

- Stefan

Hi,

We have set up a elog server at our institute. The configuration file is
attached. We have the following queries:

1. When replying to another reply in a thread, the author_name attribute is
not substitued (as desired). Since this is a mandatory field, we are not
able to send the reply message. However, reply to the originial message
works fine.

2. "Use Email From = string" prepends an additional "" to the "From"
field in the e-mails.

3. "Fixed Attributes Reply = Subject" fixes the subject line while replying.
However when we add "Category" attribute to this list, it breaks.

Can someone help us?

Suggestions and tips will be thankfully recieved.

> 1. When replying to another reply in a thread, the author_name attribute is
> not substitued (as desired). Since this is a mandatory field, we are not
> able to send the reply message. However, reply to the originial message
> works fine.

Preset on reply Author = $long_name

Do not use "Remove on reply".

> 2. "Use Email From = string" prepends an additional "" to the "From"
> field in the e-mails.

This has been fixed recently, please update.

> 3. "Fixed Attributes Reply = Subject" fixes the subject line while replying.
> However when we add "Category" attribute to this list, it breaks.

I tried to use your config file and add

Fixed attributes reply = Subject, Category

and it worked as expected. What kind of "break" did you observe?

> > 1. When replying to another reply in a thread, the author_name attribute is
> > not substitued (as desired). Since this is a mandatory field, we are not
> > able to send the reply message. However, reply to the originial message
> > works fine.
> 
> Preset on reply Author = $long_name
> 
> Do not use "Remove on reply".

This worked. Thanks.

> 
> > 2. "Use Email From = string" prepends an additional "" to the "From"
> > field in the e-mails.
> 
> This has been fixed recently, please update.

Agani, thanks for the information.

> 
> > 3. "Fixed Attributes Reply = Subject" fixes the subject line while replying.
> > However when we add "Category" attribute to this list, it breaks.
> 
> I tried to use your config file and add
> 
> Fixed attributes reply = Subject, Category
> 
> and it worked as expected. What kind of "break" did you observe?

For me, when I put the Category in the fixed attributes for reply, I see the
Category but when I actually try to send the message - it says Category not
entered. I am sure I am doing something very stupid. Please help.

- Anand.

> For me, when I put the Category in the fixed attributes for reply, I see the
> Category but when I actually try to send the message - it says Category not
> entered. I am sure I am doing something very stupid. Please help.

No, it was a bug, which I could reproduce now. I fixed it in revision 1.554. It will
be contained in the next release.

Hi

We have setup a elog server and would like to import a bunch of emails as
elog entries. Is there some way we can do this ? Since there are hundreds of
emails, it is not possible to post them individually as new elog entries.

Many thanks,
Anand.