Date attribute in Quick filter, posted by Peter Rienstra on Thu Oct 25 12:04:02 2007
|
Stefan,
I downloaded the latest source (ELOG V2.6.5-1946) to solve another problem. But now I get:
Error: "Attribute "Date" for quick filter not found", see attachment.
In the configfile I have: Quick filter = Date
A bug?
(It works fine, so it's not really a big problem.) |
Re: Date attribute in Quick filter, posted by Stefan Ritt on Thu Oct 25 20:15:46 2007
|
Peter Rienstra wrote: | I downloaded the latest source (ELOG V2.6.5-1946) to solve another problem. But now I get:
Error: "Attribute "Date" for quick filter not found", see attachment.
In the configfile I have: Quick filter = Date
A bug? |
Yep. Fixed in V2.6.5-1951. |
extendable options, posted by Arno Teunisse on Sat Oct 13 15:32:23 2007 
|
Hello
running ELOG V2.6.5-1890
Snap of the config file :
=======================
; attributes
Attributes = OS, Version, Klant , Category, Subject
Options OS = AIX{1}, HP-UX{2} , Redhat{3} , Suse{4}, Fedora{5}, SUN{6}
Options Category = Documentation, disk , network , software , backup , boot,
Options Klant = None, Cust1 , Cust2 , Cust3 , Cust4, Cust5
{1} options Version = 4.3, 5.1 , 5.2 ,5.3
{2} options Version = 10.20, 11.11, 11.23
{3} options Version = 4.0
{4} options Version = 10.0
{5} options Version = 5.0,6.0,7.0
{6} options Version = 5.6,5.7,5.8,5.9,5.10
extendable Options = Category, Klant, OS , Version
============ end of snap
When I click the "Add Version" button Elog end's with a "Internal error, no
valid header!" after hitting the submit button. ( See attachments )
An other problem is when I add a new OS and a new Version at the same time. The
OS is added , ( without the {7} extension.) and no new "{7} options version = "
gets added.
Is there a way to get this going? |
Re: extendable options, posted by Stefan Ritt on Mon Oct 22 16:33:50 2007
|
Arno Teunisse wrote: | When I click the "Add Version" button Elog end's with a "Internal error, no
valid header!" after hitting the submit button. ( See attachments ) |
"Extendable Options" are currently only possible outside any condition. While
Options Version = 1,2,3
will work, the following will not
{1} Options Version = 1,2,3
I will add a note to the documentation about this. |
Re: extendable options, posted by Stefan Ritt on Mon Oct 22 21:22:28 2007
|
Arno Teunisse wrote: |
; attributes
Attributes = OS, Version, Klant , Category, Subject
Options OS = AIX{1}, HP-UX{2} , Redhat{3} , Suse{4}, Fedora{5}, SUN{6}
Options Category = Documentation, disk , network , software , backup , boot,
Options Klant = None, Cust1 , Cust2 , Cust3 , Cust4, Cust5
{1} options Version = 4.3, 5.1 , 5.2 ,5.3
{2} options Version = 10.20, 11.11, 11.23
{3} options Version = 4.0
{4} options Version = 10.0
{5} options Version = 5.0,6.0,7.0
{6} options Version = 5.6,5.7,5.8,5.9,5.10
extendable Options = Category, Klant, OS , Version |
Actually me previous statement was incorrect. Extendable options work also under conditions. Your problem is that you specified
{1} options Version = 4.3, 5.1 , 5.2 ,5.3
instead
{1} Options Version = 4.3, 5.1 , 5.2 ,5.3
(note the capital O). If you change that, it will work. Anyhow I changed the code so that the case of these statements is ignored in the future. |
opening a local html file, posted by Arno Teunisse on Sun Oct 21 22:35:19 2007
|
Hello
I've managed to create several logbooks that are an index of a (slow) shared
directory. Now I use elog to search for files that are located on the slow
shared directory and just have to click on the link in the elog logbook to open
the file. Every day a simple batch file and 2 perl scripts will recreated the
elog logbooks. So updates are done without any user input. ( mainly via the
elog.exe program ) This all works great.
To access the shared files in the above mentioned logbooks i use for one of the
attributes : (All on one line) :
<A HREF='\\////HOST/dir 1/dir 2/dir 3/dir 4/dir 5/dir 6/dir 7/filename.doc' target='_blank'>filename.doc</a>
And this works great.
In the above the .doc may be replaced with .html, .xls or whatever WINDOWS
supports.
Here is my question :
Now I want to open a .html on my local drive. Should be possible but i seem to
miss the correct format. With local drive I mean the drive that elog is running
on. In my case this is C:
I tried :
file:///c:\dir 1\dir 2\file.html
file:///c:/dir 1/dir 2/file.html
<A HREF="file:///c:\dir 1\dir 2\file.html">file.html</a>
<A HREF="file:///c:/dir 1/dir 2/file.html">file.html</a>
<A HREF='file:///c:\dir 1\dir 2\file.html'>file.html</a>
<A HREF='file:///c:/dir 1/dir 2/file.html'>file.html</a>
and much more variants of the above. ( the first two examples do not respect the
Spaces in directory names and file name, tried some quoting, but does not help)
In my browser ( IE7.0) i see in the status bar :
file:///c:/dir%201/dir%202/file.html
That seems to be OK. But nothing happens when i click the left click the link in
the elog logbook.
The above contains the correct directories and filenames. I know that the file
is there because right clicking the link in elog and selecting "Save Target As"
will save the file. However just left clicking the link to the file does not
open the browser to display it. ( As i stated : this works on a shared drive, but not
on a local drive.)
Any suggestions ? |
Re: opening a local html file, posted by Stefan Ritt on Mon Oct 22 17:38:32 2007
|
Have a look at
http://kb.mozillazine.org/Links_to_local_pages_don't_work |
Quick Filter and boolean option question, posted by Arno Teunisse on Fri Oct 19 22:59:31 2007
|
; BUG : When "Contract" is at the second position in the "Attributes".
; We See in the "Quick Filter" a pulldown showing "Serial Number" with only "0" or "1" ,
; this is NOT what i want or is expected !!!
[WRONG]
Attributes = Server , Contract , ContractID, Serienummer,Locatie , Category , TEST4
Options Category = Server, Printer , Disk, Router
; Please notice that the boolean attribute is at the second position in the attributes <list>,
;this is a bug, otherwise the "Quick Filter" gets it wrong. So Boolean attributes must always
;be the last item when defining the Attributes
Options Contract = boolean
Quick Filter = Server , Serienummer , Category
; This is OK : Just moving the "Contract" to the end of the "Attributes"
; Now the "Quick Filter" is a normal entrie field and not a pulldown.
; So , now i can enter a serialnumber. This is what i want and is expected.
[OK]
Attributes = Server , ContractID, Serienummer,Locatie , Category , TEST4 , Contract
Options Category = Server, Printer , Disk, Router
; Please notice that the boolean attribute is the last in the attributes <list>, this is a bug, otherwise the "Quick Filter" gets it wrong. So Boolean attributes must always be the last item when defining the Attributes
Options Contract = boolean
Quick Filter = Server , Serienummer , Category
Just switch between "wrong" and "OK" to see the "quick filter" changes. |
Re: Quick Filter and boolean option question, posted by Arno Teunisse on Sun Oct 21 00:17:34 2007
|
Arno Teunisse wrote: | ; BUG : When "Contract" is at the second position in the "Attributes".
; We See in the "Quick Filter" a pulldown showing "Serienummer" with only "0" or "1" ,
; this is NOT what i want or is expected !!!
[WRONG]
Attributes = Server , Contract , ContractID, Serienummer,Locatie , Category , TEST4
Options Category = Server, Printer , Disk, Router
; Please notice that the boolean attribute is at the second position in the attributes <list>,
;this is a bug, otherwise the "Quick Filter" gets it wrong. So Boolean attributes must always
;be the last item when defining the Attributes
Options Contract = boolean
Quick Filter = Server , Serienummer , Category
; This is OK : Just moving the "Contract" to the end of the "Attributes"
; Now the "Quick Filter" is a normal entrie field and not a pulldown.
; So , now i can enter a Serialnumber. This is what i want and is expected.
[OK]
Attributes = Server , ContractID, Serienummer,Locatie , Category , TEST4 , Contract
Options Category = Server, Printer , Disk, Router
; Please notice that the boolean attribute is the last in the attributes <list>, this is a bug, otherwise the "Quick Filter" gets it wrong. So Boolean attributes must always be the last item when defining the Attributes
Options Contract = boolean
Quick Filter = Server , Serienummer , Category
Just switch between "wrong" and "OK" to see the "quick filter" changes. |
Arno Teunisse wrote: |
Hello again
Maybe it's not nice to begin with "BUG:" but i was in a hurry. Sorry for that.
Because I did not get an answer i think i must ask it in an other way : De [WRONG] and [OK] configurations are identical except for the order in which the Attributes appear. This causes the "Quick Filter" problem, as you can see when changing between the [Wrong] and [OK] tabs.
Am I missing some config setting or i am lost here ?
By the way : I see you are running version 2.6.5-1937. Is there a windows version of that too ?
with kind regards
|
|
Re: Quick Filter and boolean option question, posted by Stefan Ritt on Sun Oct 21 12:21:09 2007
|
Arno Teunisse wrote: | Because I did not get an answer i think i must ask it in an other way |
The reason you did not get an answer was not that you asked the wrong way, but simply that I'm pretty busy these days. So just be patient, I won't forget you. And sending several support requests certainly does not help you  |
Re: Quick Filter and boolean option question, posted by Arno Teunisse on Sun Oct 21 22:51:07 2007
|
Thanks Stefan , i'll wait. Sorry.
Stefan Ritt wrote: |
Arno Teunisse wrote: | Because I did not get an answer i think i must ask it in an other way |
The reason you did not get an answer was not that you asked the wrong way, but simply that I'm pretty busy these days. So just be patient, I won't forget you. And sending several support requests certainly does not help you  |
|
Re: Quick Filter and boolean option question, posted by Stefan Ritt on Mon Oct 22 17:27:45 2007
|
Arno Teunisse wrote: | When "Contract" is at the second position in the "Attributes".
We See in the "Quick Filter" a pulldown showing "Serial Number" with only "0" or "1" ,
this is NOT what i want or is expected !!! |
Yes, this is indeed a bug. I fixed it in SVN revision 1940. There will be soon a new release containing this fix. |
Add date and time stamp to file upload, posted by Fergus Lynch on Thu Oct 4 12:03:30 2007
|
Hi,
Been using ELOG for a couple of years now and I am very impressed with its functionality.
I would like to request a new feature - add date and time stamp to file upload. We use ELOG (amongst other things!) as a change log and this would really allow allow more accurate records to be kept. For instance we upload router config files (to record changes)and having the exact upload date would be a big enhancement, especially when there are a lot of attachments.
Many Thanks in Advance
Fergus |
Re: Add date and time stamp to file upload, posted by Stefan Ritt on Thu Oct 4 17:19:56 2007
|
Fergus Lynch wrote: | I would like to request a new feature - add date and time stamp to file upload. We use ELOG (amongst other things!) as a change log and this would really allow allow more accurate records to be kept. For instance we upload router config files (to record changes)and having the exact upload date would be a big enhancement, especially when there are a lot of attachments. |
There is already a time and a date stamp. If you look in the logbook directory, you see attachments preceded with the date and time when they were submitted. You can see this date/time when you click on the attachment, such as in
http://midas.psi.ch/elogs/Config+Examples/040519_000348/elogd.cfg
where you will see it even in the URL (May 19th, 2004, 0:03:48) in the above case. I agree that this is not so obvious. If you make a proposal where this date/time should be displayed, I can easily add it. |
Re: Add date and time stamp to file upload, posted by Fergus Lynch on Tue Oct 9 11:48:17 2007
|
Stefan Ritt wrote: |
Fergus Lynch wrote: | I would like to request a new feature - add date and time stamp to file upload. We use ELOG (amongst other things!) as a change log and this would really allow allow more accurate records to be kept. For instance we upload router config files (to record changes)and having the exact upload date would be a big enhancement, especially when there are a lot of attachments. |
There is already a time and a date stamp. If you look in the logbook directory, you see attachments preceded with the date and time when they were submitted. You can see this date/time when you click on the attachment, such as in
http://midas.psi.ch/elogs/Config+Examples/040519_000348/elogd.cfg
where you will see it even in the URL (May 19th, 2004, 0:03:48) in the above case. I agree that this is not so obvious. If you make a proposal where this date/time should be displayed, I can easily add it. |
Hi, I think this would be great new functionality, so I would propose the date/time stamp for an uploaded file was placed just after the file size text that appears at the far right hand side of all attachments.
Many Thanks
Fergus |
Re: Add date and time stamp to file upload, posted by Stefan Ritt on Fri Oct 19 21:44:00 2007
|
Fergus Lynch wrote: | Hi, I think this would be great new functionality, so I would propose the date/time stamp for an uploaded file was placed just after the file size text that appears at the far right hand side of all attachments. |
I implemented this as you can see at elog:Linux+Demo/14 . The new feature will be contained in the next release, and will also work for entries made before this feature was implemented. |
default css style , posted by Arno Teunisse on Thu Oct 18 23:18:03 2007
|
The default tiny.css has a bug in it.
It's calling a class that does not exists. The class name is : list1h and list2h. So I added :
/* Just highlighting the last entries , Added by Arno Teunisse . Elog is calling
these, but they are not defined in the css style sheets*/
.list1h { border:1px solid #3080FF;
border-top:1px solid white;
border-left:1px solid white;
background-color:Yellow;
text-align:center;
}
.list2h {
border:1px solid #3080FF;
border-top:1px solid white;
border-left:1px solid white;
background-color:Yellow;
text-align:center;
}
If these are NOT defined the user that edit's an entrie and does a "list" afterwards get's the colorization of a menu and all is shifted onto the left.
with kind regards
Arno Teunisse
|
Re: default css style , posted by Stefan Ritt on Fri Oct 19 09:08:06 2007
|
Arno Teunisse wrote: | The default tiny.css has a bug in it.
It's calling a class that does not exists. The class name is : list1h and list2h. |
Thanks Arno. I didn't touch tiny.css since a couple of years now, and the list1h/2h were introduced after I wrote tiny.css. Actually compact.css had the same problem. I added this to the SVN version, so it will be included in the next release. |
how to use the find calendar, posted by Arno Teunisse on Sat Oct 6 16:47:44 2007
|
Hello
In the find page you use a calendar popup from which the user can click on a date and the date boxes are filled in with the correct date. Can I use that calendar also? If so, can you show me an example of it's usage. |
Re: how to use the find calendar, posted by Arno Teunisse on Sat Oct 6 17:15:59 2007
|
Arno Teunisse wrote: | Hello
In the find page you use a calendar popup from which the user can click on a date and the date boxes are filled in with the correct date. Can I use that calendar also? If so, can you show me an example of it's usage.
I found it , Sorry for the question, ( RTFM ) Read The Fucking Manual )
|
|
testing for the limit of the elog database , posted by Arno Teunisse on Sat Oct 6 15:39:12 2007
|
Hello
To test elog i created a very large databasefile ( 071006a.log = 39MB ) via an import.
Nothing special. At the import I already got a message to increase "Max content length" to 22420822 in the global section. Below is the what i've done. There are no attachments involved, as you can see.
[global]
port = 80;
Max content length = 22420822
[DAP]
Theme = default
Attributes=Klant,Doc
Quick filter = Klant
So there are only 2 user defined fields in the database.
Everything works ......... but terrible slow : is there a rule of thumb for the size of the database ? |
Re: testing for the limit of the elog database , posted by Stefan Ritt on Sat Oct 6 15:44:51 2007
|
Arno Teunisse wrote: | So there are only 2 user defined fields in the database.
Everything works ......... but terrible slow : is there a rule of thumb for the size of the database ? |
Yes. The rule of thumb is that currently elog runs fine for a few 10000 entries. At 100000 entries it starts getting slow. I have already in my to-do list the task to improve the performance for large databases, and I have a rough idea where the bottleneck is, but I pushed the priority low because not many people have large databases right now (but it might change in the future). How many entries do you have? (It's not the size of the entries, but the number!) |
Re: testing for the limit of the elog database , posted by Arno Teunisse on Sat Oct 6 15:56:13 2007
|
Stefan Ritt wrote: |
Arno Teunisse wrote: | So there are only 2 user defined fields in the database.
Everything works ......... but terrible slow : is there a rule of thumb for the size of the database ? |
Yes. The rule of thumb is that currently elog runs fine for a few 10000 entries. At 100000 entries it starts getting slow. I have already in my to-do list the task to improve the performance for large databases, and I have a rough idea where the bottleneck is, but I pushed the priority low because not many people have large databases right now (but it might change in the future). How many entries do you have? (It's not the size of the entries, but the number!) |
That's a quick answer. I just was testing. I'm trying to introduce elog at work, so i'm not having an actual database in production. In the test database I had 125386 entries. Two column: "Customers name" and "documents".
By the way : my email address has changed : how do I change that ??
Thanks |
Re: testing for the limit of the elog database , posted by Stefan Ritt on Sat Oct 6 16:11:50 2007
|
Arno Teunisse wrote: | By the way : my email address has changed : how do I change that ?? |
Click on 'Config'. |
|