> When you do a find in elog, records per page (some crazy large number - for 
> your forum logbook, display 57 entries seem to cause the problem, then 
> select last year (1 years worth of logs),(don't select printable)
> 
> the results appear way off the screen (the message body looks fine, but the 
> title, etc extend way off the screen).
> 
> Printable doesn't have this problem.

I could not reproduce this problem. Can you send me the exact URL (the 
address with all the parameters from your browser's address bar like 
http://midas.psi.ch/elogdemo/Forum/?npp=57...) and tell me exactly under 
which browser this happens?

Hi,
We prepared a customized theme to use with ELOG. It's called for example 
my_theme and is situated in the THEMES directory (together with the DEFAULT 
theme).

I defined the my_theme the global theme for ELOG:

[global]
Theme = my_theme

And it works fine for all the logbook in ELOG. However. The login screen 
and the main menu screen (the one with list of logbooks and # of entries) 
still takes the DEFAULT theme. 

If I change the my_theme name to default then everything works correctly 
(logon + main menu + all logbooks have the desired look).

Is the DEFAULT theme somehow hardcoded for the login screen and the main 
menu ?

Thanx for your answer

Tomas Rudolf

> Is the DEFAULT theme somehow hardcoded for the login screen and the main 
> menu ?

Yes, this was in and certainly is not correct. So I fixed it, the new code 
can be obtained vom CVS (see elog:233).

I hope this is not something I did. 

I'm using elog 2.3.1 on redhat 7.1 and using stunnel to redirect from port
443 to 8080. When I try to add a new record (click submit) https:// in the
browser gets changed to http://. I ve tried three browsers all with the same
result. If I go into the address field and change it to https:// after
getting a 404 error it works. The record gets posted.

> I hope this is not something I did. 
> 
> I'm using elog 2.3.1 on redhat 7.1 and using stunnel to redirect from port
> 443 to 8080. When I try to add a new record (click submit) https:// in the
> browser gets changed to http://. I ve tried three browsers all with the same
> result. If I go into the address field and change it to https:// after
> getting a 404 error it works. The record gets posted.

Just an update: It does the same thing when I click the back button

> > I'm using elog 2.3.1 on redhat 7.1 and using stunnel to redirect from port
> > 443 to 8080. When I try to add a new record (click submit) https:// in the
> > browser gets changed to http://. I ve tried three browsers all with the 
same
> > result. If I go into the address field and change it to https:// after
> > getting a 404 error it works. The record gets posted.

This is due to a change we had to do in the redirection of the pages. If you 
submit a page, the result is a redirection using the HTTP 
statement "Location: ..." inside the header. While this was a relative link 
in the previous versions, we changed this into an absolute link, which then 
agrees with the standard. But since elgod does not know if it runs 
under "http:" or "https:", you have now to add the line

URL = https://your.server:port

into elogd.cfg. I will add this note into the documentation.

- Stefan

Operator error. Figures!

Elog has worked fine for a log time then I upgraded and added stunnel at the
same time. A case of not seeing the forest for the trees.

Thanks for the help.


> > > I'm using elog 2.3.1 on redhat 7.1 and using stunnel to redirect from port
> > > 443 to 8080. When I try to add a new record (click submit) https:// in the
> > > browser gets changed to http://. I ve tried three browsers all with the 
> same
> > > result. If I go into the address field and change it to https:// after
> > > getting a 404 error it works. The record gets posted.
> 
> This is due to a change we had to do in the redirection of the pages. If you 
> submit a page, the result is a redirection using the HTTP 
> statement "Location: ..." inside the header. While this was a relative link 
> in the previous versions, we changed this into an absolute link, which then 
> agrees with the standard. But since elgod does not know if it runs 
> under "http:" or "https:", you have now to add the line
> 
> URL = https://your.server:port
> 
> into elogd.cfg. I will add this note into the documentation.
> 
> - Stefan

Ive just installed the RPM of Elog 2.3.2 and ive found a bug relating to 
port bindings, basically im running elog bound to port 81 and when i 
install the new RPM it refuses to bind to this port, i tried port 8080 and 
that worked fine

Any ideas ?