Simply copy over your elogd.cfg file and all files under "logbooks". If you only see former logbooks, you grabbed probably the wrong elogd.cfg file.

Hi there,

our host running ELOG crashed. I installed ELOG at another host with copying backup files / folders to new installation. New installation looks fine and seems to be working. But one big problem occurs I only can see some of former existing logbooks. Are there any suggestions how to build an new ELOG with old data?

Many thanks Mario

Hi there,

our host running ELOG crashed. I installed ELOG at another host with copying backup files / folders to new installation. New installation looks fine and seems to be working. But one big problem occurs I only can see some of former existing logbooks. Are there any suggestions how to build an new ELOG with old data?

Many thanks Mario

I just upgraded to 3.1.0 after many years using 2.9.2. Our eLogs are absolutely crucial for the operation of our accelerators, so first of all I'd like to say: thanks a lot for everything you've done! It's a rock-solid application that works really well.

The issue I'm having is a minor one. Some of our users are using Internet Explorer 11, which has a Compatibility Mode option that is enabled by default for intranet sites (of which our eLog is one). This mode emulates IE7, and this causes the CKEditor rich text box to fail to load. I can tell our users to disable the CM setting on their browsers, but it may be that a simple server-side fix is possible as well.

It would be nice if the eLog pages could have a <meta name="viewport" content="width=device-width, initial-scale=1.0"> tag, so that it displays nicely on smaller screens. I've been adding this myself in some Javascript code (see elogHelper.js on the above-linked website), but it doesn't appear on every page (the logbook selection page, for instance). I also made some modifications to the CSS so that the list display collapses down when the browser window is very narrow.

The new autosave functionality is really good. I hacked something together to do this for our log a while ago, but it's nice that it's inbuilt now.

Thanks again!

Ben

Hej Stefan,

thanks for the suggestion -- through a Apache proxy the upload does indeed work without problems.

Cheers,

Hanno

Hello.

When I use "Revisions" name for attribute I have correct entry like "DATE by XXX from SOME_IP" which is added to previous edition date. 

But when i rename Revisions attribute to polish language (like "Wersje"), the entry is preceded by 3c6435es and whole looks like "3c6435es DATE by XXX from SOME_IP" and it overwrite previous entry. 

Is "Revisions" attribute must be in english?

Regards Daniel. 

Edit:

I know what I was doing wrong. I use:

Subst on Edit Wersje = $Revisions<br>$date przez $long_name z $remote_host

but it should be: 

Subst on Edit Wersje = $Wersje<br>$date przez $long_name z $remote_host

Hej,

I just noted that when having an unknown (or presumably misspelled) user name in the "Admin user" line in the
config file, that the other users are no longer treated as admins and do not see the corresponding link to the
admin page e.g. on the list page. In my specific situation, I in fact have only one user registered (new
password file) but two users still on the admin list (old config file). The one user is only treated as admin
after removing the offending name from the list of admins.

I understand that this might be the intended behavior -- but I wonder if this could lead to a situation where
one locks oneself out, e.g. when adding a misspelled user name to the list.


Thanks and cheers,

Hanno

No.