|
Scott Goodwin
|
February 27, 2014 at 8:29 pm
I have the WordPress HTTPS plugin installed, and have enabled HTTPS on my main registration page and sub pages(category pages) and well as the payment notification and auto return url. I’m using Authorize.net as the payment gateway. When registering for an event, the form action url is http:// rather than https:// and it throws the browser warning popup message. Any idea how to fix this? Here is an event as an example: https://scottgoodwinassociates.com/courses/?ee=77
|
|
Dean
|
February 28, 2014 at 1:57 am
Hi,
I registered for an event and it threw me back to the event list. Can you make sure that the four core EE pages are all published and available and contain the correct short. Also make sure they are set in the General Settings page.
|
|
Scott Goodwin
|
February 28, 2014 at 3:54 pm
All four pages are created and specified in settings. They each have the corresponding shortcodes as well. Also, all but the Cancel Return URL page has HTTPS enabled.
The only thing that has changed recently is that the WordPress was previously a single site and is now a multisite. Can this have something to do with the issue?
|
|
Josh
|
February 28, 2014 at 4:07 pm
Hi Scott,
It could. Converting a normal WP site to multisite can be tricky. With Event Espresso 3 you’ll need to make sure that Event Espresso is single site activated, not network activated.
That said, I’m not getting a pop up browser warning when I visit your registration page. If this is still happening for you, can you let us know which browser is displaying that warning so we can investigate further?
|
|
Scott Goodwin
|
February 28, 2014 at 4:19 pm
EE is indeed single site activated. The alert happens when entering the registration info as soon as the Submit button is pressed. Also, if you add to cart it will also appear once the Enter Attendee Info button is pressed. This happens for me in both Firefox and Safari.
|
|
Josh
|
February 28, 2014 at 4:32 pm
Hi Scott,
I ran a quick registration test that you can delete. I didn’t see any pop ups. It may help to temporarily deactivate all non-EE plugins except the SSL plugin to rule out any plugin conflicts.
Also, can you let us know what the pop up warning message says?
|
|
Scott Goodwin
|
February 28, 2014 at 5:02 pm
I had to leave Advanced Custom Fields enabled due to some page rendering, but I disabled the remaining plugins s2Members Framework & WP-Mail-SMTP, still getting the same result.
Safari: This is a non-secure form. This form will be sent in a way that is not secure. Are you sure you want to send it? [Cancel] [Send]
Firefox: Security Warning Although this page is encrypted, the information you have entered is to be sent over an unencrypted connection and could easily be read by a third party. Are you sure you want to continue sending this information? [Cancel] [Continue]
|
|
Lorenzo Orlando Caum
|
February 28, 2014 at 5:12 pm
Hey Scott,
This is just an idea but could you try this plugin:
http://wordpress.org/plugins/ssl-insecure-content-fixer/
From reading the description, it should change http links to https, thereby removing the mixed content warning.
—
Lorenzo
|
|
Scott Goodwin
|
February 28, 2014 at 5:18 pm
No dice, thank you for the suggestion though.
|
|
Scott Goodwin
|
February 28, 2014 at 5:32 pm
I’m close to figuring this issue out… it seems the root of the problem is indeed the fact that the form action url is set to: http://scottgoodwinassociates.com/courses/ rather than: https://scottgoodwinassociates.com/courses/
In firebug I edited the action to https and was able to get past the warning and was taken to the Verify Registration page rather the courses. I still need to figure out how to force the https action url, but now I know what is causing the issue.
|
|
Lorenzo Orlando Caum
|
February 28, 2014 at 5:39 pm
Could you try adding this to your theme’s functions.php file:
function adjusthttp($url)
{
$url = str_replace('http://scottgoodwinassociates.com/courses/', 'https://scottgoodwinassociates.com/courses/', $url);
return $url;
}
add_filter('the_content', 'adjusthttp', 105);
—
Lorenzo
|
|
Scott Goodwin
|
February 28, 2014 at 5:44 pm
It worked a treat! Thank you Lorenzo
|
