Spurious characters in the searched string, posted by Olivier Callot on Mon Sep 26 08:13:10 2011 
|
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 |
Re: Spurious characters in the searched string, posted by Stefan Ritt on Mon Sep 26 10:38:59 2011
|
Olivier Callot wrote:
Hi, |
|
Re: Spurious characters in the searched string, posted by Olivier Callot on Mon Sep 26 11:16:19 2011
|
Stefan Ritt wrote:
|
|
Re: Spurious characters in the searched string, posted by Olivier Callot on Mon Sep 26 14:49:48 2011
|
Olivier Callot wrote:
|
elogd crash for special query, posted by Andreas Luedeke on Thu Oct 27 11:29:08 2011
|
A query to a logbook can crash the demon.
Query:
|
undesired side effect of using an attribute "Entry", posted by Andreas Luedeke on Thu Oct 27 14:05:35 2011
|
If you use an attribute "Entry" then the internal variable "entry time" will expand to the last value of
"$Entry"+" time", e.g. if you use it in "Thread display = $entry time, ..."
|
Global Synchronization with 2.9.0, posted by Steve Nahn on Wed Nov 9 20:15:38 2011
|
Hi
I just updated my mirror server, which I just use as a backup to my main server, to 2.9.0 and found that after logging in (the selection
page is not protected, but the individual logbooks are) and coming back to the selection page I no longer get the "Synchronize all logbooks" |
|
Elog does not work after installing MS12-006/MS12-012 on Win 7, posted by Allen on Wed Jan 11 22:19:49 2012
|
After patching a windows 7 computer with MS12-006, can no longer connect to elog, get page cannot be displayed
See
http://support.microsoft.com/kb/2643584 |