mvied
Forum Replies Created
-
Forum: Plugins
In reply to: [WordPress HTTPS (SSL)] Backend redirects to 404 – Not FoundUmm, what? If there is an incompatibility with another plugin, this is hardly resolved. Could you explain?
Forum: Plugins
In reply to: [WordPress HTTPS (SSL)] FORCE_SSL_LOGIN for shared SSLI’ve considered adding a similar solution to WordPress HTTPS. It would have to be a little more complex than that, but it would be easy now that I think about it. I may do that now. I’m doing a lot of restructuring in the plugin right now. Working on version 3.4 and so far, it’s looking to be a really nice release. I’ll see what I can do. Would you be interesting in testing it for me?
Forum: Plugins
In reply to: [WordPress HTTPS (SSL)] PHP error on general settings saveI’ll take care of this in the next release. Thanks.
Forum: Plugins
In reply to: [WordPress HTTPS (SSL)] HTTPS WordPress Plugin strips font and hides widgetIf you’d like, you can try the development version. I’ve added some checks for fonts. Let me know if it works for you.
Forum: Plugins
In reply to: [WordPress HTTPS (SSL)] HTTPS Purchase Required?You need an SSL certificate of some kind. If you host doesn’t provide a free, shared SSL, then you must purchase one.
Forum: Plugins
In reply to: [WordPress HTTPS (SSL)] FORCE_SSL_LOGIN for shared SSLIf the plugin doesn’t work after setting your SSL Host to the Shared SSL, turn the Proxy setting On and it should work. I would recommend getting a host that isn’t terrible, though.
Forum: Plugins
In reply to: [WordPress HTTPS (SSL)] Only Admin HTTPS functionsAnything that causes a warning on error has to taken on a case-by-case basis. It’s not always as simple as it being an incompatibility between plugins. Often the issue is theme dependent or too specific to code into WordPress HTTPS. However not always. In my plugin, this module’s purpose is to fix incompaitibilities with E-commerce plugins. If I can reliably reproduce an incompatibility, I will code in a fix for it.
I don’t have any issues with WooCommerce, but I also can’t test every single configuration that exists. If you can show me what’s going on, I can see about a fix. It’s possible that the issue is theme dependent in which case I can tell you how to fix it with URL Filters.
Forum: Plugins
In reply to: [WordPress HTTPS (SSL)] how to avoid images being linked as https://?You don’t have to worry about that. The plugin takes care of everything. HTTP page show HTTP images and HTTPS pages show HTTPS images. It’s not an either or thing.
Forum: Plugins
In reply to: [WordPress HTTPS (SSL)] SlideRocket IssueYeah, and even when I fix this bug, you will still get those warnings because even if you call those slideshows over HTTPS, they load HTTP content in them.
I set up the same iframes in my test environment and got it fixed. Thanks for your help.
Forum: Plugins
In reply to: [WordPress HTTPS (SSL)] WP SSL 3.3.5 does not work with qTranslate 2.5.34Sure, no problem.
Forum: Plugins
In reply to: [WordPress HTTPS (SSL)] WP SSL 3.3.5 does not work with qTranslate 2.5.34Did you even bother testing without WordPress HTTPS? I did and the problem exists without it. https://wordpresshttps.com/?lang=de
Forum: Plugins
In reply to: [WordPress HTTPS (SSL)] ajax calls for google charts not workingThe AJAX call is probably being set to HTTP because of Force SSL Exclusively. You’ll have to look at the URL that is being called and create a URL Filter to match it to secure it.
Forum: Plugins
In reply to: [WordPress HTTPS (SSL)] domain mapping not workingIt’s not quite that simple, but that is the end result.
I created a generic filter called ‘https_external_url’ here that is simply a filter for any HTTPS external element. Then, in my domain mapping module I use that filter for the domain mapping here. This code will only be run when securing elements on an HTTPS page.
Forum: Plugins
In reply to: [WordPress HTTPS (SSL)] SlideRocket IssueThey do host it all over HTTPS. The issue is the frame is coded as http://app.sliderocket.com:80. The plugin does not blindly change every external resource to HTTPS because not every resource will be available over HTTPS. The plugin tests for the validity of the resource. In this case, when it changes the scheme to HTTPS, you end up with https://app.sliderocket.com:80/ which does not work because port 80 is specified in the URL.
I’ve modified my plugin to also remove the port in this case because the HTTP port will never be valid for the HTTPS address.
If you could, please give the development version a shot and let me know if the issue persists.
Forum: Plugins
In reply to: [WordPress HTTPS (SSL)] domain mapping not workingIn the next version I’ll make it so you can map local domains as well. There’s no reason you shouldn’t be able to.
What I want to avoid is people mapping their domains here instead of using a domain mapping plugin. But, I guess I’ll just have to trust people.