If the plugin isn’t working as intended, then how about posting some information that would actually help me fix the bug? This topic is not helpful.
Wow, thanks for the fast response.
The page does not load. Source code shows NOTHING. Everything is blank.
Sorry for the last post. I am just very frustrated as my paying subscribers are contacting me saying they cannot log in now.
Everything was working PERFECTLY prior to the update. I’m not sure what other info I can give. Questions for me?
Now my admin has locked me out. I can’t access my site at all, neither can my subscribers. Very sad. 🙁
Well, I did just push the update out about an hour ago, so I’m trying to keep an eye on the forum (Although it’s late, I’m heading to bed).
I understand your frustration. Trust me, I’ve spend more time writing and testing this plugin than I care to think about. I would never recommend updating a point release on a production site. I try to work all the bugs out of this thing, but it’s pretty much impossible.
Do you have any way to view your Apache error logs? It sounds like there’s a PHP error or something. I’ll be back in here tomorrow after some much-needed sleep.
Thanks,
Mike
Oh, add define('WPHTTPS_RESET', true); to your wp-config.php. That should wipe any settings. If that doesn’t do it, you’ll have to delete the wordpress-https folder. Let me know what it takes. I’ve certainly never had the plugin act that way in testing.
Thanks,
Mike
I had no idea this was an untested update. No WAY would I have done this… I want to go to bed too. I work 3 jobs and have a new baby. I sleep 4 hours a night… tonight I’ll sleep 1 hour. I’ll disable this plugin and try to recover. thanks.
By no means is it untested. I spent about 20 hours on it this weekend, mostly testing. It’s a very complex beast and I’m only one guy, haha. Sorry for the trouble.
Oh, it’s also worth noting that it will work for 90% of people out of the box. It’s generally the odd server setups that cause issues. I don’t have test environments for every permutation of server configuration, so it’s pretty much impossible to catch all the bugs, especially in a re-write.
OK, thanks. I’ll try that now. I appreciate you working on this plug-in. Please accept my apology for being irritated. It’s late and I was about to go to bed when I hit UPDATE so I’m just a little perturbed now (site still down and 1.2 hours later… still working with tech support on site…)
Please try to gather as much information as possible. If anything, I don’t mind logging into the site (or a fresh WP install on the same server) and working on a fix there. Often, that’s the only way I can come up with a fix since, like I said, there are some many different server configurations that can cause all sorts of different bugs.
I’ve had a few other concerning bug reports, so I’m going to revert the stable version back to 2.0.4. Hopefully those who have experienced issues will help me work on bug fixes. 🙂
Yeah, I just deleted the new version. Downloaded 2.0.4 and installed it. Everything is back to normal thank god. I’m going to sleep now…
Thanks for a great plugin. 2.0.4 works great. I would just stick with that. Why fix what isn’t broken? 😛
>> Why fix what isn’t broken?
There were issues with the previous version for some people. For example, on our servers there is an endless redirect loop that makes the previous version unusable. So I applaud Mike’s efforts.
Mark
Hey Mark,
Thanks for the backup! Haha. Yes, often times bugs are caused for users with configurations I could not test, and previous bugs are fixed for others. I’m hoping to finally get the plugin to that 100% satisfaction mark, but for that I need the feedback of my lovely user base to work out any bugs. 🙂
I had to rollback to 2.0.4, but will hopefully be working out a couple of bugs in 3.0 and pushing it out tonight. I realized that rabbitshavefangs’ problem is most likely an incompatibility with PHP 5.2.4.
Thanks,
Mike
