Forums / Upgrading to 1.5.x / Upgraded from 1.3.8a to 1.5.1. Whew! Now a few issues...

Upgraded from 1.3.8a to 1.5.1. Whew! Now a few issues...

Started by pricediscrimination on 24 Jan 2013, 7:02 PM · Views: 2,615

Results 21 to 22 of 22
3 Feb 2013, 4:51 AM
#21
drbyte avatar

drbyte

Sensei

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

Upgraded from 1.3.8a to 1.5.1. Whew! Now a few issues...

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

8 Jun 2013, 7:13 AM
#22
pricediscrimination avatar

pricediscrimination

Zen Follower

Join Date:
May 2008
Posts:
401
Plugin Contributions:
0

Re: Upgraded from 1.3.8a to 1.5.1. Whew! Now a few issues...

pricediscrimination:

And PayPal Express isn't showing up on the shopping cart page yet a PayPal button is showing up in the checkout_payment page. Is this normal or did I probably screw something up in my shopping_cart_default when merging the files? I double checked and all seemed to be right. I always thought the PayPal in the checkout_payment was from one of the other PayPal modules, but I see I might have been wrong all this time since all I have installed at the moment is the PEC module.

Hey DrByte, just wanted to come an update this thread. After months of no express button on the shopping cart page, I decided to look into it again. After hours of forum searching and playing with the code switching back and forth between modified and unmodified files, it appears that for some reason the button was set to display none in the stylesheet! No idea why, but I suppose there was a good reason for it at some point. So after all that, it was working but not displaying. :shocking: