Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 525 of 808  Not logged in ELOG logo
icon5.gif   Upgrading to 2.9, posted by Maureen Kular on Mon May 2 22:39:24 2011 

I am in the process of upgrading from 2.6.0 to 2.9.0.  I am installing it on a windows 2008 r2 server which is 64 bit.  I am having a few issues and am just wondering if Windows 2008 R2 is support with version 2.9.0.  Is there anything I need to know about the installation other than just run the exe file?  So far I have run the exe file and installed the software, the service is running, however I cannot get into the application.  I do not have IIS installed, it does mention it in the installation documentation, is this a requirement?  Any hints or ideas at this point would be appreciated.  I am close I just need that last tweek.  Thanks

    icon2.gif   Re: Upgrading to 2.9, posted by Pelle on Tue May 3 08:22:18 2011 

Maureen Kular wrote:

I am in the process of upgrading from 2.6.0 to 2.9.0.  I am installing it on a windows 2008 r2 server which is 64 bit.  I am having a few issues and am just wondering if Windows 2008 R2 is support with version 2.9.0.  Is there anything I need to know about the installation other than just run the exe file?  So far I have run the exe file and installed the software, the service is running, however I cannot get into the application.  I do not have IIS installed, it does mention it in the installation documentation, is this a requirement?  Any hints or ideas at this point would be appreciated.  I am close I just need that last tweek.  Thanks

 Hi Maureen,

You write "Upgrading from 2.6.0" Is that version working on the same computer?
If so then its strange. Else try with one of the demo config files and see what happens, try different ports etc.

If the service is running it should work the rest too. I'm running it on a Win7 64 bit so 64 bit is not the problem....

Best

Per

 

icon1.gif   Calculations & Interfacing a DataBase with Elog., posted by John on Sat Jun 22 06:52:32 2019 

Hi, I am trying to calculate two or more Elog fields and then return the value to Elog. I am currently learning Perl to do this. I realize JS can do this.. but so can IBM Basic ;)  I am savy with other db techniques like sql. My question is before I get too far along with this project, is it safe to say the current storage of Elog data is 'Flat File' database? I also want to find out if it would be better to try and grab the data prior OR  after it gets into the Elog database. I see there are other forum messages related to sql interfacing and such, but nothing conclusive.  I will submit my personal progress here. Thanks again, John

    icon2.gif   Re: Calculations & Interfacing a DataBase with Elog., posted by Stefan Ritt on Sat Jun 22 10:07:08 2019 

Yes elog stores data in a flat file database. Go to your logbook directory and look for files YYMMDDa.log where you find all data. Some people do a post submit call to scripts, other integrate JS directly on each page (e.g. via "bottom text" option where you can load a whole JavaScript file), then pick the fields and do calculations directly in the edit window.

Stefan

John wrote:

Hi, I am trying to calculate two or more Elog fields and then return the value to Elog. I am currently learning Perl to do this. I realize JS can do this.. but so can IBM Basic ;)  I am savy with other db techniques like sql. My question is before I get too far along with this project, is it safe to say the current storage of Elog data is 'Flat File' database? I also want to find out if it would be better to try and grab the data prior OR  after it gets into the Elog database. I see there are other forum messages related to sql interfacing and such, but nothing conclusive.  I will submit my personal progress here. Thanks again, John

 

    icon2.gif   Re: Calculations & Interfacing a DataBase with Elog., posted by John on Sat Jun 22 10:21:39 2019 

Thanks Stefan soo much. As I've said, I will update this post(s) as I make any progress :)

John

Stefan Ritt wrote:

Yes elog stores data in a flat file database. Go to your logbook directory and look for files YYMMDDa.log where you find all data. Some people do a post submit call to scripts, other integrate JS directly on each page (e.g. via "bottom text" option where you can load a whole JavaScript file), then pick the fields and do calculations directly in the edit window.

Stefan

John wrote:

Hi, I am trying to calculate two or more Elog fields and then return the value to Elog. I am currently learning Perl to do this. I realize JS can do this.. but so can IBM Basic ;)  I am savy with other db techniques like sql. My question is before I get too far along with this project, is it safe to say the current storage of Elog data is 'Flat File' database? I also want to find out if it would be better to try and grab the data prior OR  after it gets into the Elog database. I see there are other forum messages related to sql interfacing and such, but nothing conclusive.  I will submit my personal progress here. Thanks again, John

 

 

