| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68183
|
Mon Nov 9 10:33:46 2015 |
 | Andreas Luedeke | andreas.luedeke@psi.ch | Question | Linux | 2.9.2 | Re: WYSIWYG editor for Elog not working in Debian Jessie | Hi Nicola,
as Stefan pointed out: the debian package that you are using is from an outdated ELOG version and not supported anymore. I can't help you with that.
Is somebody out there that created a 3.1.x version debian package?
Cheers, Andreas
| Nicola wrote: |
|
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 (I had it in my old Debian 6 server) and the editor toolbar has an ugly "Windows 95" look; see the attached image. I can live with these problems but if the can be easily fixed then obviously I would do that, can you give me any hint? Thank you very much.
| Andreas Luedeke wrote: |
|
Hi Nicola,
this appears to be a particular problem of the specific (outdated) ELOG debian package.
But you could just download the FCKeditor directly and install it to the proposed location "/usr/share/fckeditor".
Or you download ELOG 3.1.1 and give it a try to install it with the makefile.
Cheers, Andreas
| Nicola wrote: |
|
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
|
|
|
|
|
68184
|
Mon Nov 9 12:15:16 2015 |
| Nicola | nicolamori@aol.com | Question | Linux | 2.9.2 | Re: WYSIWYG editor for Elog not working in Debian Jessie | 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.
Thanks again for the support.
| Andreas Luedeke wrote: |
|
Hi Nicola,
as Stefan pointed out: the debian package that you are using is from an outdated ELOG version and not supported anymore. I can't help you with that.
Is somebody out there that created a 3.1.x version debian package?
Cheers, Andreas
| Nicola wrote: |
|
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 (I had it in my old Debian 6 server) and the editor toolbar has an ugly "Windows 95" look; see the attached image. I can live with these problems but if the can be easily fixed then obviously I would do that, can you give me any hint? Thank you very much.
| Andreas Luedeke wrote: |
|
Hi Nicola,
this appears to be a particular problem of the specific (outdated) ELOG debian package.
But you could just download the FCKeditor directly and install it to the proposed location "/usr/share/fckeditor".
Or you download ELOG 3.1.1 and give it a try to install it with the makefile.
Cheers, Andreas
| Nicola wrote: |
|
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
|
|
|
|
|
|
Draft
|
Thu Mar 3 00:02:26 2016 |
| Mike Bodine | Mike.Bodine@alcatel-lucent.com | Question | Windows | 2.9.2 | Attribute Field Size Limited to 255 Characters | I currently have an Attribute defined in my .cfg file as "Format <Attribute> = 0, attribname, attribvalue, 120, 500". I've found if I exceed 255 characters elogd.exe fails. Is there a method that will allow me to exceed 255 characters? |
|
68274
|
Thu Mar 3 00:12:45 2016 |
 | Mike Bodine | Mike.Bodine@alcatel-lucent.com | Question | Windows | 2.9.2 | Attribute Field Size Limited to 255 Characters | I currently have an Attribute defined in my .cfg file as "Format <Attribute> = 0, attribname, attribvalue, 120, 500". I've found if I exceed 255 characters elogd.exe fails. Is there a method that will allow me to exceed 255 characters? |
|
68275
|
Thu Mar 3 14:51:55 2016 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | Windows | 2.9.2 | Re: Attribute Field Size Limited to 255 Characters | No. At least there is no simple method.
You would need to edit the source code and recompile elogd. But the number 256 is used for about 300 times in the source code, you'll have a hard time finding the right one to increase.
Cheers, Andreas
| Mike Bodine wrote: |
|
I currently have an Attribute defined in my .cfg file as "Format <Attribute> = 0, attribname, attribvalue, 120, 500". I've found if I exceed 255 characters elogd.exe fails. Is there a method that will allow me to exceed 255 characters?
|
|
|
Draft
|
Tue May 31 19:53:59 2016 |
| S. Caiazza | caiazza@kph.uni-mainz.de | Bug report | Linux | 2.9.2 | Unable to set a custom logbook dir on Debian 8 from the repository package | Dear all
I installed elog from the current stable repository on Debian 8 (jessie)
The installation went on smoothly, I modified the configuration files of the Apache server as described in the manual to use the elog in parallel with an existing webserver and then I tested. The demo logbook loads fine and I see that elog created a folder for the logbook in /var/lib/elog/logbooks, which is the directory specified by default in the /etc/init.d/elog file.
Then I modified the /etc/elog.conf file, added the following lines in the global section (custompath is a local path)
Resource dir = /<custompath>/elog/res
Logbook dir = /<custompath>/elog/logbooks
And I created a new logbook.
After restarting the elog service the second database is correctly created but both of them are still stored in /var/lib/elog/logbooks so it seems the global configurations in the config file are overwritten.
How can I specify the custom folder so that the new logbooks a |
|
68323
|
Tue May 31 20:03:53 2016 |
| S. Caiazza | caiazza@kph.uni-mainz.de | Bug report | Linux | 2.9.2 | Unable to set a custom logbook dir on Debian 8 from the repository package | Dear all
I installed elog from the current stable repository on Debian 8 (jessie)
The installation went on smoothly, I modified the configuration files of the Apache server as described in the manual to use the elog in parallel with an existing webserver and then I tested. The demo logbook loads fine and I see that elog created a folder for the logbook in /var/lib/elog/logbooks, which is the directory specified by default in the /etc/init.d/elog file.
Then I modified the /etc/elog.conf file, added the following lines in the global section (custompath is a local path)
Resource dir = /<custompath>/elog/res
Logbook dir = /<custompath>/elog/logbooks
And I created a new logbook.
After restarting the elog service the second database is correctly created but both of them are still stored in /var/lib/elog/logbooks so it seems the global configurations in the config file are overwritten.
How can I specify the custom folder so that the new logbooks are written there? |
|
68342
|
Mon Jun 27 16:06:55 2016 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.9.2 | Re: Unable to set a custom logbook dir on Debian 8 from the repository package | The debian version of elog is pretty old with quite a number of bugs fixed in meantime. Unfortunatlely the debig packase has not bee updated by the maintainers. So better download the current version from bitbucket and compile elogd yourself.
| S. Caiazza wrote: |
|
Dear all
I installed elog from the current stable repository on Debian 8 (jessie)
The installation went on smoothly, I modified the configuration files of the Apache server as described in the manual to use the elog in parallel with an existing webserver and then I tested. The demo logbook loads fine and I see that elog created a folder for the logbook in /var/lib/elog/logbooks, which is the directory specified by default in the /etc/init.d/elog file.
Then I modified the /etc/elog.conf file, added the following lines in the global section (custompath is a local path)
Resource dir = /<custompath>/elog/res
Logbook dir = /<custompath>/elog/logbooks
And I created a new logbook.
After restarting the elog service the second database is correctly created but both of them are still stored in /var/lib/elog/logbooks so it seems the global configurations in the config file are overwritten.
How can I specify the custom folder so that the new logbooks are written there?
|
|
|