It turned out to be a setting of our re-routing of requests that re-escaped the '%'. Sorry for the noise. Cheers

I would be too lucky if I just could fix this as I fix some ELOG problems! I guess hundreds of physicists right now are pondering about what could have gone wrong in data taking, because nobody really believes that this is a real effect. 

 Well, It may be our implementation of re-routing web requests: The requested string in elog  is prefixed by %5E (^) and postfixed by %24 ($). But in my case, the '%' is again escaped as %25 so the prefix becomes %255E that is not understood by elog as being '^' ...

I will see with my experts in routing if this is something that can be fixed in our configuration. But when elog processes the input string, it should un-escape these characters and find back the '^', no?

Strange. In this forum it works without extra characters. Just try it yourself. Do you have any strange configuration? Can you send me a minimal elogd.cfg which produces that error, maybe derived from the example elogd.cfg from the distribution.

- Stefan 

Hi,

We have a problem with the search command: Since our last upgrade to v2.9.0-2418 the searched string is pre- and postfixed with ASCII character expressed in % format, see the attached image. The searched string is prefied with %255E and postfxed by %2524 in the URL. And teh search fails. This affects searches from drop-down menus.

Thanks in advance.

 In order to copy (or move) files from one logbook to another, you first need to ensure that  the
appropriate commands are in the section of elogd.cfg of the logbook the files move *from* (called 'current')

 - made up elogd.cfg to show this, and obviously only the pertinant lines

[Global]

Group = current, Y2011, Y2010, Y2009...

...

 [current]
...
Menu commands = New, ... Copy to, ...
...
Copy to = Y2011, Y2010, Y2009 ...
...
 - end of made up example.
 
So to solve your problem, the <logbook list> is simply the list of logbooks in
this part of elogd.cfg after the 'Copy to =' line in the elogd.cfg file (Y2011, Y2010, Y2009...)  

You also need to ensure that the directory to which the entries are to be copied to exists!

('Move to' would be faster if you are going to delete the entries in 'current' afterwards, but as always, it depends on

your perception of risk.)

For the user, the logbook list is the set of logbooks that appear in the
drop-down menu by the side of "Copy to" in the menu bar, and it allows you to
move that entry (or thread of entries if more than one) to the selected destination.

---

My reason for answering this is because I have actually done this operation 'in
anger' some time ago and regularly since, and would have answered before if Stafan had not beaten me
to it.  I used what was Stefan's second method, which, for those who are
reasonably confident with file manipulation, is far faster, and, dare I say,
less prone to 'unexpected' issues - some here will know what I'm
getting at.

So I say, "Back up your files and take the plunge", I would have put something
else but this is a family friendly forum.

But you must bear in mind my views are those seen through the filter of a
regular Elog ab-user, which may be why Stefan worked so hard to answer before
me ;-)

Anyway, Stefan <i>et al</i> have got CERN's faster-than-light particle problem to deal with this morning.

 Sorry, about this dumb question but with  "Copy to = <logbook list> " what is the format of  <logbook list>?

Is it just the "logbook Name" or is it the actual path name   "http://something/somethingelse"?

I have two identical servers (IBM X337) setup on the same LAN with Ubuntu Linux 10.04 LTS with ELOGD running (Compiled from tarbell) with the same exact package install base. (Only difference between the two servers is the hostname, and the ELOGD.CFG global section)