@wpmuguru, I've got repeatable behaviour that I think might narrow it down to problems with the request or state. I used a fresh browser (private browsing) to perform this test.
Scenario 1 - pass:
- Navigate to http://www.codingmonkey.ca - public site shows
- Click Login link - successful redirect to http://wordpress-hendriks.rhcloud.com/programmer/wp-login.php
- Login - successful redirect to http://wordpress-hendriks.rhcloud.com/programmer/wp-admin/
- Navigate to http://codingmonkey.ca/wp-admin/ - successful redirect to http://wordpress-hendriks.rhcloud.com/programmer/wp-admin/ - this step can be repeated with the same correct result
Scenario 2 - fail:
- Navigate to http://www.codingmonkey.ca - public site shows
- Click Login link - successful redirect to http://wordpress-hendriks.rhcloud.com/programmer/wp-login.php
- Login - successful redirect to http://wordpress-hendriks.rhcloud.com/programmer/wp-admin/
- Navigate to http://codingmonkey.ca/ - public site shows
- Navigate to http://codingmonkey.ca/wp-admin/ - I'm redirected to http://www.codingmonkey.ca/programmer/programmer/wp-admin/ and get a 404 response - this step can be repeated with the same incorrect result
So know I know how to trigger the problem. Just have to figure out why. Going back to the public site after logging in must be altering the subsequent requests in a way that confuses the plugin.
Does that give you any ideas?