richtelford

I downgraded the plugin to 0.1.6.8. This solved the problem. For some reason the participating bank (3d secure) iframe isn’t being rendered in the latest version of the plugin. I am running WooCommerce 2.0.12

I’m getting a similar problem where I fill in the details on the checkout screen, submit the order. The little ajax spinner spins round to indicate some action but then instead of loading up the 3D secure bank iframe where normally I would enter my 3D secure password, it redirects me to the following URL (or similar):

https://www.gildapearl.co.uk/checkout/pay/?order_id=4121&order=order_5396c865ce159&pay_for_order=true

I’m not aware of anything that’s been changed on the site apart from maybe upgrading WordPress core and possibly your plugin. I’ll conduct some further debugging to try and figure out what is happening.

Yes that’s correct. I replaced that section from 91 down with:

//Force Theme Display request from visitor.
if (@$_GET['am_force_theme_layout']){
	//$_COOKIE['am_force_theme_layout'] 	=	$_GET['am_force_theme_layout'];
	setcookie("am_force_theme_layout", $_GET['am_force_theme_layout']);
	header("Location: /");
	exit;
}

if (isset($_COOKIE['am_force_theme_layout'])){ //IF USER FORCE FOR THE THEME
	if ($_COOKIE['am_force_theme_layout'] == 'mobile'){ // IF FORCED THEME IS MOBILE
		$mobile_browser = get_option('iphone_theme');
		add_filter('stylesheet', 'loadMobileStyle');
		add_filter('template', 'loadMobileTheme');
		$shown_theme = 'mobile';
	}
} else { // NORMAL THEME [PLUGIN DEFAULT]
	if (!empty($mobile_browser)){
		add_filter('stylesheet', 'loadMobileStyle');
		add_filter('template', 'loadMobileTheme');
		$shown_theme = 'mobile';
	}
}

I made a few modifications to my local version of the plugin. The main change I made was to use $_COOKIE instead of $_SESSION to store user choice. It works very well.

In the aioseop_functions.php file.

Sorry I’ve just realised that you probably shouldn’t have uppercase in register taxonomy anyway. I was bugshooting something which should never happen. Perhaps WordPress should tell you when an invalid taxonomy name at registration?