Optional Shipping Insurance Module [Support Thread]

aldo.campione ... out of curiosity, what shipping module(s) are you using?

It has been some years i last checked this module, but if i remember correctly the optional in this module is that you set the insurance to kick in above a certain total price in your cart.

Does anyone know how I might fix this so it will work with the
edit_orders-4
module.

My insurance adds correctly in the regular order total during check-out, but whenever you edit the order using the Edit Orders 4 interface, the new order total always leaves out the Shipping Insurance amount.

???

Andy

@Andy_M - Did you ever find a solution to this? I am having the same problem with Edit Orders 4.1.4

Andy_M:

Does anyone know how I might fix this so it will work with the
edit_orders-4
module.

My insurance adds correctly in the regular order total during check-out, but whenever you edit the order using the Edit Orders 4 interface, the new order total always leaves out the Shipping Insurance amount.

???

Andy

jackie.taferner:

@Andy_M - Did you ever find a solution to this? I am having the same problem with Edit Orders 4.1.4
Assuming that you both are discussing the plugin that's downloaded from the Plugins' area, it's relying on checkout-based session information to determine whether it's to be enabled and will require modification to work with EO 4.1.4 (since the admin environment contains no such session information).

Thanks @lat9, yes I am trying to get this working on a client's site as we speak. Are there any plans to upgrade this module to not use session-based information on the backend? Or any pointers on how to accomplish this upgrade?

Ok, for anyone else looking to fix up this module for Edit Orders v4.1.4, here's a bit of a workaround, but it seems to get the job done.

YOURADMIN/edit_orders.php

