updated from 1.9.2 to 2.0 and completely broken.
couldn’t login to backend anymore, needed to to disable the plugins stuff in DB manually.
Still trying to find out what went wrong.
Why couldn’t you login?
Were you using Shared SSL in 1.9.2? If so, what was your host set to?
my config could be reviewed here:
After upgrade tool did not accept my shared sslhost:
So how to use the new plugin ?
I’ve got a bug fix release coming out soon. I’m making some changes to the method that validates URL’s and I think it’ll fix your problem. I’ll update the topic when it’s released or you can test it and see if it’s fixed.
Hey there, Mvied… I have a bit of an emergency and I could really use your assistance. I installed WordPress HTTPS on a freelance project I’m working on, with the goal being setting up a contact form that would, because it may contain sensitive information, be secure.
But now I’m completely locked out of the admin portion of the site, with 404 Not Found pages popping up everywhere. How can I fix this, because I need to send the site to the client within the next day or two?
Here’s the link… http://www.jcxmarketing.com/michellewest
Obviously, any help you can provide would be greatly appreciated.
Fixed it by changing wordpress-https_ssl_admin to 0 in the Mysql database.
That scared the hell out of me (someone who isn’t entirely comfortable tinkering with the inner workings of a site).
I work on the Event Espresso plugin team, and we’ve been recommending your plugin for a while, instead of our built in https option. But the version 2.0 is breaking our customer’s registration pages. Specifically, I’ve tracked it down to the form action. Even if I put an https://mysite.com directly into the html that goes into the_content(), even though the page is ssl (is_ssl() returns true), it gets rewritten to http://mysite.com. If I put https://mysite.com anywhere else, in the form id, for example, it doesn’t get rewritten, but only in the form action.
Is the registration form on an actual post/page that you can enable “Force SSL” on? If so, enable it on that page and that should make it always HTTPS.
The registration form is on a page by means of a shortcode on the page that triggers a function in our plugin. The page has the “Force SSL” checkbox turned on. The page loads via ssl, but the form action, which should be https (back to the same page), shows up as http. On submission, the page gets redirected to https, but loses all the form submission data.
I just pushed out version 2.0.1. Let me know if it fixes your issue.
Great job on the newest version. We have a little more testing to do, but it looks like we’ll be recommending it to our customers again. Sorry I hadn’t seen your last update to this post, and we were in a panic to support our customers, so we had forked your plugin from before the change six months ago.
Do you have a paid version of your plugin with support for like $10 a year. I know there are a lot of sites depending on your plugin for their business who would be happy to pay for a dedicated support path.
I currently do not have paid support, but I’m working on the infrastructure that it would take to do that the right way. I don’t want to offer paid support and not follow through with a great customer experience.
For the time being, I offer free support here, time willing. You can always donate if you’d like.
- The topic ‘WordPress HTTPS (SSL) 2.0 broken’ is closed to new replies.