Let me start by saying that I really like ELOG-- it's a nice tool.

I'm trying out version 2.3.3. The problem that I'm having is with
attachments disappearing when I do the following:

1. create a new entry that contains one or more attachments.
2. verify that the new entry from step 1 saved correctly.
3. reply to the entry from step 1.
4. return to the entry from step 1 only to find the attachments gone.

The attachement files are still in the logbook directory, it's just that
they are no longer attached to the entry.

FWIW, I've attached the elog.config that I'm using...

Thanks,

Greg

I have been playing with Elog on windows 7.  I want to set up an elog that can be accessed from our local network, and I discovered that can be done by running the server on windows and entering the host machine's computer-name:8080 in a browser on any machine on the network.

I had the server registered as a windows service, but oddly, when I re-booted the server didn't seem to be running (problem #1).

I then ran into some other problems (currently trivial) but I eventually got around to uninstalling and reinstalling Elog.  I deleted all the existing logbooks and data files when I uninstalled, and even deleted everything in the folder I had used as a backup to the Elog directory.  So, after reinstalling, I should be getting only the demo logbook and the original demo entry, right?

BUT I'm actually getting the three logbooks that I had created before I uninstalled (problem #2).  Even though the entire Elog directory was deleted when I uninstalled... including config file and logbook directory.  I can go into "Program Files" now and see that the config file present is the default/demo config file (from the most recent install)... yet when I launch elog in a browser, I am seeing those three logbooks from before, even though they should be gone from my hard drive.

Elog must be storing data somewhere else... where?

(p.s. I've also tried clearing my cache and deleting cookies in the browser)

If it's relevant, when I'm not on the local PC hosting the server, I am accessing it through a university network, and I've found that I can enter computer-name:8080 from ANY machine on the University's nertwork to access elog.

Hello,

I am trying to set up my elog to have read-only guest access and require registration/password for users to be able to post to the elog. I've tried following the instructions here: https://midas.psi.ch/elog/faq.html#6, i.e. putting the following lines under the [global] section of my elogd.cfg file:

Menu commands = List, New, Edit, Reply, Duplicate, Find, Config, Logout, Help
Guest menu commands = List, Find, Login, Help
 

When I do this, I do get guest acccess, however the menu items are

New |  Find |  Select |  Import |  Config |  Logout |  Last day |  Help 

rather than the List, Find, Login, Help I would expect. Also, if I click on Logout, it simply does nothing, which means there's now no way to log in as a registered user.

Any thoughts on what might be wrong?

Thanks,

Greg

Got it. Thanks!

I recently ported an elog over to a new server running Ubuntu 20.10. Everything is working okay, except sometimes I get a strange unformatted appearance when I go to the elog page (see attachment). The happening of this seems random. For example, yesterday, when I started the elogd daemon everything looked fine, but when I log in today I get the unformatted appearance. Also, yesterday when I was setting things up, sometimes certain logbooks would have the formatting issue, and I could make this go away with a kill...restart cycle of elogd.

I downloaded the source code from here: https://elog.psi.ch/elog/download.html, selecting the elog-latest.tar.gz file.

I have tried viewing the elog on 3 different browsers (firefox, IE, Edge), result is the same every time.

Any thoughts about what the problem is?

In trying to fix this, I have re-downloaded the source from github rather than the source at http://elog.psi.ch/elog/download/tar/elog-latest.tar.gz, which is apparently very different from what is on github. Now I am running ELOG V3.1.4-d828aa58

The problem still persists, however, although only for some of the logbooks.  Curiously, it *seems* to only show up if I run elogd with the -D flag. If I just run it in the terminal, I have not seen the formatting problem (so far).

In case it's helpful, I post my elodg.cfg file.