Title: [Plugin: WordPress HTTPS (SSL)] Plugin broke my Admin Area Last modified: August 20, 2016 --- # [Plugin: WordPress HTTPS (SSL)] Plugin broke my Admin Area * Resolved [Sulaiman](https://wordpress.org/support/users/sulaimank/) * (@sulaimank) * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/) * Hi There, * I have recently updated the WordPress SSL plugin from 2.0.4 to 3.0 and then i returned to my dashboard lately it took me out of the dashboard also i have tried to insert my correct login details it didn’t let me in! * It seems like this plugin lastest version has bugs with cookies or something like that… Please fix this issue as i have several authors who are contributed on our website they would complaint the login is not working 🙁 Please help!!! * [http://wordpress.org/extend/plugins/wordpress-https/](http://wordpress.org/extend/plugins/wordpress-https/) Viewing 15 replies - 16 through 30 (of 36 total) [←](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/?output_format=md) [1](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/?output_format=md) 2 [3](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/page/3/?output_format=md) [→](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/page/3/?output_format=md) * [Daedalon](https://wordpress.org/support/users/daedalon/) * (@daedalon) * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/page/2/#post-2691831) * I assume Tetoonline’s fix is for other 3.0 issue. Didn’t fix mine. * I also wanted to ask why does 3.0 clutter the admin sidebar with its own major HTTPS section? These settings need to be revised so seldomly that the old placement as a subsection of Settings is more appropriate. * Apart from these two issues, thanks for the work on the plugin. Enjoyed it up to 2.0.4 so much that I wanted to contribute with testing and feedback of the freshly-released 3.0 instead of waiting for bugfix releases. * [Daedalon](https://wordpress.org/support/users/daedalon/) * (@daedalon) * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/page/2/#post-2691836) * 3.0 also broke the functionality of plugin [Search Autocomplete](https://wordpress.org/extend/plugins/search-autocomplete/) in my test environment. With 3.0 enabled, the search autocomplete works until you click the suggested post. You’re then redirected to an URL that is the current URL + `[object Object]`, instead of the suggested post’s URL. * Plugin Author [mvied](https://wordpress.org/support/users/mvied/) * (@mvied) * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/page/2/#post-2691848) * Hey Daedalon, * Saying that his fix is “for another issue” doesn’t really make sense. I didn’t push out a plugin that’s just flat out broken. It’s broken due to something in your configuration that I had no way to test. The only way I can fix it is if you provide more information on what your settings look like, what kind of server configuration you have, etc. * I can’t think of a single line of code in the plugin that would produce this kind of problem. Have you tried deactivating other plugins? It may be worth setting up a new WordPress install in a subfolder and see if you can reproduce the issue. Any information would help greatly. * Settings are on the sidebar because I want it to be easy to find and if I ever add more sections to the plugin, I will actually have a place for them. With popout menus, it’s not as big of a deal as it used to be. I will be making it a configurable setting, though. * I’ll have to test compatibility with Search Autocomplete. * Thanks, Mike * [26thandmane](https://wordpress.org/support/users/26thandmane/) * (@26thandmane) * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/page/2/#post-2691858) * im having the same problem as everyone else is. i can not access my site nor my wp admin area. i didnt have the previous version of this plug in so how do i remove the plugin if i cant even log in to my wp admin area??????????? * Thread Starter [Sulaiman](https://wordpress.org/support/users/sulaimank/) * (@sulaimank) * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/page/2/#post-2691860) * Placing HTTPS label on Sidebar that increase amount of item on the dashboard sidebar… using HTTPS on Settings as subsection is much better that reduces the items on Sidebar that’s the differences 🙂 but users would love to have the option under settings that would make them easier… * [aglakimsmith](https://wordpress.org/support/users/aglakimsmith/) * (@aglakimsmith) * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/page/2/#post-2691862) * I had the same problem with a plug-in that I installed. I had to go into the actual applications upload page through my host provider and delete the plug- in on the backside. Then I was able to sign into my wordpress account and everything came up right. * [Daedalon](https://wordpress.org/support/users/daedalon/) * (@daedalon) * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/page/2/#post-2691868) * Mvied, different problems have been discussed in this thread. My post was to clarify whether the reported fix works for the one I reported, or is probably for a different one. Perhaps something in the way I wrote it made it seem like something else, but my intention was indeed to clarify, whether a problem was solved or not. * The problem with the URLs appearing at the top of the page, right before the adminbar, occurs even after disabling all other plugins. I could delete widgets only after disabling the plugin. * After erasing all the widget settings and trying out also the themes TwentyEleven and TwentyTen, I found that now, despite all widgets disabled and regardless of WordPress HTTPS being activated or not, there are three widgets visible: Search, Archives and Meta. If WordPress HTTPS is active, Archives displays only the archives links – the URL jumble mentioned before that with another theme went into the top of the page. If WordPress HTTPS is deactivated, Archives links appear and function correctly. With TwentyTen and TwentyEleven, these are shown in the secondary widget area and only if there are no other widgets active. With TwentyTen, after disabling other widgets, enabling them had no effect – only those three were shown. * Tried also on the live site on which the test site is based. Updating WordPress HTTPS caused the same URL jumble, which was solved by reverting back to 2.0.4. The theme in both cases is [Photog](https://wordpress.org/extend/themes/photog) with, you guessed it, lots of self-made modifications, none of which should cause the issue. * I then set up a different test site based on another live blog on the same server. There, roughly the same happened. Using [ChocoTheme](https://wordpress.org/extend/themes/chocotheme), no effects visible after updating to 3.0. With TwentyEleven and TwentyTen, the same. Troubles started when tried to alter or delete widgets. That didn’t produce any effect while WordPress HTTPS was on. After deactivating it, deleting all widgets and then reactivating, TwentyTen and TwentyEleven now behave in the same way as with the other site. Activating ChocoTheme enabled two of the previously disabled widgets. After deactivating WordPress HTTPS and deleting those plugins the sidebar now shows these, presumably theme default, widgets: * Search Pages Archives Categories Friends (which is Blogroll/Links renamed) Meta * With WordPress HTTPS deactivated all those work as expected. With WordPress HTTPS activated, Archives creates the same URL jumble as in the other blog. * Plugin Author [mvied](https://wordpress.org/support/users/mvied/) * (@mvied) * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/page/2/#post-2691876) * Hey Daedalon, * Well, if I can reproduce the problem, I can work on a fix. I’m certainly not experiencing anything like that on any of my test sites, so if you can let me on your server, I can certainly fix it. That’s generally the only way I can fix these kinds of bugs that only occur for certain people. Sometimes things can’t be fixed, it just depends. This plugin has gotten a lot more complicated than I ever thought it would, haha. * I need FTP or SSH access to a site that is experiencing the issue that I can mess with to try and work on a fix. You can email me at [mike@mvied.com](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/page/mike@mvied.com?output_format=md). * Thanks, Mike * Plugin Author [mvied](https://wordpress.org/support/users/mvied/) * (@mvied) * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/page/2/#post-2691878) * It seems like the upgrade process needs some work. I wish there were a forum were all the people who it worked for could go to tell me how great my plugin is, lol. No worries, this new version didn’t take me months or anything. Haha. * I’ll be fixing bugs as fast as I can reproduce them. I’ll have a bug fix version out soon. * Thanks, Mike * Thread Starter [Sulaiman](https://wordpress.org/support/users/sulaimank/) * (@sulaimank) * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/page/2/#post-2691880) * Plugin is great on 2.0.4 but not on 3.0 🙁 because there is so much of modified files that isn’t correctly fixed and affected the MOST of this plugin users… Also please fix the placement under “Settings” because users only configures the settings for HTTPS one time not several… I hope you get it as well i could see Daedalon has different type of issues on the latest version… * [Daedalon](https://wordpress.org/support/users/daedalon/) * (@daedalon) * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/page/2/#post-2691887) * At the moment I cannot give FTP/SSH access to any of the servers. I’d be happy to help any other way, for example by giving you in private more detailed information about the servers and installs you deem might be useful. I’ll email you about this. * I have one more blog where I can try the upgrade to 3.0. Some time in the near future there I’ll also be dealing with a new install on the same server where I could try installing WordPress HTTPS 3.0 as the first thing. * Thanks for the relentless work for the WordPress community! * Plugin Author [mvied](https://wordpress.org/support/users/mvied/) * (@mvied) * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/page/2/#post-2691889) * Hey Daedalon, * Without access to the server, I simply can’t fix it. There’s no information you can give me that I can debug the code with. I’ve seen one other user with this problem, so maybe they will let me fix it on their srver. Until then, there’s nothing I can do. * Thanks, Mike * [Daedalon](https://wordpress.org/support/users/daedalon/) * (@daedalon) * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/page/2/#post-2691898) * Just for the record, the same happened with the third site on the same server. The difference is that this time I first enabled the Archives widget to be used alongside the regular ones. Other than that, everything was the same: with WordPress HTTPS 3.0 active, Archives widget printed out URL jumble instead of the properly formatted hyperlinks to archives. * Hopefully the other affected user can help you with the fix. If you want to use some server information for comparison to find possible similarities, please let me know. * Plugin Author [mvied](https://wordpress.org/support/users/mvied/) * (@mvied) * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/page/2/#post-2691916) * Thanks. I’ll be sure to update the topic if I make any progress. * Thread Starter [Sulaiman](https://wordpress.org/support/users/sulaimank/) * (@sulaimank) * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/page/2/#post-2691943) * Bugs seems to be fixed! * [@mike](https://wordpress.org/support/users/mike/), Please check your email. thanks 🙂 Viewing 15 replies - 16 through 30 (of 36 total) [←](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/?output_format=md) [1](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/?output_format=md) 2 [3](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/page/3/?output_format=md) [→](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/page/3/?output_format=md) The topic ‘[Plugin: WordPress HTTPS (SSL)] Plugin broke my Admin Area’ 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/) * 36 replies * 11 participants * Last reply from: [BaliRakhra](https://wordpress.org/support/users/balirakhra/) * Last activity: [13 years, 9 months ago](https://wordpress.org/support/topic/plugin-wordpress-https-ssl-plugin-broke-my-admin-area/page/3/#post-2692053) * Status: resolved