|
mipstickyvette
|
September 16, 2016 at 4:00 pm
Hi, I’ve just setup SSL on a client’s website and everything went well.
The website is https://www.mipstick.com/.
When I search for “mipstick” on Google, I get the results, click on the first link and I get a blank page with the following errors:
Warning: Cannot modify header information – headers already sent by (output started at /home/mipstick789/public_html/wp-includes/wp-db.php:1868) in /home/mipstick789/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Front_Controller.core.php on line 108
Warning: session_start(): Cannot send session cookie – headers already sent by (output started at /home/mipstick789/public_html/wp-includes/wp-db.php:1868) in /home/mipstick789/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Session.core.php on line 403
Warning: session_start(): Cannot send session cache limiter – headers already sent (output started at /home/mipstick789/public_html/wp-includes/wp-db.php:1868) in /home/mipstick789/public_html/wp-content/plugins/event-espresso-core-reg/core/EE_Session.core.php on line 403
Warning: Cannot modify header information – headers already sent by (output started at /home/mipstick789/public_html/wp-includes/wp-db.php:1868) in /home/mipstick789/public_html/wp-includes/pluggable.php on line 1174
It seems like when trying to access the website over regular http triggers these issues. But when you type https before the domain name, then the website appears fine.
Please help, how do I fix this?
Thank you,
|
|
Josh
|
September 16, 2016 at 4:06 pm
The first thing you need to do is set WP_DEBUG to false. You can set WP_DEBUG to false by editing the wp-config.php file.
You can use an [FTP client][1] and [a text editor][2] to access change this line to the site’s wp-config.php file:
define('WP_DEBUG', false );
[1]: http://codex.wordpress.org/FTP_Clients
[2]: http://codex.wordpress.org/Editing_Files#Acceptable_External_Editors
Then, you follow the guide posted here to force https for the entire site:
https://eventespresso.com/wiki/espresso-sslhttps/
|
|
mipstickyvette
|
September 16, 2016 at 4:19 pm
Thanks Josh.
I already have wp debug set on false.
Your article recommends to use a plugin to force SSL throughout the website but I’m already using this feature within “iTheme Security” plugin, forcing SSL on the entire website, along with the admin side.
I’ve also read on your article that if I have Woocommerce installed (which is the case), I should ensure that Woo doesn’t force any SSL on checkout?
Does that mean it could compromise the security of online payments if I uncheck this box?
So I’ve done all that and it still doesn’t work. The only thing I haven’t done is install that WordPress HTTPS plugin yet, I’m just waiting for your reply first.
Thank you.
|
|
Josh
|
September 16, 2016 at 9:50 pm
Does that mean it could compromise the security of online payments if I uncheck this box?
No, because Woo Checkout will still be https if you force SSL site wide. That’s because every page on your site will be https. The iTheme Security SSL isn’t recommended, but the Simple SSL plugin is recommended.
When you see errors displaying on your site while WP_DEBUG is false, then it’s very likely that display_errors is turned on. In which case, you should add the following to the wp-config.php file:
@ini_set( 'display_errors', 0 );
|
