billibones

I have resolved the issue. What I had to do, was go into the checkout page itself, click on the payment area “block” and select to switch to the classic checkout page. The newer “blocked” checkout page does not support the NMI extension.

Marking resolved. Thanks.

Awesome, I just stumbled across this logic, when i saw your reply, thank you so much,working like a champ now =) Much appreciation.

Hey I did find this out there though that might apply to your situation.

Adding a function to your template functions.php file:

function session_manager(){
	if (!session_id()){
		session_start();
		}
	$_SESSION['email'] = $_POST['email'];
	}

Then calling it on the page with your form when the form is posted using add_action

include 'TEMPLATEPATH . /functions.php';
add_action('init', 'session_manager');
.. update user meta etc ... with user inputed data etc ...

This was from a post here in the forums from 2 years ago regarding a seperate issue with sessions.

I think I was heading down the wrong route with looking at a modified plugin of extra_user_details ( i thought maybe serializing the data/unserializing may have had something to do with it but i think I am offbase with that thinking.) … I did find a topic below that seems to deal with similar headache’s with sessions and WP … maybe it will help.

Hey Red, I’ve got one site that currently uses custom user meta, Im looking through that code to see what I did to navigate this situation and Ill post back … Hopefully we’ll find a resolution.

Cheers

Does this happen when you explicitly call wp_rewrite globally?

//Ensure the $wp_rewrite global is loaded
global $wp_rewrite;
// rewrite
$wp_rewrite->author_base = 'atletes';
//regenerate the cache as a method of the $wp_rewrite object
$wp_rewrite->flush_rules();

WP Codex: <a href="https://codex.www.ads-software.com/Rewrite_API/flush_rules"></a>

