Still struggling with this issue, if anyone has managed to solve it let me know.   I've done the obvious and checked ownership/ permissions of the elog folders and they are exactly the same as etc/var/www, which is working in apache.

Hello

Want a hyperlink in one of the attributes like this : http://Someserver/someDir/perl.pl#subject

In this way I should be able to redirect to a certain part of the html that the perl script is generating. When I setup this manually it works. ( typing directly the html link into the attribute )

 
When I put the html link into elog config file it will never show up the correct format : everything after the '#' is translated into the digit 1. ( So you get  http://Someserver/someDir/perl.pl1 . ) 

I tried to escape with \# used quoting " and '. No luck.  Tried to use the a , No luck. 

I've tested with several versions of elog but it seems that it has never worked. 

Allow HTML = 1 dit not work for me.

Has it to do with the autoincrement  ? ( Subst Number = XYZ-##### ) I think so because of the 1 that is returned if i use a http link . When I use the same link  http://Someserver/someDir/perl.pl#subject a second time i'll get back :
http://Someserver/someDir/perl.pl2 . So it seems that the auto increment feature plays a role in this one. 

Can this be done in the attributes of elog.? Can I have a # in a hyperlink ?

Thanks for your time.

Today I released version 2.9.1 which fixes this problem.

- Stefan 

 Thank you Stefan!  I put up your new svn revision and we're back in business.  Seems to be working perfectly.

And thank you again for your efforts with regards to ELOG.  It is an incredibly handy tool.

-John

Yes, there is a new feature called record splitting which causes the browser to send the "G" of the "GET ..." in a dedicated TCP package. This started in FF10, Chrome 17, and it will come in others as well. It only affects direct SSL connections (SSL=1). I fixed the bug in SVN revision #2435. Please update also MXML to revision #73. Let's hope that surprises like that will not happen too often.

- Stefan
 

On our system, elog sends email to all people associated with an entry. Often, people will respond via email, not through elog. I'm in the process of setting up a handler for the inbound email. However, I'd like to have the outbound mail from eLog include a 'footer' to each message the details where to go to respond.

For example, the footer might read:

To respond to this message, please click the following link:
<http://www.example.com/elog/General/6153>

Any suggestions for how to implement that?
 

 I loathe the idea of 'bumping' up one's own posting, but here I go...

Has anyone seen this issue, or have any solution? We've got people who register 8 or more times, since they see the "Error" message with each registration.

John Doroshenko wrote:

Andreas Luedeke wrote: John Doroshenko wrote: Olaf Kasten wrote:  Hi there, I have a connection problem with an actual elog installation. Many Browsers like as Chrome, Firefox and IE don't  connect to the elog server with ssl = 1 in elogd.cfg.  I tested with Firefox 3.6 and IE 7 installations and there are no problems. I guess it's a bug. Does someone have a suggestion to solve that problem? Thx. Olaf  Hi! This just started happening here also.  Some users can't get on to a SSL=1 config'd elog using either IE or firefox 10 (win7 or linux) or chrome.  SAFARI works.  Occurs in 2.8.0 and a newly built (even after ssl yum updates) 2.9.0 version on SL5.5 system.  Seems to accept self signed cert then nothing.. (connection reset message).   Tried an stunnel from one port to port running elog with SSL=0.  Same behavior.  Doesn't work on some browsers.  Any clues? Thanks, -John Hi everyone, it appears that many people have this problem. I believe this is simply a problem of your firewall settings. There are two simple checks you can do to test if I'm right or wrong: Run your logbook on the standard port 443 and retry. If the special port has been opened on the firewall, it has been likely only opened for specific clients like firefox 3.6, IE 7, etc. If you use a different client (FF 10, IE 9) the port can be blocked. Or just run the browser that does not work on the ELOG server. If it works to access ELOG via localhost, then you know for sure that it is the firewall. I've actually tested it here at my institute: I've downloaded firefox 10 and could access ELOG on port 443 but couldn't access it on port 444, unless I've started FF10 on the ELOG host. To John, Olaf and Christian: If you need to be able to use a special port and a certain set of browsers then just contact your computing division or whoever maintains your firewalls.   I hope this settles the matter. Cheers Andreas   Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Detect language Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish ⇄ Afrikaans Albanian Arabic Armenian Azerbaijani Basque Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish Dutch English Estonian Filipino Finnish French Galician Georgian German Greek Haitian Creole Hebrew Hindi Hungarian Icelandic Indonesian Irish Italian Japanese Korean Latin Latvian Lithuanian Macedonian Malay Maltese Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Urdu Vietnamese Welsh Yiddish Detect language » English   PS: I've solved this with the help of google  : have a look at http://forums.mozillazine.org/viewtopic.php?p=2295421#2295421 about firewalls  Hi, Thanks for the reply.  The elog server is running SL5.5 (updates applied).  As you suggested, I ran firefox 3.6.26 on the elog server via https://localhost:port and it worked fine.   Downloaded firefox 10.0.1 and retried on elog server and get error again:  The connection was Reset; The connection to the server was reset while the page was loading. -John

 Hi,

One of our sys admins discovered that Firefox 10 appeared to send parts of the initial GET in two parts.  As if there was a flush() after the "G" and this caused elog problems.  By making the change in

the patch below, the read loop is re-entered again after the 2nd part of the GET comes in.   Firefox 10.0.1 then works with ELOG with SSL.   Stefan... perhaps you can take a look to see if there is a

better way to accomplish this? 

One side effect with it done this way is that if you start a connection (ie, telnet localhost port) and type a single character,  the elog will block further connections until the telnet is terminated.

Thank you,

-John Doroshenko