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… 🙂

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=/

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…

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.

still cannot get the error with those settings… the links are all https…  any .htaccess settings?

but will look into this weekend…

okay, give this a try…  in the https plugin folder, edit the file plugins/wordpress-httpslibWordPressHTTPS.php…  and at line 342, find this line of code:

                    $updated->setScheme(‘http’);

and change it to

                    if (!is_admin()) $updated->setScheme(‘http’);

think that will get you going… and since that plugin hasnt been updated in years and  years, you shouldnt have to worry about updates over writing your changes…

Incidentally, I would call this a bug with that plugin…  you have force_ssl_admin set to true, yet its converting urls from https to http…  if it had just left them alone, all would be good…  it is misinterpreting those urls as direct links to front end content, which they are not…  all i have done is stop the converting of those urls from https to http…  and if there should actually be one, then the plugin should catch it on the other end when loaded anyways, right?

I really thought I had updated this, but I must’ve just written the post and not submitted it…
Anyway, you found the right line, but your fix did not work. This ended up working:

if (strpos($_SERVER[‘REQUEST_URI’], ‘sp_ahah’) === false) { $updated->setScheme(‘http’); }

If there is any reason why it wouldn’t be a good idea to do it this way, please let me know.

Edit: it appears I actually have spoken too soon – that for some reason fixes the inability to modify user groups, but not the inability to click on the red female icon from the user list in the admin panel (which is accessed via HTTPS), or to moderate threads in the forums themselves (accessed via the public facing forum front-end on HTTP). Back to the drawing board… Any ideas?

it worked when this was done some time ago – but must admit I did not try every possible form or action..  but since it was one you tried, pretty sure I tested it…  and off hand cannot think why it would be any different for that…  when I get a chance, I can try to look at some more, but right now I dont even have that plugin around…  maybe this weekend…