Re: elog hanged when uploading photo failed, posted by Xuan Wu on Wed Mar 6 05:10:28 2019
|
That make sense. Is there a way to recovery when hung except restart elogd? On the other hand, whether could prompt for reloading attachment
when interpreter detect error but not hang?
Wu Xuan |
How to edit Elog landing pages., posted by John on Thu Mar 14 06:38:12 2019
|
Hi and thanx for such a wonderful program! I was wondering how I might edit, change or add to the landing pages. In other words the first pages that
show up (or any for that matter) when you login to a book. I can view the code ok in my browser using that function, but when I search for the actual page
and it's locale, I cannot find it. Is it created on the fly by the server? If so, how can I change them.. as I want to add for instance javascripts |
|
Re: How to edit Elog landing pages., posted by John on Sun Mar 17 00:40:42 2019
|
Well I answered part of my own question already.. I can have a start page different from what is default, and I can edit the orginal one by simply copying
it and modifiying it to my hearts desire. I still have isues after making menu selections from that page tho, when the program (server) takes
me to a site called for example: ../forum/index.html?cmd=Config. I cannot find out how to prevent or modify this behaviour. I am supposing tho, that |
|
Reverse proxy setting of Elog for Apache httpd 2.4 so that changing password windows works ?, posted by Takashi Ichihara on Tue Mar 19 06:13:03 2019
|
In CentOS 7.6 + Apache httpd-2.4.6 + ELOG V3.1.4 environment with Reverse Proxy setting of
/etc/httpd/conf/httpd.conf
: |
|
HTML editor not working after updating to V3.1.4, posted by Ross Gibson on Tue Mar 19 23:24:48 2019
|
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 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).
|
|
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.
|
elog.css and lock.png fail to load with top groups, posted by Ben Loer on Thu Mar 21 16:14:00 2019 
|
As the title says, we have our elog running behind an Apache proxy that is also providing authentication. We also have top groups enabled. The
first time a user views a top group page with a fresh browser cache, the index is delivered, but requests for elog.css and lock.png are returned with http
302 with location set to the elog root. (I.e., if the server is proxied under server.example.com/logs, the first request for server.example.com/logs/TopGroup1/elog.css |