ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66510
|
Tue Aug 11 08:38:56 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Comment | Linux | 2.7.7-2251 | Re: Comment on: Alphabetize Quick Option filter | Ok, that makes sense, so I changed it to
Sort Attribute Options Status = 1
as you suggested.
> (For some reason I could not add this in Dennis's thread.)
>
> I like this new feature, BUT
>
> I happen to have two Options: Options System, and Options Status.
>
> System are a very few items, whereas Status has a long list, which, like Dennis's example, can be added to.
> Keeping the latter in alpha order is great, but it's a shame that the cost is that Options System are also
> sorted alphabetically, whereas it has a natural order which it would be preferable to keep - for example (and
> this is made up)
>
> Options System: 3.1, NT, 2000, XP, Vista
>
> where the natural order here is chronological.
>
> Perhaps the configuration file option could be more specific, for example
>
> Sort attribute Options Status = 1
>
> which would then NOT sort Options System. If both are needed to be sorted, both should be specified, or back to
> the original syntax which defaults to sort *all* Options. |
66513
|
Tue Aug 11 13:25:48 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.6.5 | Re: Logbook Parser |
Steve Williamson wrote: |
excuse my butting in ... I've found the exports useful in the past - however, is is possible to run the export from a script in order to produce reports? Utilities like wget won't work as the export process doesn't return the data as html.
|
That's not true. wget does work. Try that one:
wget --no-check-certificate -O export.csv https://midas.psi.ch/elogs/linux+demo/?mode=CSV1
actaully wget doesn't care if the return is HTML or a GIF image or anything else, it just saves it into the output file. |
66521
|
Mon Aug 31 11:22:20 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.7-2246 | Re: fckeditor update |
Arno Teunisse wrote: |
Hello
Just a few fckeditor related questions. How do elog versions and fckeditor versions relate. ?
Can I just drop another version of the fckeditor over an other version? What things should I consider when doing so ?
thanks for you're time.
|
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. |
66524
|
Thu Sep 3 18:14:26 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | Windows | 2.7.2-2012 | Re: multiple keyword search - regular expression |
Johannes Liegl wrote: |
Dear Sirs,
searching for keywords regular expression becomes very long. Are there any other type easy multiple keyword search supported. For example a keyword search like keyword1 & keyword2 results in different output than a keyword search like keyword2 & keyword1. A simple keyword search like "keyword1 & keyword2 and keyword2 &keyword1 should find all documents in a database containing both keywords resulting in the same output.
|
I had this request already several times. Indeed I myself am not very happy with regular expressions. If anybody knows of any other convenient search method, together with freely available C code, I'm more than happy to include this into elog. |
66526
|
Fri Sep 4 08:33:16 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.7-2246 | Re: chain.crt | > Like many educational institutions we get "educational certificates" that are chain certificates..
>
> With apache the full certificate chain is working as expected..
>
> For elog I copied the appropriate files to server.crt and server.key
>
> Netscape 3 is happy with that setup, Internet Explorer and Opera are mentioning the open certificate chain.
>
> When I tried to copy the file known as SSLCACertificateFile in Apache to chain.crt elogd does not longer work
and
>
> openssl s_client -showcerts -connect <myserver>:<elogd_port>
>
> only shows:
>
> CONNECTED(00000003)
> 25523:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:s23_clnt.c:562:
To be honest I'm not an expert on SSL. I just use following code inside ELOG to initialize the SSL connection:
SSL_CTX *init_ssl(void)
{
char str[256];
SSL_METHOD *meth;
SSL_CTX *ctx;
SSL_library_init();
SSL_load_error_strings();
meth = SSLv23_method();
ctx = SSL_CTX_new(meth);
strlcpy(str, resource_dir, sizeof(str));
strlcat(str, "ssl/server.crt", sizeof(str));
if (!file_exist(str)) {
eprintf("Cerificate file \"%s\" not found, aborting\n", str);
return NULL;
}
if (SSL_CTX_use_certificate_file(ctx, str, SSL_FILETYPE_PEM) < 0)
return NULL;
strlcpy(str, resource_dir, sizeof(str));
strlcat(str, "ssl/server.key", sizeof(str));
if (!file_exist(str)) {
eprintf("Key file \"%s\" not found, aborting\n", str);
return NULL;
}
if (SSL_CTX_use_PrivateKey_file(ctx, str, SSL_FILETYPE_PEM) < 0)
return NULL;
if (SSL_CTX_check_private_key(ctx) < 0)
return NULL;
strlcpy(str, resource_dir, sizeof(str));
strlcat(str, "ssl/chain.crt", sizeof(str));
if (file_exist(str))
SSL_CTX_use_certificate_chain_file(ctx, str);
return ctx;
}
Maybe I need something different for chain certificates, but I don't know. I just copied these calls from the
example which comes with the libssl library which I'm using. Maybe somebody has an idea how this could be
improved. Actually looking at the code I see that the 'chain.crt' file is used. If you send me your files
privately I could try them and see if I get a specific error code from the SSL library. |
66527
|
Fri Sep 4 09:48:55 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.7.7-2246 | Re: Fix text prevents user from editing text during creation, instead of just edit |
Allen wrote: |
When we set Fix text = 1, according to the syntax, this should prevent users from modifying the text field during an edit, but it looks like it is blocking access at both time of edit and creation, meaning you can never add anything to it. Is that the intended functionality?
|
Thanks for reporting that bug. I realized that this was not working at all since a long time. I fixed it in SVN revision 2245. |
66529
|
Fri Sep 4 14:07:31 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | Windows | 2.7.2-2012 | Re: multiple keyword search - regular expression |
Yoshio Imai wrote: | Maybe there is a simple way.
If I understand it correctly, the entries are accepted/rejected for inclusion in the search result list based on one call to regexec. In order to search for N keywords, you could replace this by a loop of N calls to regexec, and only accept the entry if all of them find a match. |
That's right, but some people want something like
(NOT "House" and "Car") OR "Tree"
Using regex'es is a bit exotic for most users. So I hope there is some source code which implements a Google type search more or less 1:1. And Google does not use regex'es (is that right?). Here is the syntax for the Google search:
http://www.google.com/support/websearch/bin/answer.py?hl=en&answer=136861 |
66531
|
Mon Sep 7 15:18:39 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.7-1 | Re: ELcode in Summary Text | > Hello,
>
> Thank you for such a great piece of software!
>
> When displaying the entries in a log book with Summary view, ELCode is not processed in 'Text'. I know
there
> is an option called 'Allow HTML", but is there something similar for decoding ELCode in the Summary 'Text'
field?
>
> Thank you again,
> - Dan
Decoding HTML (or ELCode which translates to HTML) in the summary field is difficult, since the text is
truncated.
Assume you have some code like
Text
<b>Text
<i>Text
----- cut here
</i>
</b>
Sot he bold <b> and italics <i> tags are opened, but closed after the cutting line. In that case the whole page
might render wrongly, because everything after the summary text will be displayed in bold and italics. To fix this I
would have to scan the HTML code and close all open tags "by hand". But since there are very many possibilities,
especially if one used multi-column tables, this is almost impossible without writing my own HTML parser which is
beyond the scope of elog. So the only clean solution I have found so far is to strip off all HTML formatting and
just showing plain text there. |
|