Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon1.gif   WYSIWYG editor for Elog not working in Debian Jessie, posted by Nicola on Tue Nov 3 18:22:33 2015 
    icon2.gif   Re: WYSIWYG editor for Elog not working in Debian Jessie, posted by Andreas Luedeke on Wed Nov 4 14:40:39 2015 
       icon2.gif   Re: WYSIWYG editor for Elog not working in Debian Jessie, posted by Nicola on Fri Nov 6 15:52:30 2015 elog-debian8.jpeg
          icon2.gif   Re: WYSIWYG editor for Elog not working in Debian Jessie, posted by Stefan Ritt on Fri Nov 6 16:06:34 2015 
          icon2.gif   Re: WYSIWYG editor for Elog not working in Debian Jessie, posted by Andreas Luedeke on Mon Nov 9 10:33:46 2015 
             icon2.gif   Re: WYSIWYG editor for Elog not working in Debian Jessie, posted by Nicola on Mon Nov 9 12:15:16 2015 
Message ID: 68177     Entry time: Tue Nov 3 18:22:33 2015     Reply to this: 68178
Icon: Entry  Author: Nicola  Author Email: nicolamori@aol.com 
Category: Info  OS: Linux  ELOG Version: 2.9.2 
Subject: WYSIWYG editor for Elog not working in Debian Jessie 

I suspect that this might be a Debian packaging issue; however no one replied to my help request on the Debian forums so I try posting the question also here. I insatlled Elog on my Debian Jessie machine, I can open it with a browser but when entering a new post just a simple plain text editing box is shown instead of the WYSIWYG editor, and no drag and drop area for attachments is shown. When I start the elog service with "systemctl start elog" I get this suspect message in the journal: "FCKedit NOT detected". Indeed, I see that the elog installation creates a symlink which I guess is supposed to point to the fckeditor installation, which nevertheless is missing:

root@static-3-080:/usr/share/elog/scripts# ll fckeditor
lrwxrwxrwx 1 root root 15 Oct 25  2014 fckeditor -> ../../fckeditor
root@static-3-080:/usr/share/elog/scripts# ll ../../fckeditor
ls: cannot access ../../fckeditor: No such file or directory

Is this a Deban misconfiguration or a bug in Elog? thanks

ELOG V3.1.5-3fb85fa6