SteveMcA

Yes, I found a work-around by adding a hidden CF7 type input field that CF7 recognizes using a short code I added in functions.php. I can now use that value just like any other CF7 input, both in the form and in the email.

–Steve

FWIW,

I found a solution to my specific “wp-login.php?redirect_to” problem. Maybe this will help someone else. In short it was a domain naming convention problem. I took an existing MU 2.8 site and did an auto-upgrade to 3.2.1, then I followed the instructions in the Codex. I got 95% of the way there before hitting the “wp-login.php?redirect_to” problem.

I am creating a development/staging server that will have different sub-domains than production, so I looked at all the docs, updated the database and was able to get most everything copied and working. Everything worked find on the user side, but not on the admin side. My problems were when I wanted to use the Dashboard of the sub-blogs. Then I would get the dreaded “wp-login.php?redirect_to” problem. Even if you logged in withe a known good account you would just get redirected to the wp-login.php page, with no indication that there was no admin site for that domain.

For example:
If my main domain is https://www.example.com. The main blog domain name is the same: https://www.example.com. For some reason, I thought the second blog’s domain name was supposed to be of the form blog1.example.com, but it actually needs to be blog1.www.example.com.

I just changed my 2 blogs to use the new naming convention and I can now login as the super admin / network admin on https://www.example.com or blog1.www.example.com

–SteveMc