Support Forum
not sure how one can have it both ways... either you have the front end in ssl and 'tell' plugins that - or you dont... WordPress tells us the protocol in play... we can't possible know about another potential plugin (without explicit coding) and what they are doing...
basically, if I follow this, we are using the wp schema for the pages as per wp api, but your https plugin is redirecting our https urls in the admin back to http because of the 'appearance' of them being front end pages not covered by the force_ssl option... but we are in the admin and governed by force_ssl, so it would seem it should not dork with any urls in the admin as they are by definition force_ssl...
Afraid I have no idea how they are doing that, but if they allow you to hook into the process (ala like wp or other plugins do), seems like you could add your own check for is_admin() and bypass the force_ssl if you are in the wp admin...
Visit Cruise Talk Central and Mr Papa's World
Looks like you're right, it is because Simple:Press uses index.php, which is a frontend page. I presume there are no plans to change the functions to use another file, so we will likely have to find a workaround on our side. Thanks again, for all the help and quick response time.
currently, no plans to change using the primary WordPress entry point for those ajax type activities...
but as I mentioned, think the best answer might be in the https plugin... see if it has standard wp hooks that can be used to adjust how it works (like core, simple press and many other plugins)... do you have a link to that plugin? we might be able to see if it provides those kind of usability features...
Visit Cruise Talk Central and Mr Papa's World
Yes: https://wordpress.org/plugins/.....ess-https/
It hasn't been updated in a while but still works properly (except the Simple:Press issue).
I will try to take a look tonight and see if it has an api for extensibility... might be the weekend though before I can... depends on how busy my wife keeps me tonight... 🙂
Visit Cruise Talk Central and Mr Papa's World
took a quick look at the plugin (installed it)... interesting, it looks like you can set a url filter in the options to ignore the securing... have you tried that?
something like
/yoursite.com/index.php?sp_ahah=/
its regular expressions so might have to escape the ? sign
/yoursite.com/index.php\?sp_ahah=/
Visit Cruise Talk Central and Mr Papa's World
If you mean this: https://db.tt/MR9ETDlC
I had intended to mention in a previous post that this could all be resolved if the plugin offered an "exclude" functionality, but that does not exist. That area I took a screenshot of is actually a "force" section which we use to force SSL on entire sections of the site and all of their subpages, without manually having to checkmark each page.
ah, not what it appears from the code comments (did seem exclusion) but that was just a quick look...
had a bit longer look at the code and not really tracking what its doing... also dont see very many hooks so may not even be possible... but I suspect, if I can find where the check is being made its going to be a simple change from wp-admin check to is_admin()... plugin has not been updated in ages, so if it is a simple change to it, you might be able to do it... but more time needed to follow its logic...
did install it locally, but not getting the same response as you so must be other configurations I am missing...
more this weekend...
Visit Cruise Talk Central and Mr Papa's World
Here is how we have it configured: https://db.tt/OHlLTiFj
The second option is disabled because we already have that set in wp-config. It is the third option being enabled that causes the problem.
1 Guest(s)