v151 Using UTP Payment module

[lat9]

That log file contains no errors, just a bunch of PHP Notices, but the Notices are strange. Many items that should be set aren't.

Which version of "Capture Type" do you have configured?

[lat9]

Is your site running with ENABLE_SSL set to 'true'?

[HammurIT]

Hi

Bit new to Zen Cart, what is "capture type"?

As to the running with ENABLE_SSL set to 'true', yes it is.

[lat9]

Hi

Bit new to Zen Cart, what is "capture type"?

As to the running with ENABLE_SSL set to 'true', yes it is.

Within the UTP module's configuration (Modules->Payment admin screen), there's a setting that is either Direct or Hosted.

[HammurIT]

Within the UTP module's configuration (Modules->Payment admin screen), there's a setting that is either Direct or Hosted.

Hi, that setting is hosted.

[lat9]

Have you verified your Merchant ID and Signature values against the values in your mms?

[HammurIT]

yes, we can get onto the payment form with no issue. Its just the coming back from a successful payment that the issue is with.

[lat9]

I ran a test transaction using the credentials you PM'd. There's a database-related issue (WARNING: An Error occurred, please refresh the page and try again.) that occurs on the re-entry to the checkout_process page.

[HammurIT]

Issue resolved. Many thanks for your help.

When I looked at the database directly the table was names zen_utp. The code used to create was CREATE TABLE IF NOT EXISTS `utp` and the creation was run via the install sql patch option in zen cart. So this must have named the table "zen_utp". I dropped this table, and then created the table directly in the database and it all worked.

[mc12345678]

Issue resolved. Many thanks for your help.

When I looked at the database directly the table was names zen_utp. The code used to create was CREATE TABLE IF NOT EXISTS `utp` and the creation was run via the install sql patch option in zen cart. So this must have named the table "zen_utp". I dropped this table, and then created the table directly in the database and it all worked.

Glad to see that it has been resolved!

That's an indication that the program (installation?) does not support DB_PREFIX which technically could be easily fixed, but unfortunately the plugin needs revision...

Two ways it looks to resolve in includes/modules/payment/utp.php:
Consideration 1) the preferred way is to have a define for TABLE_UTP such that it is defined as DB_PREFIX . 'utp'

define('TABLE_UTP', DB_PREFIX . 'utp');

and that would basically be substituted as follows:

TABLE_UTP

would replace

DB_PREFIX . 'utp'

TABLE_UTP . "

would replace

DB_PREFIX . "utp

the define might work in the __contstruct() function possibly as:

if (!defined('TABLE_UTP')) {
define('TABLE_UTP', DB_PREFIX . 'utp');
}

but it is more consistent to place a file in each of the includes/extra_datafiles and admin/includes/extra_datafiles to provide the definition without the if statement...

Consideration 2) modify the following line:

zen_db_perform('utp', $form_response_array);

to be:

zen_db_perform(DB_PREFIX . 'utp', $form_response_array);

and in the function admin_notification:

$sql = "SELECT * FROM utp WHERE zen_order_id = '$zf_order_id'";

Change to:

$sql = "SELECT * FROM " . DB_PREFIX . "utp WHERE zen_order_id = '$zf_order_id'";

in functions _doCapt and _doRefund:

$transaction_info = $db->Execute("SELECT * FROM utp WHERE zen_order_id = '$oID'");

to:

$transaction_info = $db->Execute("SELECT * FROM " . DB_PREFIX . "utp WHERE zen_order_id = '$oID'");