Once again, I have no idea what's going on with my BOA.
On Friday of last week I upgraded to the most recent version of Barracuda head as recommended in the comments when I asked for help the other day when my php.ini overrides are not being recognized, I have been having problem with a production site login redirecting to a secure https URL.
Before the Barracuda upgrade I had cloned the production www site back to dev so we could do some major content and navigational changes. I also added the Media module and some of it's related modules as well. Then I cloned the dev site back to production on the same platform. I verified the sites before and after the cloning. The platform is modified version of Open Public Beta 2.
After the upgrades I migrated the site back to production and now when I go to the login page on the production site redirected to a secure https URL.
This of course prompts a warning that the site is not secure. This is also causing a problem with editing, because when the site user is forced to operate in https mode and if you edit a node and place a picture on page using WYSISWYG and Media module, then the picture will not load for a visitor with the http URL. This is also causing problems with loading the CSS in Windows Google Chrome on Vista. (BTW, I'm actually working on an iMac running Parallels for Vista.)
This seems to only happen with the production site, not the dev site. Although in Windows Vista Chrome I did get the certificate warning when I went to the dev site too, but this was after I had gone to the production site on www.
The site I'm working on is: http://www.bryanclenahan.com and the production site is http://dev.bryanclenahan.com
If you go to the http://www.bryanclenahan.com.user it will redirect to https://www.bryanclenahan.com/user and give you security warning.
I found a discussion in these forums called SSL enforced from install script and I have reviewed the installed global.inc file where this might be causing this to occur, but I can't find where such a thing might be happening.
The whole reason I'm on the head version is because of I was having problems upgrading to BOA-2.0.2. See Upgrade to BOA-2.0.2 failing and git is being removed on Ubuntu Lucid. I'm assuming it would not be safe to switch back to the stable version Barracuda until the next release since I've installed with a version of head after that, correct?
Things I've done to asses and fix the problem:
- I destroyed the cloned site to production and tried cloning again. Nothing changed.
- I have another fresh Drupal 7 based site on another platform that was in dev only and I cloned that to production and do not see the same problem as I do with this Open Public site.
Things I'm planning to try next:
- Clone the dev site to another sub-domain and see what happens with that.
- Clone the production to another sub-domain and see what happens with that.
- Upgrade my modified Open Public platform to the latest version of Open Public (don't ask me why didn't do that already, it's a long story), but I don't see where that would solve this problem anyway.
- And of course, anything anyone recommends here!
Thanks for any and all your help in advance, I really need it!!!! My friend is trying to launch his campaign right now and I need to get this working!
Steve
P.S. I hope this all make sense, I'm exhausted.
| Comment | File | Size | Author |
|---|---|---|---|
| barracuda.cnf_.txt | 1.53 KB | wickwood | |
| install.log_.txt | 5.56 KB | wickwood | |
| barracuda_log.txt | 2.63 KB | wickwood |
Comments
Comment #1
omega8cc commentedThis is normal and expected with Open Public, as it enables securepages by default: #1480780: Remove securepages configuration install task so it is not a BOA issue.
As for Aegir compatible version, note that the last working version is beta3: #1366084: PHP segmentation fault on install with Aegir
Comment #2
omega8cc commentedSo, in short - disable, uninstall and remove securepages there.
Comment #3
wickwood commentedThank you, that was it. I Secure Pages module must have got turned back on when I accidentally turned off OpenPublic Defaults and then re-enabled it, I know it must have been off since we first built this site last summer.
Thanks once again for saving my butt, Omega8, and putting up with me!
Comment #3.0
wickwood commentedI added in some more things that I tried and that I'm planning trying.