Re: Attribute option "+x" not searcheable, posted by Andreas Luedeke on Tue Oct 31 16:56:24 2017
|
Hi Stefano,
I've tested it: it does not work.
Neither in edit nor in list view the HTML encoded characters show correctly.
|
Buttons missing in ckeditor, posted by Roland Beyer on Thu Oct 11 10:51:17 2018
|
Hello everybody,
we had to setup a new server for our elog some time ago because the old one crashed. We are now running version ELOG V3.1.1-0767eb0.
In the previous installation we had these nice buttons for file upload, time stamp and equation editor, which are also available here in the |
|
Re: Buttons missing in ckeditor, posted by Stefan Ritt on Fri Oct 12 10:17:20 2018
|
Have you selected "HTML" encoding (below the main message box). The HTML editor is not activated if you have "plain" text encoding.
Did you try the default elogd.cfg file? If you modified the config file and did a mistake there, the program can for example not properly find all directories.
Also makse sure you did a full install with "make install", not just update the executable. |
|
Re: Buttons missing in ckeditor, posted by Roland Beyer on Fri Oct 12 11:56:26 2018
|
Dear Stefan,
thanks for your hints. Meanwhile we already solved the problem. I think it was caused by the recovery from a backup version after the server
crash ... and the retirement of the person who did the previous installation. |
|
How to enforce line breaks in plain text entries?, posted by Andreas Luedeke on Wed Apr 27 14:07:52 2016
|
We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
entries made during the shift and files the printouts. If one entry in the shift was plain text without
appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the width
|
|
Re: How to enforce line breaks in plain text entries?, posted by Andreas Luedeke on Wed Apr 27 14:15:19 2016
|
> We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
> entries made during the shift and files the printouts. If one entry in the shift was plain text without
> appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the
|
|
Re: How to enforce line breaks in plain text entries?, posted by Andreas Luedeke on Wed Apr 27 14:36:42 2016
|
> > We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
> > entries made during the shift and files the printouts. If one entry in the shift was plain text without
> > appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the
|
|
Re: How to enforce line breaks in plain text entries?, posted by Stefan Ritt on Wed Apr 27 14:39:28 2016
|
> > We use ELOG for our accelerator operation logbooks. As part of the shift handover every shift prints out all
> > entries made during the shift and files the printouts. If one entry in the shift was plain text without
> > appropriate linebreaks (like this one), then this screws up the printout: the whole window is scaled to the
|