Right around line 430:

			foreach($_POST['update_total'] as $order_total) {
				$order_total['text'] = $currencies->format($order_total['value'], true, $order->info['currency'], $order->info['currency_value']);
				$order_total['sort_order'] = $GLOBALS[$order_total['code']]->sort_order;

				// TODO Special processing for some modules
				if(zen_not_null($order_total['title']) && $order_total['title'] != ':') {
					switch($order_total['code']) {
						case 'ot_shipping':
							$GLOBALS['order']->info['shipping_cost'] = $order_total['value'];
							$GLOBALS['order']->info['shipping_module_code'] = $order_total['shipping_module'];
							break;

Add this code:

			//unset the insurance session before loading the next order
			$_SESSION['opt_insurance'] = false;
			foreach($_POST['update_total'] as $order_total) {
				$order_total['text'] = $currencies->format($order_total['value'], true, $order->info['currency'], $order->info['currency_value']);
				$order_total['sort_order'] = $GLOBALS[$order_total['code']]->sort_order;

				// TODO Special processing for some modules
				if(zen_not_null($order_total['title']) && $order_total['title'] != ':') {
					switch($order_total['code']) {
						//add insurance session if order has insurance
						case 'ot_insurance':
							$_SESSION['opt_insurance'] = true;
							break;
						case 'ot_shipping':
							$GLOBALS['order']->info['shipping_cost'] = $order_total['value'];
							$GLOBALS['order']->info['shipping_module_code'] = $order_total['shipping_module'];
							break;

I have a question I've upgraded my Zen Cart installation from 1.5.5e to 1.5.5f in my development server, as well as upgrading from PHP 5.6 to PHP 7.1.
I've made sure my customization php.ini definitions are migrated too.

Going through QC testing I've noticed ot_insurance no longer functions properly.
First symptom is upon a user attempts to checkout and pay for the product on index.php?main_page=checkout_payment , the screen returns blank.
Second symptom is the edit Edit and Remove buttons within the administration page of the module does not show up anymore. The module list is of course still green light. I can click on the module listing again to edit the attribute of the module that way.

According to the debug log, there's evident that something isnt compatible with the module.
[18-Jan-2018 20:08:08 America/Los_Angeles] PHP Fatal error: Uncaught Error: Call to undefined function split() in /home/www/includes/modules/order_total/ot_insurance.php:128
Stack trace:
#0 /home/www/includes/classes/order_total.php(185): ot_insurance->process()
#1 /home/www/includes/modules/pages/checkout_payment/header_php.php(101): order_total->pre_confirmation_check()
#2 /home/www/index.php(36): require('/home/apusa/ang...')
#3 {main}
thrown in /home/www/includes/modules/order_total/ot_insurance.php on line 128

Disabling, but not Removing (Since I cant do that without the button) the module will make my shopping cart work again.

Also ZC 1.5.5e and 1.5.5f works with Php 5.6 but this issue appears within Php 7.1 So far, I have no other issues with other modules, and general functionality of the cart except this module. As I'd like to force my customers to have insurance for every order.
Now, I think there's a work around using the USPS shipping insurance check box, and not using this module at all. But that is a bad work around as it does not show the customer that they are being charged for the extra service.

Any help would be greatly appreciated!

The PHP ***split ***function was deprecated (i.e. letting you know that it' going to be removed) in PHP 5.3.0 and removed totally in PHP 7.0. That's why the ot_insurance worked under PHP 5.6 but not under PHP 7.0.

If you would post the contents of /includes/modules/order_total/ot_insurance.php's function on/around line 128, perhaps someone could propose a code-change to allow that order-total to (again) operate.

lat9:

The PHP ***split ***function was deprecated (i.e. letting you know that it' going to be removed) in PHP 5.3.0 and removed totally in PHP 7.0. That's why the ot_insurance worked under PHP 5.6 but not under PHP 7.0.

If you would post the contents of /includes/modules/order_total/ot_insurance.php's function on/around line 128, perhaps someone could propose a code-change to allow that order-total to (again) operate.

Okay that sounds logical enough.
This is the latest version from both Numinix's website and the one uploaded in the ZC Plugins page. Version number is 3.2.2
I look the liberty checking if there other occurrence of the split and I have found two. Here they are:

Starts at Line 125
// usps still open
$table = constant('MODULE_ORDER_TOTAL_INSURANCE_COST_' . $this->dest_zone);
$table_cost = split("[:,]", $table);
$size = sizeof($table_cost);
for ($i=0, $n=$size; $i<$n; $i+=2) {
if (round($order_total_insurance,9) <= $table_cost[$i]) {
$insurance = $table_cost[$i+1];
break;
Ends at Line 132

Starts at Line 219
if (MODULE_ORDER_TOTAL_INSURANCE_TABLE == 'true') {
$table = constant('MODULE_ORDER_TOTAL_INSURANCE_COST_' . $this->dest_zone);
$table_cost = split("[:,]", $table);
$size = sizeof($table_cost);
for ($i=0, $n=$size; $i<$n; $i+=2) {
if (round($order_total_insurance,9) <= $table_cost[$i]) {
$insurance = $table_cost[$i+1];
break;
}
Ends at 227

Yes split has now changed to preg_split. For those changes:

change to:

$table_cost = preg_split("/[:,]/", $table);

AND it appears to work! Version zc 1.5.5f and Php 7.1

Oddly enough, this module never had a Edit and Remove button apparently to start with.
I guess I'll repackage it for the site repository since everyone is supposed to migrate to 7.x anyways, as 5.6 will be EOL this coming December.

Thank you for the quick fix!

tmccaff:

Yes split has now changed to preg_split. For those changes:

change to:

$table_cost = preg_split("/[:,]/", $table);

Another odd artifact that I've noticed now that the module worked with the above modification.
I have noticed now the built-in store pickup module cannot bypass insurance enforcement. It's annoying my customers, but I can sort of get around it by refunding the insurance amount upon pickup.
Anyone else having the same issue? And any advice on how to diagnose and perhaps find out how to actually get this mod somewhat up to date?

chibipaw:

Another odd artifact that I've noticed now that the module worked with the above modification.
I have noticed now the built-in store pickup module cannot bypass insurance enforcement. It's annoying my customers, but I can sort of get around it by refunding the insurance amount upon pickup.
Anyone else having the same issue? And any advice on how to diagnose and perhaps find out how to actually get this mod somewhat up to date?
A new version, 3.3.0, has been released on our website. At the top of the file there is a check for storepickup. Can you confirm if that resolves your issue chibipaw?

numinix:

A new version, 3.3.0, has been released on our website. At the top of the file there is a check for storepickup. Can you confirm if that resolves your issue chibipaw?

Woo hoo! And here I thought its abandoned. Alright going to start testing out the dev server tonight, and I'll let you know once I get some concrete results.
Thanks for the update ! in both the information and the new version!

numinix:

A new version, 3.3.0, has been released on our website. At the top of the file there is a check for storepickup. Can you confirm if that resolves your issue chibipaw?

Alright, I've installed 3.3.0 into my dev environment and this is what I have discovered so far:

If there is previous version of ot_insurance installed, one must manually delete the values MODULE_ORDER_TOTAL_INSURANCE_* under the configuration_key in the configuration table before proceeding. Otherwise this module will display a +install button in the admin menu and then fail to install these values. Probably will need an uninstall SQL script of some sort.

Once installed, this module does not appear to know it has been installed. So the +install will return to the admin menu, and edit of the module's configuration_value's is not possible without directly manipulating the database directly. With that said, the -remove button will not appear, uninstall is not possible without deleting the above keys from the table mentioned above. This is of course going to be problematic.

If using a permitted zone address was used to check out using the Store Pickup option, no insurance was charged.
But here comes to show stopper. Checkouts using the normal delivery method (USPS), does not trigger ot_insurance to charge a fee either.

chibipaw:

Alright, I've installed 3.3.0 into my dev environment and this is what I have discovered so far:

If there is previous version of ot_insurance installed, one must manually delete the values MODULE_ORDER_TOTAL_INSURANCE_* under the configuration_key in the configuration table before proceeding. Otherwise this module will display a +install button in the admin menu and then fail to install these values. Probably will need an uninstall SQL script of some sort.

Once installed, this module does not appear to know it has been installed. So the +install will return to the admin menu, and edit of the module's configuration_value's is not possible without directly manipulating the database directly. With that said, the -remove button will not appear, uninstall is not possible without deleting the above keys from the table mentioned above. This is of course going to be problematic.

If using a permitted zone address was used to check out using the Store Pickup option, no insurance was charged.
But here comes to show stopper. Checkouts using the normal delivery method (USPS), does not trigger ot_insurance to charge a fee either.

The module needs to be uninstalled before uploading the new files and reinstalling. However, any future versions after 3.3.0 will auto upgrade.

numinix:

The module needs to be uninstalled before uploading the new files and reinstalling. However, any future versions after 3.3.0 will auto upgrade.

Do you know whats the procedures to cleanly uninstalling the module? perhaps manually?
v3.23 do not have the Remove button to uninstalling in the menu, as indicated in the documentation.
The best I know of is deleting the the SQL entries above and over writing the two files.

The closest thing I can see is after clicking on the module is the first option, which it's a True False button with the following dialog:
"Do you want to enable this module? To fully turn this off, both this option and the one below should be set to false."

Thanks.

Ryk:

For anyone else looking to do this, this answer was provided by the module author:

Now, having made it mandatory, the next requirement is to exclude it completely from the Store Pickup option! This would probably take a proficient php coder a matter of minutes...but I'm not, and I'm starting now! :D (So any suggestions are welcome!)

Thanks for the wonderful module to add shipping insurance.

I have two types of shipping options on my website:

1. expedited shipping
2. regular mail

Now, I need to add mandatory shipping insurance to the Regular mail shipping only. I do not want the shipping insurance to show with Expedited shipping option.

Kindly let me know how an this be made possible.

Thanks in advance.
muteyaar

chibipaw:

Alright, I've installed 3.3.0 into my dev environment and this is what I have discovered so far:

Once installed, this module does not appear to know it has been installed. So the +install will return to the admin menu, and edit of the module's configuration_value's is not possible without directly manipulating the database directly. With that said, the -remove button will not appear, uninstall is not possible without deleting the above keys from the table mentioned above. This is of course going to be problematic.I have this same problem. Did you find a solution?