As far as I know, it is not possible, if you make a "new" entry.
You could configure the elog, to always PRESET an atribute, but then it is always the same, not the last.

I think the "duplicate" entry function could provide you partly with the functionality you want, as it copies all old values into a new entry.

Regards,
Sebastian

Here are the relevant excepts from the documentation:

Subst <attribute> = <string>
When submitting logbook entries, attribute values can be substituted by some text. This text can contain arbitrary fixed text and following values:

• $<attribute>: The entered value of the attribute itself
• $host: The host name where elogd is running
• $remote_host: The host name of the host from with the entry was submitted
• $short_name: The login name (if password file is present)
• $long_name: The full name from the password file for the current user
• $user_email: The email address from the password file for the current user
• $logbook: The name of the current logbook
• $date: The current date, formatted via "Date format"
• $utcdate: The current UTC date (GMT) and time, formatted via "Date format"
• $version: The version of the ELOG server in the form x.y.z
• $revision: The Subversion reversion of the ELOG server as an integer number
• $shell(<command>): <command> gets passed to the operating system shell and the result is taken for substitution.

Execute new | edit | delete = <command>
It is possible to execute a shell command on the server side after a new message has been submitted, edited or deleted. This feature has been used in the past for SMS notifications over a telephone system and for synchrnonization of the ELOG database with an external SQL database. The <command> can contain substitutions similar to the Subst command. In addition the list of all attachments can be referred to via $<attachments>. The text body of the entry can be referred to with $text. It should be noted that only the first 1500 characters of the text can be used, in order not to exceed the limits of the shell. Following (Unix) command writes a notification into some file:

Execute new = echo "New message wiht ID $message id of type $type from $long_name on $remote_host" >> /tmp/elog.log

It should be noted that this feature can impose a security problem. If someone can edit the elogd.cfg through the Config command of elogd, that person can put malicious code into elogd.cfg and execute it. This is even more severe if elogd runs with root privileges. To avoid such problems, the execute facility is disabled in elogd by default and has to be enabled explicitly with the "-x" command line flag. The administrator has to ensure then of course that only trusted people can edit elogd.cfg.

Have fun!

Andreas

Sorry, I didn't yet have time to implement your request.

Have you considered to download an entry in plain text? Like this entry you can load with

https://midas.psi.ch/elogs/Forum/66555?cmd=Download

which should be much easier to interprete. If you write your entries in ELCode or plain format, it should be even easier. 

The relation is not very "stong". In the past I updated between major version of fckeditor without chaning any elog code, so just give it a try. 

I have found the problem:

the fckeditor folder contains not all necessary files after installation of Elog version 2.7.7.

I have downloaded the fckeditior manually from:

http://www.fckeditor.net/.

and replaced the faulty one with the new one.

Now the editor is running fine and I see the menu bar when I choose Encoding HTML:

elogd 2.7.7 built Jul 31 2009, 13:01:20 revision 2246
FCKedit detected
Indexing logbooks ... done
Server listening on port 8080 ...

Stefan could you please ckeck if some files are missing in the fckeditor folder within the elog version 2.7.7 rev. 2246.

Thanks

Yepp, the editor source code is completely missing in rev. 2.7.7. Thanks for pointing that out. I will include it in 2.7.8 which I will release pretty soon. 

Answer : Problem solved. It is not window7 related. When I did a fresh install ( not installing over the old directory ) everything is working as expected. So I did something wrong with installing over the old elog directory.

Thanks for you're time and the inconvenience.

> In order to avoid having to remember multiple usernames/passwords for
> different systems, is it possible for ELOG to use external authentication
> via Active Directory, etc?

Not yet.