Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 199 of 806  Not logged in ELOG logo
ID Date Icon Author Author Email Categorydown OS ELOG Version Subject
  65670   Fri Nov 30 10:36:21 2007 Reply Gregory M. Caugheycaugheygm@aol.comQuestionWindows2.7.0-1964Re: Display Picture in ELOG Welcome Page

Adam Blandford wrote:

 

Hi

I want to display an image on the title page and have put the following code into the elogd.cfg:

Welcome Title = <img src="pictures/ln2.jpg"><p><font size = 5 color=white>Welcome to My Project Log</font>

I have put the picture "ln2.jpg" in a pictures folder I have created in the root ELOG directory however the image does not show up. Any assistance would be great :)

Thanks in advance

Adam

 

 

Hi Adam,

You might double check your file names vs. HTML tags. It appears in your example above that your HTML tag is requesting a file named: "1n2.jpg" and your image file name is "In2.jpg". Please note that in the first case the file name starts with (1) a numeral one and in the second case the file name start with a capital (I) a capital I.

Greg

  65671   Fri Nov 30 11:34:42 2007 Reply Stefan Rittstefan.ritt@psi.chQuestionWindows2.7.0-1964Re: Display Picture in ELOG Welcome Page

Adam Blandford wrote:

 Hi

I want to display an image on the title page and have put the following code into the elogd.cfg:

Welcome Title = <img src="pictures/ln2.jpg"><p><font size = 5 color=white>Welcome to My Project Log</font>

I have put the picture "ln2.jpg" in a pictures folder I have created in the root ELOG directory however the image does not show up. Any assistance would be great :)

Thanks in advance

Adam

You cannot put the images into a subdirectory. The above link "pictures/ln2.jpg" will translate into a URL

http://<your server/pictures/ln2.jpg

and there the path pictures will be taken as a logbook name, and the server will complain that this logbook does not exist. Unfortunately you cannot see this error message since it happens during the loading of the picture, and the browser just displays a broken picture link. So put your image into the root of the elogd server and it will be fine.

  65672   Mon Dec 3 09:05:16 2007 Reply Stefan Rittstefan.ritt@psi.chQuestion 2.7Re: Icon comment

Uwe wrote:

one idea for improvement. When using the option 'Icon comment' this comment is shown when creating a new entry and moving with he mouse over the icon but it is not displayed in full or summary view. In full or summary view the filename is shown. Not really important, but perhaps an improvement.

I implemented this request in SVN revision #1974.

  65673   Mon Dec 3 11:25:54 2007 Agree Uweuweho@web.deQuestion 2.7Re: Icon comment

Stefan Ritt wrote:

Uwe wrote:

one idea for improvement. When using the option 'Icon comment' this comment is shown when creating a new entry and moving with he mouse over the icon but it is not displayed in full or summary view. In full or summary view the filename is shown. Not really important, but perhaps an improvement.

I implemented this request in SVN revision #1974.

 

Thank you!

Uwe

  65676   Wed Dec 12 16:05:00 2007 Question Mattmatt.phipps@cerner.comQuestionWindows2.7.0-1954ELog Friendly Reporting Tools

We have used ELog for some time now (within the IT industry) for several things (on-call tracking, after-hours work, knowledge base and a few other uses in development).  Now that we have a good base of data, we would like to do some trending analysis.  We have used Excel in the past for this, but it is rather time consuming.  Does anyone have recommendations for tools (hopefully open source) they have used?  I know nearly anything will since ELog uses flat files, but I'm looking for recommendations that you all know works well.

  65677   Mon Dec 17 02:17:20 2007 Question Val Schmidtvschmidt@ccom.unh.eduQuestionMac OSX2.6.1Moving a logbook from one installation to another

I've attempted to move a logbook from an old elog installation to a new one on another system. The version of elog is the same (2.6.1) in both. Both systems have the same name and the logbooks are and installation are going in the same place. So all paths are identical. Also, for the new installation, I've simply recompiled the same sources used to install the original one. The only difference is an upgrade in the OS.
 
