Hi,

I've set up my ELOG configuration to display one summary line in the list view. However, a word from the next line creeps in from time to time. You can see this in my logbook - look at the 'Text' column for entries 805, 802 and 800 for instance. The word 'Shift' is from the second line of the entry, but it has been added to the summary text for some reason. Any ideas how I can fix this?

ben

 Your problem comes from the fact that you probably did not enter the HTML text body with the build-in editor, but copy-and-pasted it from somewhere else. ELOG determines the end of a line by looking at the line-feed character (\n), and your HTML text does sometimes not contain this character at the end, but only the HTML paragraph tag (</p>). I added some code in SVN revision 2131 to look also for the HTML tags properly, so if you upgrade to that version, it should be fine for you.

Hello,

one question regard Options: For e. g. I am using the following command: Options Categories = NT, 2000, XP, Linux
Now I would like to delete the entry NT. But that would cause, that NT is no longer available in the search function. So I wonder if there is a way to deactivate an attribute?

Thanks!

Uwe

A deactivate option is not implemented. The only possibility you have is to enter the search string drictly in the url, like

http://<host>/<logbook>/?Category=NT

Thanks for the quick answer!

best regards,

Uwe

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.

Thank you very much for you help in advance.

Best Regards

Johannes Liegl

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.