Liek Dan said it is best to stay within the WP Db, however easiest way to do what you are wanting to do is to create a file called somthing like: db_connect.php (have all your connections to your DB here (ie. db_name, host, user, pass)

Then (if using a WordPress generated page to collect your users information, you will want to use a plugin like [include it] or create a custom template page based on your theme with your contact form inside of it and make your calls normally as if it were a standard PHP file.)

Something like this:

<? include db_connect.php;

// php / mysql to process collected data
if (isset($formSubmitted))
{
$name = $_POST['name']
$othervariables = $_POST['othervariables'];
$query = 'INSERT ..... $name, $othervariables';
$result = mysql_query($query);
}

// user contact form to collect data
echo 'your form stuff';
-- Note: make sure you write back to the same page by calling:
<form action='<?php echo htmlentities($_SERVER['REQUEST_URI']); ?>' method='POST' enctype='application/x-www-form-urlencoded'>
form submit / clear <inputs>
<input type='hidden' name'formSubmitted' value='Y'>
</form>

?>

Hope this helps.

Could you not write the new value to a SESSION variable and then pass it along that way?
(ie.

<?
session_start;
if (isset($_SESSION['oldEmail']))
{
// user submits form ... new email is written to a variable $newEmail
// do your update_user_meta etc updates to the DB ...
// I think session_register is deprecated now
// query the user table and get your newly updated email address for the ID of the user
// $resObj-> mysql_fetch_object the new email and register it in a temp session variable.

$_SESSION['newEmail'] = $resObj->user_meta_field_name;
$newEmail = $_SESSION['newEmail'];
$oldEmail = $_SESSION['oldEmail'];
$oldEmail = $newEmail;
}
?>
... carry on ...

Also sessions are specific to the web address in which you are submitting the data and the cookie ID needs to be set the same otherwise you are forced to carry the session over in the URL itself to the next the next location for evaluation: so if you are at https://yourplace.com and your post to https://www.youplace.com you will have problems. Keep the URL exact if it isnt that way already. (ie. <?php echo htmlentities($_SERVER['REQUEST_URI']); ?>)

This probably a little archaic, and not even certain it will work but just some initial thoughts.

Just wanted to follow up with this and thank you again. As of 4am last night I was finally able to get the entire site secure. A little bit of a headache and some of it cryptic, but its working! lol …

Still have some areas I dont understand though … One of my insecure calls was coming from a jquery.js?ver=x.x.x (in this case 1.8.3) .. Not sure where that came from as I use the 1.9.x library. Didn’t look like it was from a plugin but from WP itself. And I could only locate it in the “cache’d”) (<– I think that’s what these are (folders start with strange file names like: ar\__cat, de\__cat,ja\_ this goes all the way into the Zh\_) files within WP (Not sure if I can get rid of these, about 223 files like this all with this 1.8.3 call., and I could not find the offending register of the jquery library. (ie. wp_enqueue_script) … /shrug…

Anyhow I have manually gone through and changed all of those and loaded it up one more time before going to bed and got all “green” locks across 4 different browsers. (Talk about smiling …) lol .. Anyhow I just wanted to say thank you again for replying back … Really helped me step away from the code for a minute and look over everything again.

Peace!

(FYI: Just a side note: I was able to get this site SSL compliant without the use of WP HTTPS and using Network Solutions Shared SSL. (I know folks have had issues with these guys: but it does work!))

Thank you very much for you reply. Most (I’d say 80%) of the images, CSS and JS files were uploaded into WP prior to going SSL. (I will start a new side sandbox with a fresh install of WP and start SSL … perhaps then a migration of the old site in this new one?

I had looked into modifying my htaccess file, but when I did, I would get the message: Too many redirects. I checked memory and upped to 80mb. But with the same result. My current htaccess:

# BEGIN WordPress
RewriteCond %{SERVER_PORT} !=443
RewriteRule .* https://%{HTTP_HOST}/$1 [R=301,L]
# END WordPress

I was forcing SSL on Admin and Login, but the Admin pages would display as insecure. (Although in general settings I am set to https:)

I noticed the plugins causing some breaks, and I am looking to find the code that is offending …

Thanks so much for your reply. I think I should find a solution one way or the other with your suggestions =).

Much appreciated. Sometimes you are just staring at it too long and not able to see some of the potential problem areas to perhaps consider. Thanks again!

Ok I was able to correct the Unsecured Links section. This was an oversight on my part as I was logged in as the admin, and the admin bar was causing the reference to the invalid links.

I am still trying to figure out the “Unsecured Images” and “Unsecured CSS/Scripts/Style Sheets” areas to modify or adjust.

Unsecured Images:
<img src="https://www...../wp-content/uploads/2013/01/100bill-150x145.jpg" >
<img src="https://www...../wp-content/uploads/2013/01/ameraqLion.png" >
<img src="https://www...../wp-content/uploads/2013/01/chromeSSLdisplayissues-300x143.png" >
<img src="https://1.gravatar.com/avatar/b8e81a516c52afb49a779dc485e86542?s=16&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D16&r=PG" >
<img src="https://1.gravatar.com/avatar/b8e81a516c52afb49a779dc485e86542?s=64&d=http%3A%2F%2F1.gravatar.com%2Favatar%2Fad516503a11cd5ca435acc9bb6523536%3Fs%3D64&r=PG" >

Unsecured CSS/Scripts/Style Sheets:
<link href="https://www...../wp-content/themes/whitehouse/css/960.css" >
<link href="https://www...../wp-content/themes/whitehouse/css/reset.css" >
<link href="https://www...../wp-content/themes/whitehouse/css/trans.css" >
<link href="https://www...../wp-content/themes/whitehouse/css/wp.css" >
<link href="https://www...../wp-content/themes/whitehouse/style.css" >
<link id="upm_polls.css-css" href="https://www...../wp-content/plugins/upm-polls/css/polls.css?ver=3.5" >
<link id="admin-bar-css" href="https://www...../wp-includes/css/admin-bar.min.css?ver=3.5" >
<link id="contact-form-7-css" href="https://www...../wp-content/plugins/contact-form-7/https://www...../wp-content/plugins/contact-form-7/includes/css/styles.css?ver=3.3.2" >
<script src="https://www...../wp-content/plugins/upm-polls/js/jquery-1.4.2.min.js?ver=3.5" >
<script src="https://www...../wp-includes/js/jquery/jquery.js?ver=1.8.3" >
<div id="upm_loading" background="rgba(0, 0, 0, 0) url(https://www...../wp-content/plugins/upm-polls/img/loading.gif) no-repeat scroll 50% 50% / auto padding-box border-box" background-image="url(https://www...../wp-content/plugins/upm-polls/img/loading.gif)" >
<script src="https://www...../wp-includes/js/admin-bar.min.js?ver=3.5" >
<script src="https://www...../wp-content/plugins/contact-form-7/https://www...../wp-content/plugins/contact-form-7/includes/js/jquery.form.min.js?ver=3.23" >
<script src="https://www...../wp-content/plugins/contact-form-7/includes/js/scripts.js?ver=3.3.2" >