I've rsync'd the directory and contents from the old installation to the logbooks/ directory for the new one. I then over-wrote the standard config file with the new one. I then started elogd in the new place.
 
What I find is 
 
a) The default entry from the demo logbook is inserted into my logbook. This I can live with but it was unexpected.
b) The dates for all my entries as shown in my browser have years starting in 1946, rather than 2006. This is particularly odd since all of the actual log files have the correct dates. 
c) The numbering of entries has been reset to 1.
 
 
Can anyone explain what I've done to mucky this up and how to fix it?
 
Thanks in advance,
 
Val
 

  65678   Mon Dec 17 08:13:22 2007 Reply Stefan Rittstefan.ritt@psi.chQuestionMac OSX2.6.1Re: Moving a logbook from one installation to another

Val Schmidt wrote:

I've attempted to move a logbook from an old elog installation to a new one on another system. The version of elog is the same (2.6.1) in both. Both systems have the same name and the logbooks are and installation are going in the same place. So all paths are identical. Also, for the new installation, I've simply recompiled the same sources used to install the original one. The only difference is an upgrade in the OS.
 
I've rsync'd the directory and contents from the old installation to the logbooks/ directory for the new one. I then over-wrote the standard config file with the new one. I then started elogd in the new place.
 
What I find is 
 
a) The default entry from the demo logbook is inserted into my logbook. This I can live with but it was unexpected.
b) The dates for all my entries as shown in my browser have years starting in 1946, rather than 2006. This is particularly odd since all of the actual log files have the correct dates. 
c) The numbering of entries has been reset to 1.
 

That sounds really strange. The only thing I can think of is that the demo entry conflicted with your other entries and two of them have the same entry ID. The entry ID is a unique key which identifies each entry. If you look into the raw logbook file 011108a.log with a text editor, you will see them as

$@Mid@$: 1
Date: Thu Nov 08 18:37:57 2001
Author: Stefan Ritt
Type: Routine
Category: General
Subject: Welcome
Attachment:
Encoding: ELCode
========================================
[B]Congratulations for installing ELOG sucessfully!
[/B]

This is a demo entry to ensure the elogd server is working correctly.
Click [I]"New"[/I] to add new pages and [I]"Delete"[/I] to delete this page.

so in this case the ID is 1. When you rsync'ed your entries into the demo logbook directory, you probably got two entries with the ID 1, which screws up elogd. Try to delete the file 011108a.log before you do the rsync. If you start elogd interactively with the "-v" flag, you will see some debugging output which can you help identify some problems:

[ritt@pc5082 ~/elog]$ ./elogd -v
elogd 2.7.0 built Dec 13 2007, 08:05:12 revision 1977
Config file  : /afs/psi.ch/user/r/ritt/elog/elogd.cfg
Resource dir : /afs/psi.ch/user/r/ritt/elog
Logbook dir  : /afs/psi.ch/user/r/ritt/elog/logbooks/
Indexing logbook "demo" in "logbooks/demo/" ...

Config [demo],                           MD5=F2E39262960C779517FEE576C17B1ED0

Entries:
  ID   1, 011108a.log, ofs     0, thead, MD5=81D89C3C94C6626BB7FF191026040E83
After sort:
  ID   1, 011108a.log, ofs     0
ok
Server listening on port 8080 ...

 

  65679   Mon Dec 17 19:18:13 2007 Reply Val Schmidtvschmidt@ldeo.columbia.eduQuestionMac OSX2.6.1Re: Moving a logbook from one installation to another

 

 

Stefan, I'm still stumped. I'm sorry for the hassle. 

I've removed all the demo entries from both my logbook and the demo. I restarted elog in verbose mode and everything seems normal. I've even run the binary from my old elog installation on the config and logbooks in the new place and it works like a champ.

