Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 768 of 808  Not logged in ELOG logo
    icon6.gif   Re: Announcement of RSS feeds, posted by Marc Neiger on Mon Nov 15 13:10:12 2004 ELOG_Forum.htm
Hi Stefan,

The parsing now seems OK, IE downloads the XML and the RSS reader of Avant 
Browser 
accepts the feed. 
I still have a problem however : below the header, only the first 3 items 
are displayed and it seems only partially.
I included the HTML result so you can "visualize" what's going on (this may 
also be on the avant browser side !).

Cheers,
Marc


> The problems came from the French accents and the German umlauts. I 
changed the XML
> charset, so this should be fine now. New version is under CVS.
icon6.gif   Including the text in the CSV export, posted by Gary Mercier on Mon Feb 28 21:35:57 2005 
Is there any way to include the text of a log message in the CSV export? 
Anyway to include a pointer to the attachment?
    icon6.gif   Re: Logbook locking issue, posted by Steve Jones on Wed Jun 1 21:00:01 2005 

Steve Jones wrote:
Stefan, not a problem. ITMT, any idea how I can manually clear this "lock"? Is it embedded in the logbook itself?


Stefan Ritt wrote:
Sorry about my unusual slow response, but I'm pretty busy these days. I hope I will be able to address this problem in a two weeks from now.


Steve Jones wrote:
Stefan, any ideas on this problem?


Quote:
Our eLog is set to create logbook entry locks and after 30minutes prevent one from re-editing an entry, thus forcing a REPLY to be created.

SCENARIO: When an *attempt* is made to edit a logbook after the 30minute timer, one gets the message that EDITING is prevented and to use the browser "Back" button.

PROBLEM: The display now shows that particular entry to be locked, even though the attempt to edit was blocked. It appears that the lock flag is set prior to the "Edit" attempt being blocked and thus the lock flag is never "unset".
icon6.gif   prevent CVS and XML exports , posted by Paul Paquette on Mon Jun 20 04:29:57 2005 
Hello Again,

I'm being asked to do the impossible to list the Assessing Dept Data but not letting people download the whole database. This way they can lookup the info the Town uses to assess their property. The Town’s Selectmen have stopped paying for the company who hosted the database and the software they used. Now I'm asked to do the same service in house with out funds and without resorces. Hence the question.

Thanks


Paul
    icon6.gif   Re: prevent CVS and XML exports , posted by Stefan Ritt on Fri Jun 24 20:45:41 2005 

Paul Paquette wrote:
I'm being asked to do the impossible to list the Assessing Dept Data but not letting people download the whole database. This way they can lookup the info the Town uses to assess their property. The Town’s Selectmen have stopped paying for the company who hosted the database and the software they used. Now I'm asked to do the same service in house with out funds and without resorces. Hence the question.
Paul


See elog:1202
icon6.gif   Problem selecting ports, posted by Chris Warner on Fri Jan 13 03:21:32 2006 
I had problems getting elog to run on port 8080 (or many others). I have it installed on Redhat Enterprise Linux rel 4. The only way I was able to get it working was using port 80. I would like to run it on a different port if possible but I'm not sure what is wrong.

Any Ideas
    icon6.gif   Re: In version 2.6 the themes do not work right on Windows., posted by Mark Coudriet on Thu Jan 19 20:50:29 2006 

Stefan Ritt wrote:

Quote:
The URL is fixed at whichever logbook that is selected (e.g. ELOG 2.5.9-4 is <link rel="stylesheet" type="text/css" href="default.css"> & ELOG 2.6.0-1 is <link rel="stylesheet" type="text/css" href="http://localhost:8080/demo/default.css">).


So what is your problem? Can't you access http://localhost:8080/demo/default.css ?

If so, you could use an
URL = http://{your host}:8080/

option in your config file, where you replace {your host} with your real host name.


No, because they would have to be in every logbook instead of coming out of the theme directory.
But I just updated to your new version 2.6.1 & everything is fine now. Thanks for your help! Big grin
    icon6.gif   [SOLVED] Re: MOptions problem ?, posted by Alex H on Tue Feb 28 12:08:42 2006 gotcha.gif
Yop,
I think I found the solution! I was in fact a conditions conflict!
See the attached picture for easiest comprehension.
My list box type's conditions (FWL1{1}, FWL2{2}, FWL4{3}, VPN1{4}, VPN2{5}, CLIVPN-PROC{6}) conflict with my Equipment's conditions. It seems that the condition ID must be unique across the whole elogd.cfg.
So I have replaced my "Options Type = FWL1{1}, FWL2{2}, FWL4{3}, VPN1{4}, VPN2{5}, CLIVPN-PROC{6}"
by : "Options Type = FWL1{101}, FWL2{102}, FWL4{103}, VPN1{104}, VPN2{105}, CLIVPN-PROC"
and it works well Smile!
ELOG V3.1.5-3fb85fa6