icon5.gif   ELOG Stop working with kerberos configuration , posted by Moustafa Messed on Wed Oct 16 11:06:34 2019 

Dear All 

i have this problem since i tried  to install ELOG latest version while make Authetnetication Kerberos ELOG stop runing any idea or help please

 

 

    icon8.gif   [CLOSED] Re: show attributes directive does not work? -- It does, if you use show attributes edit, posted by Harry Martin on Sat Aug 16 14:31:49 2025 

Well, it DOES work.... but only if you use the "Show Attributes Edit" directive.  "Show Attributes" is only for the single entry pages, whereas "Show Attributes Edit" is for the "entry pages."

I should have read the docs more carefully, sorry.  But isn't this a bit inconsistent with the way other directives work?  Usually one uses "<Directive>" for new entries, "<Directive Edit>" for editing existing entries, and "<Directive Reply>" for replies.  So I am guessing that "Show Attributes Edit" will be used for new and edit?

Harry Martin wrote:

Follows a very simple logbook definition:

[simple]
Comment = test show attributes directive
Attributes = a, b, c
Show Attributes = a

(Assume that all attributes are used farther down.  This is for illustration only.)   

To see what I see when I run this tiny elogd.cfg, see attachment.

"Show attributes" does not seem to be working because all of the attributes are shown, not just those specified in the directive.  Or do I misunderstand/forget something?

 

 

    icon2.gif   [CLOSED] Re: 3-level conditional not working, posted by Harry Martin on Sat Aug 16 22:19:03 2025 

Closed.  This "problem" was due to the same lack of document eyesight as https://elog.psi.ch/elogs/Forum/69889.   Sorry for all the noise.  New eyeglasses are forthcoming...

Harry Martin wrote:

Tried a variant, this time for NEW entries (not EDIT), which I meant to do to begin with; sorry if that was confusing. 

[cond_test]
attributes = region, manufacturer, model

options region = american{us}, japanese{jp}, european{eu}
show attributes = region

{us} options manufacturer = ford, chrysler, gm
{jp} options manufacturer = toyota{toy}, nissan{nis}, mitsubishi{mit}
{eu} options manufacturer = audi, mercedes, bmw, volvo, fiat
{us} show attributes = region, manufacturer
{jp} show attributes = region, manufacturer
{eu} show attributes = region, manufacturer

{toy} options model = corolla, prius, miata
{nis} options model = sentra, murano
{mit} options model = starion, outlander, mirage
{toy,nis,mit} show attributes = region, manufacturer, model

 I'm not sure if my multi-character conditional names are allowed or not, but they do seem to work... somewhat.  Note that I even tried a couple different ways of specifying which attributes to show (single versus multiple OR conditionals).  The problem now is that all of the attributes are always shown, seeming to ignore the conditionals entirely.

Harry Martin wrote:

Not sure if this is a bug or not; if it is not, kindly reclassify the category.

Following is a small example of what I will dub a 3-level, conditional logbook:

[cond_test]
attributes = region, manufacturer, model

show attributes edit = region
options region = american{1}, japanese{2}, european{3}

{1} options manufacturer = ford, chrysler, gm
{2} options manufacturer = toyota{4}, nissan{5}, mitsubishi{6}
{3} options manufacturer = audi, mercedes, bmw, volvo, fiat
{1,2,3} show attributes edit = region, manufacturer
{4} options model = corolla, prius, miata
{5} options model = sentra, murano
{6} options model = starion, outlander, mirage
{4,5,6} show attributes edit = region, manufacturer, model

This example is hardly complete, but it is sufficient to demonstrate the issue I am running into.  This works until I select from the 2nd level (manufacturer); it won't display the dropdown for the model (I think my show attribute edit is supposed to display that).  Is there a restriction on how many levels of conditional I can have?  If there is, it would be disappointing because I am trying to do something similar to this example.

I hope there is something very simple I can do to correct this, or perhaps a completely different approach that accomplishes the same thing.  I'd like to stick with the multi-level selection process as I have done here.

I am running elog 3.1.5 on Devuan Chimaera (approx. Debian Bullseye, sans systemd) in a Virtualbox VM.

 

 

ELOG V3.1.5-3fb85fa6