|
MattLynch
|
August 28, 2020 at 11:50 am
Hello,
I followed the guides linked below and WP Engine is securing all pages but the registration page is still not working.
I ran a search and replace in the database, the wp_options table has https for the siteurl and home, and there is no other SSL plugin installed. Cloudflare is setup to force HTTPS, I will test that while waiting for a response.
https://eventespresso.com/wiki/espresso-sslhttps/
https://wpengine.com/support/add-ssl-site/#secureoptions
The url for the registration page is fastfast530.com/register
|
|
Tony
|
August 28, 2020 at 12:01 pm
Hi there,
Why are you are loading the calendar through an iFrame?
Within that register page you’ll have something like:
<div style="width:100%; height: 500px;">
<iframe src="http://{domain}?calendar=iframe" width="100%" height="100%"></iframe>
</div>
You need to manually change the above to use HTTPS.
However, I’m not sure why you are loading the calendar on the site through an iFrame. How come you aren’t calling [ESPRESSO_CALENDAR] directly on the page?
|
|
MattLynch
|
August 28, 2020 at 12:11 pm
Turns out there was a hardcoded url in the register HTML that does not show up in search and replace.
I fixed this block of html on the register page and it is now working:
<div style="width:100%; height: 500px;">
<iframe src="https://fastfast530.com?calendar=iframe" width="100%" height="100%"></iframe>
</div>
|
|
MattLynch
|
August 28, 2020 at 12:12 pm
That iframe was auto inserted when the register page was created by the plugin
|
|
Tony
|
August 28, 2020 at 12:15 pm
That iframe was auto inserted when the register page was created by the plugin
Event Espresso does not create a page for the Calendar, that has to be done manually and the shortcode added.
I recommend switching the above out to use the shortcode rather than the iFrame.
|
|
Tony
|
August 28, 2020 at 12:18 pm
Side note, if you are using WPEngine you need to follow the steps here:
https://eventespresso.com/wiki/setup-wpengine-hosting-event-espresso/
WPEngine forcing server side caching on all pages, EE’s critical pages need to be excluded for it to work (it will work now if you are logged in, but not logged out)
|
