We purchased an SSL certificat from network solutions (would never recommend them to my worst enemy, btw).
Apparently it’s activated… did a few checks that says it’s activated for our domain. But when I put in https://www.texasshredderclassic.com the entire site breaks. To be more specific, by “breaks,” I mean it completely disables the CSS, and my login User+Password no longer work (seems like this might be a clue?)
I’ve tried downloading WordPress HTTPS, but that kicks me out of the admin page and also mangles the CSS.
I don’t care if it works on the entire site, just need it working for our form page (texasshredderclassic.com/registration) â using gravity forms and connecting to authorize.net!
I’m tearing my hair out here because I don’t have a clue where to go next. Seems like we have the SSL cert… just can’t get the damn thing to work! Any help is GREATLY appreciated!
For the login part, this works for me …
Paste the following line in your wp-config.php
but make sure that you do it before the following line
By doing so you can get your admin panel back …
See details here
Also to avoid getting Mixed content, after restoring your admin panel, remember to go to SETTINGS, General, change Server URL from http to https.
Go to your WordPress General Settings and change the WordPress Address (URL) and the Site Address (URL) from HTTP to HTTPS.
ps. And disable all the plugin breaking your site.
If that doesn’t fix this there is a proper guide here and several steps you can take: https://managewp.com/wordpress-ssl-settings-and-how-to-resolve-mixed-content-warnings
This type of CSS “breaking” is caused mostly due to accessing files via HTTP request on an HTTPS connection, or to be short, accessing insecure files.
In the provided link, the Registration form is loaded in an iframe, and also, its CSS files are loaded by HTTP and not by HTTPS connection.
So, if you have direct access to the files that is served as registration form, changing all http:// to https:// might does the job, but I’ve been using the SSL Insecure Content Fixer, and it works fine till now.
Have you tried running SSL Insecure Content Fixer? (disclosure: I wrote it, but I just want to know have you tried fixing your problem with this plugin). It should clear up most of the script load errors, at least for plugins that haven’t been too naughty.
I notice that you’re running WP 3.5. I had a report this morning that someone running WP 3.5 with stylesheets loaded using
bloginfo('stylesheet_url');was getting the same problem, insecure content report on their theme’s stylesheets. Can you look at your theme and tell us how your stylesheets are loaded?