I attempted instead to build from the tar ball, and, except for a "fatal" git error, make built elogd, elog, and elconv.  I put the first in /usr/local/sbin, and the latter two in /usr/local/bin, and then restarted elogd, but this didn't work:

Service Temporarily Unavailable

The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

So, I backed these out and restored the previous executables, and access to the elog was restored, and the elogd.cfg accessed is the original one, but all logbooks are empty and requiring authentication.  The logbook directories still contain all the old entries, so I'm not sure what has happened.

Thanks for your advice.

Phil

OK.  I found the source of the logbook problem in an exchange from May 2015, so no need to answer this one.

But I would like to be able to upgrade to 3.x from 2.9, so any help with this will be much appreciated.

Phil

I did the following on CentOS 6.7 (Should work for Fedora and RHEL as well):

This should install all the required dependencies.

Hello,

Is it possible to remove the "active" checkbox a user sees when they click on "config"?  Alternatively, is it possible to have a new user arrive directly at the logbook they chose, rather than starting out at the config screen?

We are running elog-3.1.1 on SL6 with webserver authentication.  For the most part this works great, but somehow a few users become inactive after they login for the first time.  They claim they didn't un-check "active," but I can't think of any other way this would happen.

Many thanks,
Devin

I seem to be having some trouble with Find when using conditional attributes.

when I change the primary attribute in the find field, the corrispnding secondary attribute dosn't refresh properly with the list of values.

I am able to use the conditional options as expected when creating a new logbook.

I am using version ELOG V3.1.1-0767eb0 running on debian wheezey (compiled from sid sources)

This may be due to how I have my config file setup

Example:

Attributes = A, B
Options B = Please Select A
Options A = One{1}, Two{2}
{1} Options B = 1, 2,
{2} Options B = 3, 4,
 

Uppon closer inspection, removing the option to preset the secondary attribute as a Option list dosn't do anything for the find page.

This:

Attributes = A, B
Options A = One{1}, Two{2}
{1} Options B = 1, 2
{2} Options B = 3, 4

Still fails to set attribute B to a option list on  the find page. 

Hello,

Has anyone implemented an email gateway for ELOG, allowing users to submit entries by sending an email?  Granted this should be possible using the elog client binary, but I thought I'd see if I've overlooked any examples or docs first.

Thanks!
Devin