WF format lost

Because Wordfence is the only plugin with an issue. The site works fine. The SSL works and redirects. There are no other issues or conflicts. I have SSL working on my other sites and Wordfence works fine on them. I’m stumped. I’ve read the sourcecode. I manually reinstalled Wordfence. All I can think is something needs changed in the database as it’s like it’s not reading the WF CSS code.

So oddly, it cleared up on its own. May have been a caching issue. Nothing else worked (trying plugins, etc.) and all the code and data in the database seemed correct, so no reason for it not displaying. I do like when all of a sudden, it just starts working again but wish I knew for sure why. Only explanation is the cache cleared. Marking Resolved.

Thanks. I’m just going to follow up on this in case anyone is switching over to SSL as there are a lot of articles and every one seems to have differing advice. I just switched another site over to SSL. Nothing broke but the forced redirects in the wp-config.php file didn’t seem to do anything. And the recommended plugins seemed to make a mess of things on the last site (esp. getting looped into logging in every time in the dashboard). So here’s what did/does work:

1. Get your SSL certificate.
2. Update your Settings/General/Site URL to https://yoursite.com or https://www.yoursite.com
3. Use Search and Replace plugin to replace http:// with https:// in the database (BUT DO A ***DRY RUN*** FIRST AND LOOK THROUGH THE DATA as you really only want to change your site and could change other links)
4. Create a .htaccess file in Notepad++ or another editor and save as a txt file – if you do not already have one in the root directory.
5. Add the following code in the .htaccess file:

# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTPS} !on
RewriteRule ^(.*) https://%{SERVER_NAME}/$1 [R,L]
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>

# END WordPress

6. Save and upload to your root directory via FTP and set permissions to 644

When all of that is done, you should get green locks and your site should redirect to https:// on both the front-end and back-end (admin/dashboard) with no conflicts and should only take 10-30 mins. depending on how familiar you are with things.

Based on my experience, it seems better to do this manually than rely on plugins as they made a mess of things and there was no way to tell what caused it (for me at least).

If something is wrong in those steps or doesn’t work for you, please correct me, but that should be the ‘clean’ way to switch from http:// to http:// with no issues.

• This reply was modified 6 years, 2 months ago by wpexpertla. Reason: fixed typos