mvied
Forum Replies Created
-
Forum: Plugins
In reply to: [WordPress HTTPS (SSL)] [Plugin: WordPress HTTPS (SSL)] Redirect LoopHey Bert,
I just pushed out 3.0. Try updating and see if anything changes. Let me know.
Thanks,
MikeHey 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,
MikeHey Angie,
I actually pushed it out last night (hence the previous post) but realized that I hadn’t tested in PHP 5.2.4 and it was broken! If you’re using PHP 5.3+, you can grab a copy under Other Versions. Just look for the link to 3.0. After work I’ll be working on fixes and will hopefully push it out again.
Thanks,
MikeIt looks like there are a few major bugs that I didn’t catch in 3.0. I’ve reverted the stable tag back to 2.0.4. If you want to try out the current development version of 3.0, you can download it here.
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. 🙂
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.
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.
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,
MikeWell, 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,
MikeIf 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.
Forum: Plugins
In reply to: [WordPress HTTPS (SSL)] [Plugin: WordPress HTTPS (SSL)] Slash TruncatedHey Mark,
Thanks, that helped me track down the bug. I’ll be working on a fix.
Thanks,
MikeForum: Plugins
In reply to: [WordPress HTTPS (SSL)] [Plugin: WordPress HTTPS (SSL)] Slash TruncatedHey Mark,
Is this only happening on the login form and nowhere else? Do pages appear to be working correctly otherwise?
Thanks,
MikeHey Karen,
Is there actually another plugin out there that still works? I didn’t think I had any competition, haha.
Let me know! 🙂
Thanks,
MikeI just pushed out version 3.0 which may or may not fix the issues you were having. Please try updating and let me know if you need any help.
Sorry for the late response. I have not had time to support the plugin for a while now. Since I just pushed out 3.0, I’ll be keeping an eye on the support forums to fix any bugs that arise.
Thanks,
MikeI just pushed out version 3.0 which may or may not fix this. I ended up taking a more generic route for detecting proxies. Please try updating and let me know if you need any help.
Sorry for the late response. I have not had time to support the plugin for a while now. Since I just pushed out 3.0, I’ll be keeping an eye on the support forums to fix any bugs that arise.
Thanks,
Mike