Re: HTML editor not working after updating to V3.1.4, posted by Stefan Ritt on Wed Mar 20 01:12:36 2019
|
Have you cleared your browser cache? There might be some old JavaScript stored there. If that does not help, remove elog and reinstall it to make sure to have the correct libraries on the server (first back up you logbooks, then restore them afterwards).
Stefan
| Ross Gibson wrote: | Since updating to v3.1.4 the HTML editor has stopped working. If I switch to HTML encoding, the editor appears with a blank field, cannot select or type in field and none of the buttons work.
I have tried reverting to earlier versions, but the issue persists. Any suggestions to rectify? |
|
|
Re: HTML editor not working after updating to V3.1.4, posted by Ross Gibson on Wed Mar 20 06:50:57 2019
|
Thanks Stefan. Tried these without success. I tried opening in another browser and it works fine in Firefox or Internet Explorer - the problem only appears in Microsoft Edge. Perhaps its an issue with a Microsoft update (corporate rollout) to Edge and just a coincidence that I noticed it after updating Elog.
| Stefan Ritt wrote: | Have you cleared your browser cache? There might be some old JavaScript stored there. If that does not help, remove elog and reinstall it to make sure to have the correct libraries on the server (first back up you logbooks, then restore them afterwards).
Stefan
| Ross Gibson wrote: | Since updating to v3.1.4 the HTML editor has stopped working. If I switch to HTML encoding, the editor appears with a blank field, cannot select or type in field and none of the buttons work.
I have tried reverting to earlier versions, but the issue persists. Any suggestions to rectify? |
|
|
|
Re: HTML editor, posted by Andreas Luedeke on Mon Sep 17 09:16:38 2012
|
| Josef Uher wrote: |
|
[...] maybe I missed something in the configuration, but how do I get this nice editor for HTML like the one available on this forum?[...]
|
The fckeditor is already installed with the elog package. All you need to do is to enable HTML in ELOG and Javascript in your browser.
The ELOG command "Allowed encoding = 7" gives you the same encoding choices as in this forum. |
|
Re: HTML editor, posted by Josef Uher on Mon Sep 17 15:14:46 2012
|
| Andreas Luedeke wrote: |
|
| Josef Uher wrote: |
|
[...] maybe I missed something in the configuration, but how do I get this nice editor for HTML like the one available on this forum?[...]
|
The fckeditor is already installed with the elog package. All you need to do is to enable HTML in ELOG and Javascript in your browser.
The ELOG command "Allowed encoding = 7" gives you the same encoding choices as in this forum.
|
Hi Andreas, thank you for your reply. I have already found out that the problem on Mac was that I moved the cfg file to some other folder which did not contain the resources and scripts. I used the "-s" switch and now it works nicely. However, now I try to do the same thing on Windows and even the "-s" switch does not help (the default encodings etc. are set in the cfg file). I compiled the elog on Mac, but I used the installation package on Windows. |
|
Re: HTML Editor not working after enabling SSL, posted by Daniel Sajdyk on Thu Mar 9 09:44:32 2023
|
Hello,
I created new certificate, but it doesn't help with resolving this problem.
Does someone have and idea how to resolve it?
Best Regards
Daniel
| Daniel Sajdyk wrote: |
|
Hello,
After enabling SSL=1 in /usr/loca/elog/elogd.cfg file, HTML editor loading very long.
After changing SSL to 0, everything work flawlessly.
Does anyone know what can cause this behaviour?
Best Regards
Daniel
|
|
Re: HTML Editor not working after enabling SSL, posted by Daniel Sajdyk on Tue Mar 21 14:25:25 2023 
|
Hello,
I found that someone else had the same issue - https://dev.ckeditor.com/ticket/10874#no1
In Firefox I do not have problems, but in Chrome and Edge i have.
His solution was:
My problem is solved. The .htaccess file sents any request to the login page. Therefore CKEditor could not reach the CSS file. Thanks for helping!
Sinse I don't use apache webserver, I don't know what should I do.
It looks that also in my case problem is with file progressjs.min.css (please look at attached screenshot)
Anyone have solution for this?
Best Regards
Daniel
| Daniel Sajdyk wrote: |
|
Hello,
After enabling SSL=1 in /usr/loca/elog/elogd.cfg file, HTML editor loading very long.
After changing SSL to 0, everything work flawlessly.
Does anyone know what can cause this behaviour?
Best Regards
Daniel
|
|
|
Re: HTML Editor not working after enabling SSL, posted by Daniel Sajdyk on Tue Mar 21 14:25:25 2023
|
Hello,
I found that someon
| Daniel Sajdyk wrote: |
|
Hello,
After enabling SSL=1 in /usr/loca/elog/elogd.cfg file, HTML editor loading very long.
After changing SSL to 0, everything work flawlessly.
Does anyone know what can cause this behaviour?
Best Regards
Daniel
|
|
|
Re: HTML Editor not working after enabling SSL, posted by Daniel Sajdyk on Tue Mar 21 14:25:26 2023
|
Hello,
I found that someone else had the same issue - https://dev.ckeditor.com/ticket/10874#no1
But I don't know why
| Daniel Sajdyk wrote: |
|
Hello,
After enabling SSL=1 in /usr/loca/elog/elogd.cfg file, HTML editor loading very long.
After changing SSL to 0, everything work flawlessly.
Does anyone know what can cause this behaviour?
Best Regards
Daniel
|
|