Title: Deactivating
Last modified: August 31, 2016

---

# Deactivating

 *  [Subhodeep Sadhukhan](https://wordpress.org/support/users/subho1995/)
 * (@subho1995)
 * [10 years, 1 month ago](https://wordpress.org/support/topic/deactivating/)
 * Deactivating the plugin makes it lose the styling. The website is displayed just
   as a series of texts. Even the admin panel loses it’s styling. Help.
 * [https://wordpress.org/plugins/wordpress-https/](https://wordpress.org/plugins/wordpress-https/)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  [bulewold](https://wordpress.org/support/users/bulewold/)
 * (@bulewold)
 * [10 years ago](https://wordpress.org/support/topic/deactivating/#post-7376910)
 * Same issue, if anyone knows how to deactivate/uninstall this plugin, please share!
 *  [janco](https://wordpress.org/support/users/janco/)
 * (@janco)
 * [10 years ago](https://wordpress.org/support/topic/deactivating/#post-7376912)
 * Right-click on the pages that are broken and view source. If you see a lot of
   https links still, that’s your problem.
 * Since the plugin hasn’t been updated in two years–what with all of the changes
   to WordPress during that time–I’m guessing there aren’t any functional provisions
   to remove the “add https” changes from the database and anywhere else they may
   have been written to while the plugin was activated (e.g., .htaccess files). 
   Additionally, in various cases, plugin developers didn’t necessarily include 
   provisions to remove the code rewrites if their plugin was simply deactivated.
   It’s often (but not always) the case that such plugins have to be deleted in 
   order to facilitate that process.
 * Given how long it’s been since the plugin was deactivated, I’d recommend exporting
   a copy of the database as well as downloading all files in your document root,
   then performing global searches for the use of https specific to your site (w.
   g., search for ‘[https://mysite.com&#8217](https://mysite.com&#8217); and ‘[https://www.mysite.com&#8217](https://www.mysite.com&#8217);).
   Clean those out (change ‘https’ to ‘http’ in those cases, then overwrite the 
   database with the updated sql file, and replace the files on the server that 
   need updating. **But be careful…**
 * Be careful with all htaccess files before making changes–inspect those individually
   where https was found, and make changes only if you’re sure about what you’re
   doing (e.g., remove force_ssl, etc.). Also, don’t make changes to https where
   links point to external sites.
 * If you’ve gotten this far and don’t understand what I’ve mentioned, you may need
   to seek the assistance of someone who does.
 *  [Aboobacker Amani](https://wordpress.org/support/users/aboobackeramani/)
 * (@aboobackeramani)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/deactivating/#post-7376913)
 * How to change href=”// to href=”https://

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Deactivating’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/wordpress-https_bec2c9.svg)
 * [WordPress HTTPS (SSL)](https://wordpress.org/plugins/wordpress-https/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordpress-https/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordpress-https/)
 * [Active Topics](https://wordpress.org/support/plugin/wordpress-https/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordpress-https/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordpress-https/reviews/)

 * 3 replies
 * 4 participants
 * Last reply from: [Aboobacker Amani](https://wordpress.org/support/users/aboobackeramani/)
 * Last activity: [9 years, 11 months ago](https://wordpress.org/support/topic/deactivating/#post-7376913)
 * Status: not resolved