know that illness...  :-(  but was the last of the family of 4 people

i'd like to ask for an other usefull change togehter with this and how url's are 
handled by elog:

since there may be spaces in the name of a logbook (ex. "1stWordOfLogbook 
2ndWordOfLogbook") it is very userfriendly to name logbooks. also it's easy th 
make a reference for a other entry by copy and paste:

Display ThisURL = http://localhost:8080/$logbook/$message id

however, using spaces in the logbook name may give a wrong result, because the 
url would be http://localhost:8080/1stWordOfLogbook

and the space as well as the 2ndWordOfLogbook//$message id is only normal text.

may it be possible stefan, to replace the space in an url (starting 
with "http://") with a "+" or "%20"? this would allow to automate some things. 
actual the logbook name has to be hardcoded.


> > I think you should be using tcp_hostname instead of gethostname if it is 
> > specified.
> 
> Sorry my late reply, I was ill for some time. I implemented your suggestion in
> revision 1.522 which is available from CVS.
> 
> Note that there is also the "URL = xxx" option in the configuration file which
> lets you specify the whole URL including the host name.

Ok, I changed that in version 2.5.5-3. Note that one can also use the "elog:..."
substitution, like

Display ThisURL = elog:$logbook/$message id

Recursive attributes are not possible. All you can do is to define a certain number (like Ingredient1, Ingredient2, Ingredient3) and use Conditional Attributes to show them using the "Show Attributes Edit = ..." option.

To display two attributes in the same row, use 

Format <attribute> = 1

for the second attribute.

 Ok, thank you for your answer.

I guess my next question is whether it is possible to have, for example, 2 attributes:

Options Ingredient1 = 

Options Ingredient2 = 

Extendable options = Ingredients1, Ingredients2

sharing the exact same possible list of values.

Thanks agin.

If you add via an option to one Ingredient, you have to add it to the other as well. There is no automatic way to do that. 

Have you tried the config option "Preset on reply <attribute> = $date". On a reply, the <attribute> will be preset with the current date.

Stefan

I have not heard of that problem before.

The key to fix is to reproduce it, then teach me how to reproduce it. Only errors I can reproduce on my computer I am able to fix.

Best regards,

Stefan

 Does this occur if you are adding an attachment?  As I am blessed with forever using ancient systems, I've seen fields and indeed text  being cleared  because they were entered between clicking on 'Upload' for an attachment and the .png files being generated and displayed.  Answer here is patience - I use all too much of mine up in this exercise, sadly.