Re: Forgot Password, posted by Stefan Ritt on Wed May 2 09:17:56 2012
|
Christopher Lee wrote: |
Stefan Ritt wrote: |
Christopher Lee wrote: |
We seem to have a problem with retrieving user passwords using the forgot password system
|
Thanks for reporting that bug. With the help of your config file I finally could reproduce and fix it. The fix is contained in SVN revision 2462.
|
Thanks mate.. Glad to know it wasn't just me going insane? I'll keep an eye out for the new file
|
For the new version have a look here: http://midas.psi.ch/elog/faq.html#21 |
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 searches from drop-down menus.
Thanks in advance. |
Re: Spurious characters in the searched string, posted by Stefan Ritt on Mon Sep 26 10:38:59 2011
|
Olivier Callot wrote: |
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.
|
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 |
Re: Spurious characters in the searched string, posted by Olivier Callot on Mon Sep 26 11:16:19 2011
|
Stefan Ritt wrote: |
Olivier Callot wrote: |
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.
|
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
|
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? |
Re: Spurious characters in the searched string, posted by Olivier Callot on Mon Sep 26 14:49:48 2011
|
Olivier Callot wrote: |
Stefan Ritt wrote: |
Olivier Callot wrote: |
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.
|
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
|
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?
|
It turned out to be a setting of our re-routing of requests that re-escaped the '%'. Sorry for the noise. Cheers |
Fckedit and quotation style sheets, posted by Robert Heine on Wed Feb 2 15:26:53 2011
|
Dear colleagues,
I have edited my own style sheets for elog, but if I use the reply function while having fckedit as editor, the quotations have the standard elog colors, not mine. With elog's own editor, I get my colors. I figured out that fckedit inserts the quote as HTML-block with "hard coded" colors, but I am not able to find the template fckedit uses for it! Does anyone know the path to this template?
Thank you in advance
Robert Heine |
Re: Fckedit and quotation style sheets, posted by Stefan Ritt on Mon Feb 7 16:44:54 2011
|
Robert Heine wrote: |
Dear colleagues,
I have edited my own style sheets for elog, but if I use the reply function while having fckedit as editor, the quotations have the standard elog colors, not mine. With elog's own editor, I get my colors. I figured out that fckedit inserts the quote as HTML-block with "hard coded" colors, but I am not able to find the template fckedit uses for it! Does anyone know the path to this template?
Thank you in advance
Robert Heine
|
That's actually a limitation of fckedit. It simply does not interprete any style sheets, that's why actually the elogd program hard-wires the colors etc. Sorry for that. |
openssl - openssl/ssl.h, posted by Christoph Kukulies on Tue Nov 9 18:05:00 2010
|
Nasty nasty. I prepared a longish post and only because I forgot to click an Icon of choice, all my message is lost.
Thus in short:
openssl/ssl.h isn't there.
I assume I got to get it from openssl.org.
But where do I put it in the compilation tree?
--
Christoph
|