Per default, all pages are created dynamically by elogd directly from its C code. So nothing to change easily except hacking the code. There is one exception which is the start page you found already. To change any other page, you have to modify the C code. There is one more (dirty) trick: You can sneak in JavaScript code on every page via the "bottom text" option. This code can then modify the DOM tree and changes pages, but you need to program this in JavaScript.

Stefan

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 because I am using my own original index.html (start page), that the program is not modifying it (on the fly), like it does with the oringal web pages?  I am also still currious if the program does indeed create/modify pages on the fly, and if it does, where does it store them on my hard drive (or is it only put in memory temporaly?). Thanx again :)

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 returns a 302 with location set to server.example.com/logs// ). 

Any subsequent visits return the files fine. The attached screenshot shows the network requests in chrome. 

Is this a proxy configuration issue, something we've set wrong in elog, ??

Dear users,

we started an elog serveur (using ssl) and open to the world which is working fine.

However I am trying to access it via the command line client, from a computer that uses a proxy to connect to internet.

The environnment variable are set :

declare -x ftp_proxy="ftp://myproxy:3128/"
declare -x http_proxy="http://myproxy:3128/"
declare -x https_proxy="https://myproxy:3128/"
declare -x socks_proxy="socks://myproxy:3128/"
 

but when I try to connect

elog  -h myelog -p 443 -l lognote -s 1 -u username passwd  -w last

I have the following message :

Cannot connect to host myelog, port 44

How should I proceed ?

Best regards

JG

:

In CentOS 7.6 + Apache httpd-2.4.6 + ELOG V3.1.4 environment with Reverse Proxy setting of

/etc/httpd/conf/httpd.conf
 :
ProxyRequests Off
RedirectMatch ^/elog$ /elog/
<Location /elog/>
ProxyPass                      http://mmm.riken.jp:3333/ 
ProxyPassReverse         http://mmm.riken.jp:3333/
ProxyPassReverseCookiePath   /      /elog/
</Location>
:
It almost works fine.  But Changing password has problem. 

When clicking the "Forget password?" link in login window and displaying "Entering your user name or email address"
and entering it, an email is sent to the user:

----
This is an automatically generated account recovery email for host mmmm.riken.jp.
Please click on following link to recover your account:

http://mmm.riken.jp/elog/?redir=%3Fcmd%3DChange+password%26oldpwd%3DIHCPHXNTMJGEYDKY&uname=test&upassword=IHCPHXNTMJGEYDKY

ELOG Version 3.1.4
---

Clicking the URL above in the Firefox Browser results invalid URL: 

http://mmm.riken.jp/?cmd=Change%20password&oldpwd=IHCPHXNTMJGEYDKY

These parameters does not pass to the elog by the Reverse Proxy setting above.

 While accessing the URL of (native elog port: 3333)

http://mmm.riken.jp:3333/?cmd=Change%20password&oldpwd=IHCPHXNTMJGEYDKY

displays the normal page for Changing password windows for the user.

Is there any suggestions for the Reverse Proxy setting in Apache httpd 2.4 
so that the changing password windows works fine ?

Thank you for any suggestions.

Dear Supporters,

I am evaluating the elog software as lobgook for high energy pgysics and I was just wondering the interface with SSO from the login point of view. Once euthenticated with SSO, can this authentication be also recognized by elog?

Thank you so much

Best Regards,

PAtricia