Hm, maybe my question is silly, but why don't you just use the "Duplicate" command instead of renaming and misusing "Copy to"??

Here is the relevant excerpt from the documentation (https://midas.psi.ch/elog/config.html#general):

Menu commands = <list>
This option specifies the menu commands displayed on top of a single logbook page. For certain installations, it can be useful to disable some commands. Following commands are possible:

• New - Enter new logbook entry
• Edit - Edit current logbook entry
• Delete - Delete current logbook entry
• Reply - Submit a reply to current entry
• Duplicate - Duplicate the current entry with the possibility to change some values
• [...]
• Copy to - Copy entry to other logbook
• [...]

The commands are always in English, independent of the language = ... setting, and are automatically translated into the specified language.
If this option is not present, following default is used:

Menu commands = List, New, Edit, Delete, Reply, Duplicate, Find, Config, Help

Somehow, I've missed to see that option :)

Thanks :)

Menu commands = List, New, Edit, Delete, Reply, Duplicate, Find, Config, Help

So did I [thankful there is no shame face icon].

Menu commands = List, New, Edit, Delete, Reply, Duplicate, Find, Config, Help

 Still struggling with this issue, if anyone has managed to solve it let me know.   I've done the obvious and checked ownership/ permissions of the elog folders and they are exactly the same as etc/var/www, which is working in apache.

> Since elog 2.6.0 we cannot redirect our elog via apache2.
> 
> in apache2.conf we have (had for a long time):
> Redirect permanent /elog http://elog.oursite.com/elog/
> ProxyPass /elog/ http://elog.oursite.com:8080/
> 
> When visiting the url, this results in:
> The proxy server received an invalid response from an upstream server.
> The proxy server could not handle the request GET /elog/myelog/.
> 
> After testing we found that ELOG V2.6.0-beta2 works just fine.
> 2.6.0 stable crashes after visiting a redirected url.
> 
> Running on debian sarge

Have you tried 2.6.1. I released it just recently, so I don't know when it will be available for Debian. Have you
checked that your "URL = xxx" statement in the config file is correct? I see above "myelog", while the proxy
passes requests to "elog".

> > Since elog 2.6.0 we cannot redirect our elog via apache2.
> > 
> > in apache2.conf we have (had for a long time):
> > Redirect permanent /elog http://elog.oursite.com/elog/
> > ProxyPass /elog/ http://elog.oursite.com:8080/
> > 
> > When visiting the url, this results in:
> > The proxy server received an invalid response from an upstream server.
> > The proxy server could not handle the request GET /elog/myelog/.
> > 
> > After testing we found that ELOG V2.6.0-beta2 works just fine.
> > 2.6.0 stable crashes after visiting a redirected url.
> > 
> > Running on debian sarge
> 
> Have you tried 2.6.1. I released it just recently, so I don't know when it will be available for Debian.

No it doesn't work with 2.6.1. I hoped it would be fixed, but I should have reported it sooner.
I compiled 2.6.1 myself.
The original version was a debian package, after that, we compile elog ourselves and copy elogd manually over the old
version. Just to stay up-to-date.

> Have you checked that your "URL = xxx" statement in the config file is correct? I see above "myelog", while the
proxy passes requests to "elog".

I changed our urls, just to be safe.
myelog is a 'sublogbook', like forum here. http://elog.oursite.com/elog/myelog

We are running V2.6.0-beta2 and it runs fine, without any alterations to our config files.
All previous versions runned fine too.

update:
After further testing on a different server, it seems to be an issue with the proxy and the proxy_http modules in sarge.
after loading and unloading  proxy_http this is the error:
The proxy server received an invalid response from an upstream server.

unfortunately instructions do not exist to cover every possible situation.

but in general, to migrate elog to a new machine, I would say do this:
- on new machine, install new elog from scratch
- copy the old elogs from "logbooks" on the backup disk to the new elog "logbooks"
- merge the config file by hand (this may require a few tries)

feel free to ask for more help with any of these steps here.
K.O.

> unfortunately instructions do not exist to cover every possible situation.
> 
> but in general, to migrate elog to a new machine, I would say do this:
> - on new machine, install new elog from scratch
> - copy the old elogs from "logbooks" on the backup disk to the new elog "logbooks"
> - merge the config file by hand (this may require a few tries)
> 
> feel free to ask for more help with any of these steps here.
> K.O.

Thank you so much. It worked this way.