Re: WYSIWYG editor for Elog not working in Debian Jessie, posted by Nicola on Fri Nov 6 15:45:33 2015
|
<p>Hi Andreas, I opted for installing FCKeditor rather than Elog, since the debian package, even if outdated and broken, has some goodies like a systemd
unit which is very handy for managing the daemon. I found FCKeditor 2.6.11 on SorceForge (after a long search, seems that CKeditor almost made his parent
disappear from the web), unpacked it in the proper folder and now when I edit a page I can use the WYSIWYG editor. There are just two minor issues: the |
Re: WYSIWYG editor for Elog not working in Debian Jessie, posted by Nicola on Fri Nov 6 15:52:30 2015 
|
Hi Andreas, I opted for the first solution since the Debian package, although outdated and broken, has some goodies like a systemd unit for managing
the daemon which is very handy. I downloaded FCKeditor 2.6.11 from SourceForge (after a long search, seems that CKeditor made its parent almost disappear
from the web), unpacked it in the proper folder and not the WYSIWYG editor works. I have just a couple of minor issues: there is no attachment drop area |
|
Re: WYSIWYG editor for Elog not working in Debian Jessie, posted by Nicola on Mon Nov 9 12:15:16 2015
|
Hi Andreas, understood. I found a 3.1.0 package for Debian unstable but it won't install on Jessie since it depends on a newer version of openssl,
and it seems to not have a systemd unit (not sure about that, though). I can live with my old version now that the WYSIWYG editor works, and in the meantime
I'll keep my eyes open for a brave soul who would eventually package a newer elog version for Jessie. |
How to not expose elog port when running under a reverse proxy, posted by Nicola on Mon Jan 22 08:22:33 2024
|
I am running elog under Apache as explained in the administrator's guide. Everything works fine, butmy IT service complains about the elog port being
publicly exposed, so I have to fix this. As far as I understand when running under a reverse proxy there's no need for the port to be publiuclyexposed,
but I cannot find how to configure the elog server to expose it only locally |
Problems with 2.3.2, posted by nick on Thu Mar 13 17:30:16 2003
|
Ive just installed the RPM of Elog 2.3.2 and ive found a bug relating to
port bindings, basically im running elog bound to port 81 and when i
install the new RPM it refuses to bind to this port, i tried port 8080 and
|
|
Re: Elog and SSL, posted by nick on Mon Mar 31 12:44:33 2003
|
Im not running anything on port 443, one thing I did notice is that when
stunnel is run and setup, I can run a netstat and nothing is bound to those
ports, if I do a ps -ef | grep stunnel nothing is running, yet it accepts the
|
|
Logbook Title bar , posted by nick on Wed Apr 2 16:36:18 2003
|
Is there a way to change the title entry for individual log books, and
forms ive completely rebranded our system but ut stil says ELOG ENTRIES on
the summary screen |
|
Re: Logbook Title bar , posted by nick on Thu Apr 3 09:40:45 2003
|
> > Is there a way to change the title entry for individual log books, and
> > forms ive completely rebranded our system but ut stil says ELOG ENTRIES
on
|