Posted: April 13, 2020 at 12:24 am
|
Hello A number of years ago we implemented https:// into our wordpress general settings to secure all pages across our website. This worked fine however we have noticed recently that a number of our pages are loading as insecure http:// pages. This is also causing the event espresso shopping cart not to work (on wordpress pages where we use the cart shortcode but the pages are loading as insecure – message says the cart is empty). Can you help? |
Hi, We’ve received your request for priority support. I’ve logged in and I can see that your site has the WordPress https plugin, and it’s setting “Force SSL Exclusively” is unchecked. I’ll go ahead and activate that setting and that should fix the issue for you. May I ask is there a reason why Event Espresso hasn’t been updated on your site to the current version of Event Espresso 3? (currently 3.1.37.17) There have been a number of fixes since 3.1.37.12, especially with compatibility issues with newer versions of WordPress and PHP. If you upgrade PHP or WordPress (or both) you’ll also need to update to the current version of EE3. |
|
Actually, your site also has the iThemes security plugin, which also has an https feature. So since there’s no need to have two plugins that both can force SSL, where one could conflict with the other, we’ll just go with iThemes security and remove the other SSL plugin. |
|
Update: the iThemes security plugin is now handling the https. The other https plugin (this one) has been removed. |
|
|
This reply has been marked as private. |
The plugin SSL Insecure Content Fixer serves a slightly different purpose. How it works is it “fixes” items within your site’s content that start with http, changing them to https. For example if you have a picture on a page of your website, and its image tag points to a URL that starts with http, the SSL Insecure Content Fixer plugin will automatically change the URL to start with https. This prevents the mixed content warning that happens when a page’s URL starts with https, but separate elements on the page like pictures have a URL that starts with http. So you may still need this plugin if the above scenario applies to the content in your website. |
|
The support post ‘Securing Website pages’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.