|
PCOS Challenge
|
March 4, 2015 at 10:56 am
WP Version:4.1.1
EE Version: 4.6.12.p
Browser: Chome Version 40.0.2214.115 m
Site: http://www.pcoschallenge.org/symposium/
1) I just installed the recommend WordPress HTTPS plugin for securing registration and payment pages. I was following the instructions on this page:
https://eventespresso.com/wiki/espresso-sslhttps/
2) I enabled Force SSL Exclusively and checked “Secure Post” for the Registration Check Out Page, Transaction Page, and Thank You Page.
PROBLEM: The system hangs with a spinning gear after a registrant selects his/her ticket quantity, enters their address information and presses “Proceed to Payment Options”
After completing the information on the registration page,
|
|
Josh
|
March 4, 2015 at 12:00 pm
Hi checked the where the registration form is and it turns out there are a number of JavaScript errors related to the countdown timer as well as the WordPress admin ajax loading as http:
Mixed Content: The page at 'https://www.pcoschallenge.org/symposium/registration-checkout/' was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 'http://www.pcoschallenge.org/symposium/wp-admin/admin-ajax.php'. This request has been blocked; the content must be served over HTTPS.
What the above error means is you will need to set the WordPress https plugin to load the WordPress admin as SSL. This will allow the admin-ajax.php endpoint to be served over https.
|
|
PCOS Challenge
|
March 4, 2015 at 12:33 pm
I have both now have “Force SSL Administration” and “Force SSL Exclusively” checked, and I’m still getting the same error. Is only one supposed to be checked?Or any other thoughts?
|
|
Josh
|
March 4, 2015 at 2:38 pm
Hi there,
The “Mixed Content: The page at ‘https://www.pcoschallenge.org/symposium/registration-checkout/’ was loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint ‘http://www.pcoschallenge.org/symposium/wp-admin/admin-ajax.php’. This request has been blocked; the content must be served over HTTPS.”
errors are still in the Developer tools console. Is the SSL certificate a shared certificate or is it dedicated?
Along with that, it may also help to deactivate the other plugins that are not loading their scripts as https. For example, if the countdown timer script is added by a plugin that loads all scripts as https, and it forces the admin-ajax.php script to load as http, you’ll get the error you’re seeing.
|
|
PCOS Challenge
|
March 4, 2015 at 2:51 pm
The SSL certificate is dedicated. The countdown timer is part of the theme, not a plugin and I’m not sure how to tell which scripts are being loaded as http vs https.
|
|
Josh
|
March 4, 2015 at 3:15 pm
The countdown timer script isn’t loading as https. One quick way to find out if your theme is causing the conflict is by installing the theme test drive plugin and try a registration with the twentyfifteen theme active for the admin only.
|
