[Cloudrunner]

Originally Posted by insanekelso

getting an error when viewing ppverify.php

Warning: array_merge() [function.array-merge]: Argument #1 is not an array in /global.php on line 329

Warning: Invalid argument supplied for foreach() in /includes/functions.php on line 2290

any idea, this was after a reinstall. installed ok after a full uninstall.
First "real" donation created a mysql database error (which i forgot to not..doh!) and was held in the invalid transactions area, all values for this transaction where zero.

found error output:
Database error in vBulletin 3.0.7:

Invalid SQL: INSERT INTO donation_paypalipn (
`txn_id`, `userid`, `test_ipn`, `notify_version`, `verify_sign`,
`first_name`, `last_name`, `payer_business_name`, `address_name`,
`address_street`, `address_city`, `address_state`, `address_zip`,
`address_country`, `address_status`, `payer_email`, `payer_id`,
`payer_status`, `business`, `receiver_email`, `receiver_id`,
`item_name`, `ip_address`, `quantity`, `invoice`,
`memo`, `tax`, `option_name1`, `option_selection1`, `option_name2`,
`option_selection2`, `payment_date`, `parent_txn_id`, `txn_type`,
`payment_type`, `payment_status`, `pending_reason`, `reason_code`,
`mc_gross`, `mc_fee`, `mc_currency`, `mc_handling`, `mc_shipping`,
`settle_amount`, `settle_currency`, `exchange_rate`, `case_id`,
`case_type`, `case_creation_date`, `valid`
) VALUES (
'', '0', '0', '0', '',
'', '', '', '',
'', '', '', '',
'', '', '', '',
'', '', '', '',
'', '', '0', '',
'', '0', '', '', '',
'', '', '', '',
'', '', '', '',
'0', '0', '', '0', '0',
'0', '', '0', '',
'', '', '0'
);
mysql error: Duplicate entry '' for key 1

mysql error number: 1062

Date: Sunday 17th of July 2005 11:08:43 PM
Script: http://arpclan.gaming.multiplay.co.u...s/ppverify.php
Referer:

ppverify is not designed to be viewable from any browser. The only thing that will view ppverify without an error (as designed) is paypal's server.

As far as the DB error goes, you have a conflicting txn_id. You will need to remove the empty txn_id row. i.e. the row that contains the empty txn_id field. That field should NEVER be empty. Ever, if it is, then you will get a invalid marker and the system will give you notice of the invalidity of the transaction. This is an indicator of an attempt at compromising the system.

Clean out that specific transaction, and the system *should* again work. Lemme know what you come up with.