Login using http:// vs. https:// and the associated problems with viewing menu items, google adsense ads, and node tabs. HELP $

Hello,

I have been trying to secure my site, but I am running into a few critical issues that are preventing the site from being functional/secure.

My site is http://carbonpig.com

What I'm trying to do

I'm trying to make all of my admin, login, ubercart payment and checkout, user*, logout, etc. (i.e., pages with forms/input fields) pages secure.

I'm trying to enforce/guarantee that my homepage, "article*" pages, and other designated content types are not secure because the google adsense ads won't appear on the https:// (secure) pages.

The Issue(s) I'm Facing

I've found that if you login in an http:// environment and then go to your account page in an https:// environment that it doesn't acknowledge that you're logged in as an authenticated user and vice versa; logging in via secure http and then going to an unsecure page.

This is important because it is affecting my dropdown menus and node tabs as follows:

-If you log in at https://carbonpig.com/user/login everything looks fine and all the desired pages are secure.

-Then, if you then navigate to an article page, as I want, the https:// changes to http://. This is important because we need the ads to show.

-However, as mentioned, the site no longer recognizes the user as being logged in. Therefore, the dropdown menus no longer show any links that are restricted to the role that you are loggen in as, and the view and edit tabs disappear from the article page.

What I've Tried

I've tried both the secure pages (official and dev) and secure role modules alone and in tandem to try and engineer a solution. I thought maybe I would just designate certain pages for certain roles to be secure and all pages for my "publisher" role (they can write articles), so that I could have the edit tab show up on article pages...needless to say it didn't do what I was expecting (i.e. the secure role module didn't take precedent over secure pages.

I always flush all caches and when I've tried different module versions I do a complete uninstall from my modules page and at the database level in the system table.

I've tried ticking and checking every box including manually defining the options for:
-Make secure every page except the listed pages. and
-Make secure only the listed pages.

I've also tried pulling my hair out and cursing Drupal, but that didn't work, because deep down, I love Drupal.

What I'm Hoping For

1. A simple solution, that isn't currently in the que.

or

2. Someone to emerge that understands php and Drupal more than myself that can help troubleshoot this in a skype call for free.

or

3. Number two, but I can pay a modest amount because I'm a poor environmentalist hoping to build a really great site.

Lastly

I've disabled the module for now so that the core functionality is back up. If someone is willing to help please email me via Drupal with ideas or reply to this post and I'll enable during a scheduled time.

Thanks,

CarbonPig