HTML editor not working after updating to V3.1.4, posted by Ross Gibson on Tue Mar 19 23:24:48 2019
|
Since updating to v3.1.4 the HTML editor has stopped working. If I switch to HTML encoding, the editor appears with a blank field, cannot select or type
in field and none of the buttons work.
I have tried reverting to earlier versions, but the issue persists. Any suggestions to rectify? |
Re: HTML editor not working after updating to V3.1.4, posted by Stefan Ritt on Wed Mar 20 01:12:36 2019
|
Have you cleared your browser cache? There might be some old JavaScript stored there. If that does not help, remove elog and reinstall it to make sure to
have the correct libraries on the server (first back up you logbooks, then restore them afterwards).
|
|
Re: HTML editor not working after updating to V3.1.4, posted by Ross Gibson on Wed Mar 20 06:50:57 2019
|
Thanks Stefan. Tried these without success. I tried opening in another browser and it works fine in Firefox or Internet Explorer - the problem only appears
in Microsoft Edge. Perhaps its an issue with a Microsoft update (corporate rollout) to Edge and just a coincidence that I noticed it after updating Elog.
|
Very long URLs in message list corrupt layout, posted by Ederag on Sun Mar 10 01:07:53 2019
|
First, thank you so much for elog;
after using it for about 3 years, it has proven really handy and reliable.
When there is a very long URL in a message in "plain" encoding, |
|
Chain certificate, posted by Michal Falowski on Mon Mar 4 18:55:09 2019
|
I tried to run elog with SSL so I created key and crt files. In crt file I added client certificate and intermediate certifacte. Unfortunately, when
I try to run openssl s_client -showcerts -connect myexample.com:443 I got only the first certificate from the chain. Anyone has idea
why this happens? |
|
Mirror synchronization and file servers, posted by Frank Baptista on Fri Mar 1 19:18:53 2019
|
We have a number of temperature chambers – each has its own laptop running a local ELOG server, with unique logbook for each. Using the mirror
feature, these individual logbooks periodically synchronize to a single remote desktop server, which has a copy of each of the logbooks. All of that
works great, as long as each of the ELOG servers are storing the logbook(s) to their respective local hard drive. |
|
Re: Mirror synchronization and file servers, posted by Stefan Ritt on Mon Mar 4 13:35:13 2019
|
Sounds really strange to me. The remote server does not "know" that "S:\" is a network drive, so the syncing process should work
exactly as before. The only idea I have is that the access to the network files take pretty long, and you run into a timeout during syncing. We had this
in the past (for AFS netwhor shares, not Windows shares), where sometimes we have a blocking behaviour where the file access lasted 10-20 seconds, and |
New feature request for Options list, posted by Alan Grant on Wed Feb 20 22:24:05 2019
|
Is it possible to include an option in the next release to have the Options list reference a text file of attributes rather than explicity listing the
attributes in the Config file directly?
This would make it much easier to maintain a particular list that is referenced in several log books. |
|
Re: New feature request for Options list, posted by Stefan Ritt on Wed Feb 20 22:45:39 2019
|
I can put it on the wish list.
Alan
Grant wrote:
Is it possible to include an option in the next release to have the |
|
Re: New feature request for Options list, posted by Andreas Luedeke on Thu Feb 28 14:56:50 2019
|
Just my two cent - I would have many very good applications for that feature:
Keep option lists identical over different logbooks.
Keep option lists identical over different applications.
Create
option lists from a database - that allows to use the options in many applications and in the database; e.g. a list of systems with a failure database, |
|
Re: New feature request for Options list, posted by David Pilgram on Thu Feb 28 16:03:36 2019
|
May I slip my vote in for this, especially if it would allow more than 100 attributes (the default, and I do know how to increase it).
I even considered cutting that into two groups,. the first being words like "New", "Re-" and the second being actions.
Clunkey and binned. |
Migration from 3.1.2 version to 3.1.4, posted by Vladimir Travalja on Tue Feb 26 14:26:13 2019
|
Hi,
sorry for bugging you with this, but I could not find any information for making migration of elog system from one server to another. |
|
Re: Migration from 3.1.2 version to 3.1.4, posted by Stefan Ritt on Tue Feb 26 14:31:00 2019
|
To move an elog instance, just stop the old server, move the configuration file elogd.cfg and the logbook directory to the new server, and start the
new server. If the URL of the server changes, you have to adjust it in elogd.cfg.
Stefan |
elogd hangs on self referencing log entry, posted by Kester Habermann on Mon Feb 25 17:03:50 2019 
|
Hello,
Somehow when replying to a log entry, a log entry was created that was referring to itself. How this happened, I have no idea. The effect was
that each time this enty was loaded, the elogd started to hang, going to 100% load and not responding to any http requests anymore. This problem can be |
|
Unwanted double entries eg. double clicking submit button, posted by Finn Junker on Wed Feb 13 09:29:36 2019
|
I'm having a minor issue that were getting double entries due to the user is using the "submit" button more than once.
I seems like when there is a lag either on the machine or on the network it is possible to tap the "submit" button more than once resulting
i a double or triple entry containing the same text and a almost identical timestamp. |
|
Re: Unwanted double entries eg. double clicking submit button, posted by David Pilgram on Wed Feb 13 10:58:37 2019
|
I too have this as an occasional issue, although in my case due to a dodgy pointer. I too manually delete the entries.
Interestingly, it gives double entries - and thus the start of a branch - even in logbooks were branches are not allowed.
Finn |
|
Re: Unwanted double entries eg. double clicking submit button, posted by Stefan Ritt on Wed Feb 20 15:14:32 2019
|
I just committed some code which disables the "Submit" button after the first click and replaces the text with "Please wait...".
So double submits should not be possible any more.
David |
|
Re: Unwanted double entries eg. double clicking submit button, posted by Alan Grant on Wed Feb 20 21:56:32 2019
|
I'm also happy to see this change implemented as we've had to deal with the same issue at times as well. Will this change
be incorporated into the latest version (314-2, aka elog-latest.exe), or will there be a new version release (that is not in Changelog yet)? If
so, can you give any ETA on this new code availability? |
|
Re: Unwanted double entries eg. double clicking submit button, posted by Stefan Ritt on Wed Feb 20 22:41:23 2019
|
"I committed" means that the change is sent to the GIT repository. People who compile from the source code can pull and compile immediately.
Windows users have to wait until I do the next release. I'm developing on a Mac and have to boot a special (old) Windows machine to compile the .exe
which each time takes me about one hour including documenation updates, changelog updates, upload of zip files etc. Since my main job is heading a research |
|
Re: Unwanted double entries eg. double clicking submit button, posted by Finn Junker on Thu Feb 21 08:51:21 2019
|
Thank your very much for your work on this - as i mentioned this is a minor issue.
Kind Regards Finn
|