mvied
Forum Replies Created
-
Usually this kind of thing happens when the redirect_to parameter on the wp-login.php page is incorrect. Try logging into just wp-login.php with no redirect_to parameter on it. Then trying browsing to /wp-admin/ and then logging in. If that’s the issue, /wp-admin/ may not work, but wp-login.php directly will work every time. Try it and let me know.
Forum: Plugins
In reply to: [WordPress HTTPS (SSL)] Secure connection could not be establishedUnfortunately, no. You can use remote debugging in the Android SDK to use Chrome developer tools on your phone’s browser to troubleshoot the issue. It’s pretty boss.
Forum: Plugins
In reply to: [WordPress HTTPS (SSL)] A strange behaviourTry uninstalling and reinstalling the plugin through the Dashboard. If that doesn’t work, try the development version and let me know if the issue persists.
Hmm, not a clue. Could you try the development version and let me know if the issue persists?
Forum: Plugins
In reply to: [WordPress HTTPS (SSL)] On WPMU setup, New Site Defaults not workingHmm, not a clue. Could you try the development version and let me know if the issue persists?
Forum: Plugins
In reply to: [WordPress HTTPS (SSL)] Trying to setup URL mapping with ver 3.4.0bWell, you’re going to want secure.mydomain.com to point to the same public_html folder.
Past that, I didn’t actually catch what the problem was. What’s not working how you want it to?
Forum: Plugins
In reply to: [WordPress HTTPS (SSL)] Plugin Crashes SiteThere is in my development version. I should have implemented it sooner, but my server has been flawless for years. Updated it last week and haven’t had the time to fix it. I have to log in and restart Apache a few times a day. Terrible.
It’ll have a timeout of 5 seconds in the next release.
Forum: Plugins
In reply to: [WordPress HTTPS (SSL)] Plugin Crashes SiteYeah, this last week my server has been eating itself. Typically it’s a non-issue.
Again, you still didn’t explain what the problem is. Take the time to actually explain what’s happening. As for what you did tell me, I don’t know if you’re talking about the SSL settings in Jigoshop or WordPress HTTPS, so that doesn’t help much.
The fact of the matter is you shouldn’t have conflicting settings. If a page is seucred in one plugin, you should secure it in the other. There is code to attempt to fix conflicting settings, but it only works if WordPress HTTPS is activated before (I think) Jigoshop. Either way, there’s not a great solution to having mismatched settings and there’s nothing I can do to fix it. You just need to make the settings match.
Forum: Fixing WordPress
In reply to: [WordPress HTTPS (SSL)] securing xmlrpc.phpNo. You would need to use a redirect rule in your .htaccess.
If someone makes a POST to an HTTP page, even if that page is being redirected immediately, there is a chance that it could be intercepted. Furthermore, it’s possible that the POST will be lost when the redirect occurs.
Hope that helps.
You should have had a lot more issues than that if that was the fix. At least you got it working.
I try to leave the server configuration up to the user and their hosting provider. If the server isn’t correctly reporting that the page is HTTPS, there’s really nothing I can do about it. The plugin has an entry in the debug log called “SSL: Yes/No” that helps identify this issue. If it says No on an HTTPS page, the server is set up wrong. I have limited time to develop and support the plugin, so I try to focus on people having issues with the plugin directly.
You’re assuming the issue is an incompatibility between plugins, which is unlikely. I’ve used Quick Cache and WordPress HTTPS together fine. Disable WordPress HTTPS and view the site over HTTPS and see if Quick Cache and Widget Cache are having issues still.
Forum: Plugins
In reply to: [WordPress HTTPS (SSL)] domain mapping not workingNo problem. I’m going to take my time with this version, so it’ll probably be a while before release. I’ve got a few other projects running parallel with it and some of the work I’m doing there is being ported into WordPress HTTPS.
If you didn’t install it through the Dashboard, you have to deactivate/reactivate the plugin to run the install/upgrade process. I moved the port out of its own field, that’s why your port was missing.
It’s just a bug somewhere in the code. Not sure where, though.
I can’t reproduce this issue. Could you tell me if this happens with the development version?