So I think I've concluded that my new compilation is mucky'd up. The logbooks and config file are fine.

So for the record, the new installation is on MacOS 10.5 (Leopard). The compiler is gcc4.0. There is one warning when I compile:

src/elog.c: In function 'url_encode':
src/elog.c:209: warning: pointer targets in passing argument 2 of 'strlcpy' differ in signedness
 

But this is not likely the problem.
 
So I stuck a debug statement into the code and recompiled to see the dates that are read from the logbook. Here is what I found:
 
DEBUG: Thu Nov 08 18:37:57 2001
DEBUG: Sun, 09 Apr 2006 12:38:31 +52175311
DEBUG: Sun, 09 Apr 2006 12:41:17 +52175311 
DEBUG: Mon, 10 Apr 2006 09:24:26 +52175311
DEBUG: Mon, 10 Apr 2006 09:29:50 +52175311
DEBUG: Mon, 10 Apr 2006 16:15:31 +52175311
DEBUG: Mon, 10 Apr 2006 18:22:16 +52175311
DEBUG: Mon, 10 Apr 2006 18:23:20 +52175311

 

I haven't yet been able to figure out what this last number is and if it should indeed be part of the date. Any ideas here?

Thanks,

-Val

 

Stefan Ritt wrote:

 

Val Schmidt wrote:

I've attempted to move a logbook from an old elog installation to a new one on another system. The version of elog is the same (2.6.1) in both. Both systems have the same name and the logbooks are and installation are going in the same place. So all paths are identical. Also, for the new installation, I've simply recompiled the same sources used to install the original one. The only difference is an upgrade in the OS.
 
I've rsync'd the directory and contents from the old installation to the logbooks/ directory for the new one. I then over-wrote the standard config file with the new one. I then started elogd in the new place.
 
What I find is 
 
a) The default entry from the demo logbook is inserted into my logbook. This I can live with but it was unexpected.
b) The dates for all my entries as shown in my browser have years starting in 1946, rather than 2006. This is particularly odd since all of the actual log files have the correct dates. 
c) The numbering of entries has been reset to 1.
 

 

That sounds really strange. The only thing I can think of is that the demo entry conflicted with your other entries and two of them have the same entry ID. The entry ID is a unique key which identifies each entry. If you look into the raw logbook file 011108a.log with a text editor, you will see them as

$@Mid@$: 1
Date: Thu Nov 08 18:37:57 2001
Author: Stefan Ritt
Type: Routine
Category: General
Subject: Welcome
Attachment:
Encoding: ELCode
========================================
[B]Congratulations for installing ELOG sucessfully!
[/B]

This is a demo entry to ensure the elogd server is working correctly.
Click [I]"New"[/I] to add new pages and [I]"Delete"[/I] to delete this page.

so in this case the ID is 1. When you rsync'ed your entries into the demo logbook directory, you probably got two entries with the ID 1, which screws up elogd. Try to delete the file 011108a.log before you do the rsync. If you start elogd interactively with the "-v" flag, you will see some debugging output which can you help identify some problems:

[ritt@pc5082 ~/elog]$ ./elogd -v
elogd 2.7.0 built Dec 13 2007, 08:05:12 revision 1977
Config file  : /afs/psi.ch/user/r/ritt/elog/elogd.cfg
Resource dir : /afs/psi.ch/user/r/ritt/elog
Logbook dir  : /afs/psi.ch/user/r/ritt/elog/logbooks/
Indexing logbook "demo" in "logbooks/demo/" ...

Config [demo],                           MD5=F2E39262960C779517FEE576C17B1ED0

Entries:
  ID   1, 011108a.log, ofs     0, thead, MD5=81D89C3C94C6626BB7FF191026040E83
After sort:
  ID   1, 011108a.log, ofs     0
ok
Server listening on port 8080 ...

 

 

ELOG V3.1.5-3fb85fa6