Forums / Bug Reports / [Done 1.3.6] PayPal bug when using zen_ functions in extra_definitions

[Done 1.3.6] PayPal bug when using zen_ functions in extra_definitions

Locked

Views: 1,849

Results 1 to 2 of 2
This thread is locked. New replies are disabled.
26 Sep 2006, 10:29 PM
#1
brandtim avatar

brandtim

Zen Follower

Join Date:
Apr 2006
Posts:
250
Plugin Contributions:
0

[Done 1.3.6] PayPal bug when using zen_ functions in extra_definitions

This one took me a while to find.

I was using the function zen_ez_pages_link in ez_pages_defintions.php (properly placed in a templates over-ride folder) to turn the ez_pages sidebox header into a link.

Orders were not making it through - presumably because that function was not being defined and so was throwing an error when being loaded as part of includes/modules/payment/paypal/ipn_application_top.php.

I wasn't able to come up with an easy fix other than to remove the offending function.

Tim

27 Sep 2006, 2:22 AM
#2
drbyte avatar

drbyte

Sensei

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

Re: [Done 1.3.6] PayPal bug when using zen_ functions in extra_definitions

Evidently the idea of using that function in the scope you are attempting wasn't considered previously.

To work around the limitation, you could do this:

In ipn_application_top.php around line 88 you have:// define general functions used application-wide require(DIR_WS_FUNCTIONS . 'functions_general.php'); require(DIR_WS_FUNCTIONS . 'html_output.php'); require(DIR_WS_FUNCTIONS . 'functions_email.php');simply add this on the next line below the call to functions_email:```
require(DIR_WS_FUNCTIONS . 'functions_ezpages.php');

.
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.