choosing the default font ? , posted by Pavel Murat on Wed Nov 13 18:12:34 2024
|
Dear All,
is there a way to choose the default "style" for the HTML encoding ? - I'd like to set it to "Typewriter" but couldn't find
the corresponding option in the available docs/ sample config files... |
Re: choosing the default font ? , posted by Stefan Ritt on Fri Nov 15 09:55:11 2024
|
Check elog/themes/default/elog.css and look for font-family.
If you just want the elog entries in monospaced font, you can swith to "plain" encoding at the bottom of the entry form. You can also
make this a default (check the docu). |
Equation Editor does not work, posted by Dominic on Sun Sep 1 04:33:13 2024
|
Hi!
I am not sure if this is a know issue: it seems that the equation editor does not work anymore. Is there any fix or alternative method to type
latex formula in the log? |
|
Re: Equation Editor does not work, posted by Nick Sauerwein on Wed Sep 25 16:00:06 2024
|
We have observed the same issue. Did the CodeCogs api change?
Thanks for the help.
Dominic |
|
Re: Equation Editor does not work, posted by Dominic on Tue Nov 5 15:51:26 2024
|
is there any update on this bug? Has anyone else observed the same problem?
Dominic
wrote:
Hi! |
|
Crash on attachment upload, posted by jaro mrazek on Thu Sep 12 10:42:08 2024
|
I am on ubuntu 24.04.1, I needed to git clone, make and make install,
HEAD is 3fb85fa6 - (HEAD -> master, origin/master, origin/HEAD) Fixed compiler warning (3 weeks ago)
It crashes on every attachment: thank you. Jaro |
|
Re: Crash on attachment upload, posted by Dominic on Tue Nov 5 15:44:57 2024
|
Does this issue occur only on Ubuntu systems? as I've experienced the same on my Raspberry Pi 5 running Ubuntu too ...
jaro
mrazek wrote:
I am on ubuntu 24.04.1, I needed to git clone, make and make install, |
|
Looking for version update advice, posted by Patrick Upson on Fri Sep 13 12:02:54 2024
|
I've inherited a position that includes deploying elog for an at-sea mission. Once at sea there's no gauntee of internet connection so I have
to be sure things are going to work before hand. The machines I currently have (we have several backup machines) are running elog version 2.9.2 and
I'm looking for a change log, or feature list to determine if it's safe to update the at-sea laptops to the latest version of elog. |
|
Re: Looking for version update advice, posted by Stefan Ritt on Wed Sep 25 13:17:06 2024
|
If 3.1.4 runs safely on your laptop, there should be no problem to update the 2.9.2 one. But first do it on a copy of your logbooks from the at-sea.
The get converted automatically into a newer format but that should be transparent.
On the other hand you don't really need a new system if your old installation works fine and you don't need any of hte new features. |
|
Re: Looking for version update advice, posted by Patrick Upson on Wed Sep 25 13:26:07 2024
|
Thanks. I did eveuntaully find the change log and made the decision to upgrade the at-sea machines. So far the configuration file we update for each
mission still works. I have a copy of the 2.9.2 installer that if something catostrophic happens I can remove the new version and take it back, but I don't
think it'll be a problem. We archive logbooks at the end of a mission, but each mission basically starts from a fresh install like state anyway. |
|
Re: Looking for version update advice, posted by David Pilgram on Wed Sep 25 14:21:33 2024
|
I use linux elog, and if you upgrade to v3.x.x, it's difficult to go back to v2.9.x. This is because the log files get grouped in year sub
directories at v3.x.x.
In 2.9.x, the logfiles are store as (made up example) /home/logfiles/yymmdda.log |
|
Re: Looking for version update advice, posted by Patrick Upson on Wed Sep 25 15:02:16 2024
|
I ran a test (using Windows) and you're correct about the subfolder and file naming. I don't think that'll be an issue, but it's good
to be aware of. If we end up having to revert to 2.9.2 for whatever reason, I think it sould still work fine if what logs we have are just copied up a
directory (i.e /home/logfiles/2023/23mmdda.log ==> /home/logfiles/23mmdda.log) |
|
elog sprintf() buffer overflows on ubuntu-22, posted by Konstantin Olchanski on Wed May 15 01:07:12 2024
|
I get the following compiler warnings about sprintf() buffer overflows. I suggest sprintf() should be replaced by std::string msprintf() from
midas. K.O.
|
|
Re: elog sprintf() buffer overflows on ubuntu-22, posted by Stefan Ritt on Wed Sep 25 13:19:29 2024
|
> I get the following compiler warnings about sprintf() buffer overflows. I suggest sprintf() should be replaced by std::string msprintf() from
> midas. K.O.
|
Catgegory filtering, posted by Gabriel Lopez on Tue Sep 24 19:38:23 2024
|
Currently have multiple logbooks hosted with elogd. One book is having an issue with Categories. The user regulary uses the category filtering to see
one subject for the whole month. This past week it hasn't been working properly. When choosing a drop down category to filter there are not logs found.
I've notice the fields under the categories change randomly. Sometimes it would add a % sign where there should be --. Some other fields go from displaying |
|
Is the Windows Binary/Installer now compiled for Windows 11?, posted by Frank Baptista on Fri Sep 20 16:24:37 2024
|
Hi all,
Quick question -- I was wondering if the current Windows Binary/Installer is now compiled for compatibility for Windows 11?
I did look through the Forum, but the the answer wasn't really clear. |
|
Please help with config, posted by Daniel Sajdyk on Mon Sep 2 12:54:12 2024
|
Hello,
I'm trying to create config file for simple incident logbook. It should has 3 attributes:
source (source of incident) with options:
email
jira_id
ezd_id
Tactics |