Hi there,
I posted a reply here: http://www.chronoengine.com/forums/posts/t97137/p335997.html But then realized it was marked as "solved" so maybe I better start a new thread.
I am trying to use ReCaptcha on a form on a site that uses HTTPS. SSL Server is set to YES in the Load ReCaptcha action, but I can still see this error in Chrome's code inspector:
The page at '(mydomain)/index.php?option=com_chronoforms5&chronoform=contactin' was loaded over HTTPS, but ran insecure content from 'http://www.google.com/recaptcha/api/challenge?k=6LepLPoSAAAAADNOG8YaqxC20z19eGEjawzplSsn': this content should also be loaded over HTTPS.
How do I fix this?
Thanks!
I posted a reply here: http://www.chronoengine.com/forums/posts/t97137/p335997.html But then realized it was marked as "solved" so maybe I better start a new thread.
I am trying to use ReCaptcha on a form on a site that uses HTTPS. SSL Server is set to YES in the Load ReCaptcha action, but I can still see this error in Chrome's code inspector:
The page at '(mydomain)/index.php?option=com_chronoforms5&chronoform=contactin' was loaded over HTTPS, but ran insecure content from 'http://www.google.com/recaptcha/api/challenge?k=6LepLPoSAAAAADNOG8YaqxC20z19eGEjawzplSsn': this content should also be loaded over HTTPS.
How do I fix this?
Thanks!
Hi megana,
I think that there is a little bug in the code :-(
Please will you test this edit. Find this line around line 34 of /administrator/components/com_chronoforms5/chronoforms/actions/load_recaptcha/load_recaptcha.php
Note: this isn’t a proper solution - but a workaround that should force the use of SSL for that URL.
Bob
I think that there is a little bug in the code :-(
Please will you test this edit. Find this line around line 34 of /administrator/components/com_chronoforms5/chronoforms/actions/load_recaptcha/load_recaptcha.php
$recaptcha_load = "<div id='recaptcha'>".$this->recaptcha_get_html($config->get('public_key'))."</div>";
and replace it with this line$recaptcha_load = "<div id='recaptcha'>".$this->recaptcha_get_html($config->get('public_key'), null, true)."</div>";
Note: this isn’t a proper solution - but a workaround that should force the use of SSL for that URL.
Bob
Yea, that fixed it! Thankya, sir!
Will that be changed in future versions or should I make note of it so I can change it again after any upgrades?
Will that be changed in future versions or should I make note of it so I can change it again after any upgrades?
Hi Megana,
Hopefully Max will fix it for the next release - but it won't do any harm to keep a note just in case.
Bob
Hopefully Max will fix it for the next release - but it won't do any harm to keep a note just in case.
Bob
Hi,
I will apply this fix before the new update!
Thanks Bob!🙂
Regards,
Max
I will apply this fix before the new update!
Thanks Bob!🙂
Regards,
Max
This topic is locked and no more replies can be posted.