Forums / PayPal Express Checkout support / Debug Logging - PayPal

Debug Logging - PayPal

Sticky Locked

Views: 36,909

Results 1 to 1 of 1
This thread is locked. New replies are disabled.
20 Mar 2007, 3:48 AM
#1
drbyte avatar

drbyte

Sensei

Join Date:
Jan 2004
Posts:
63,515
Plugin Contributions:
176

Debug Logging - PayPal

*** PLEASE NOTE: this content is now available on the documentation site at https://docs.zen-cart.com/user/troubleshooting/paypal_debug_logging/

You can enable debug logging of PayPal transaction activity.

The debug logs do NOT contain your PayPal password or API certificate information. This sensitive information is masked so that it cannot be stolen and used unscrupulously.
Further, in the default configuration, there are protections in place to prevent snoops from finding and obtaining your log files, as they are named with some degree of randomness, making it virtually impossible to guess.

  1. Ensure you are using Zen Cart v1.3.7 or newer, and any published PayPal patches are installed.

  2. Go to Admin->Modules->Payment ... and choose your PayPal module (either Standard/IPN or Express Checkout, Payments Pro, etc). Click Edit.

  3. Choose "Log to File" for your debug option. (recommend to** NOT** use log-to-email option, because the emails are harder to isolate.)

  4. Use your FTP program to mark the /includes/modules/payment/paypal/logs folder writable (ie: chmod 777). If given a "recursive" option, select "no". If asked about altering files "and" folders, say "no".

NOTE: As of Zen Cart v1.5.1 and newer, the folder is now /logs/

  1. do some test transactions to simulate the problems you're encountering or reporting.

  2. Once you've duplicated a problem with logging enabled, grab the log files related to that transaction (ie: look at the date/time on the files) and download and zip them for analysis ... ie: you may be asked to provide a link to where the zip file can be downloaded from when talking to DrByte, Ajeh, Kim or wilt. You might alternatively post the link directly in the support thread where you're discussing a reported problem.

**UNDERSTANDING THE LOG FILES
**With Express Checkout and Payments Pro, there are several kinds of log files created:
- PayPal_CURL_xxxxxxxxxxx.log -- there are 3 of these per EC transaction: SetExpressCheckout, GetExpressCheckoutDetails, DoExpressCheckout, or 1 for a Payments Pro transaction.
- paypalwpp_xxxxxxxx.log - there are up to 5 of these per EC transaction, showing individual checkpoints. This is useful in seeing what's going on vs where things are aborting, if at all
- paypaldp_xxxxxxxx.log - there are up to 5 of these per Pro transaction, also showing activity at various checkpoints.

In addition, for all modules (Standard/Express/Pro), there will be another log file created:
- ipn_xxxxxxx.log -- This tracks the steps when an IPN is received ... which happens for all activity in your PayPal account. Zen Cart knows which ones to "use" and which to "ignore".
The "Standard" module relies on this step to insert orders into your store. If that step doesn't happen or aborts prematurely, then the order won't show. Thus it's better to use Express Checkout, instead of Standard, for your payments.
- pdt_xxxxxx.log - this sort of log file might appear if the Standard module is being used and a PDT token has been set.

**
LOG LOCATION**

Remember, the logs can be found in the following folder:
a) for Zen Cart v1.5.1 or newer: /logs/
b) for Zen Cart v1.5.0 or v1.3.9h or older: /includes/modules/payment/paypal/logs/

.
Zen Cart - putting the dream of business ownership within reach of anyone!
Donate to: DrByte directly or to the Zen Cart team as a whole

Remember: Any code suggestions you see here are merely suggestions. You assume full responsibility for your use of any such suggestions, including any impact ANY alterations you make to your site may have on your PCI compliance.
Furthermore, any advice you see here about PCI matters is merely an opinion, and should not be relied upon as "official". Official PCI information should be obtained from the PCI Security Council directly or from one of their authorized Assessors.