The Official Website of AgoraCart and Agora.cgi Demos Download AgoraCart User Manuals & Wiki Gold Members Forum Go Gold Now! Gold Version Memberships

Payment Gateways
Send a Donation
Founders Club
BLOG: News & Updates

Showcases & Demos

AgoraCart Demos
Shop Live Stores

Downloads & Add-ons

Gold Version Downloads
DBwizz Database Mgr. Store

Help & Support

User Manuals
Gold Version Users Forum
Gold Version Chat
Tech Support
Certified Agora Pros
Certified Designers
Hire a Freelancer

Gold Version Members

Member Benefits
Join Today!
Gold Members Home
Gold Version Users Forum
Gold Version Chat Rooms
Gold Version Downloads

For Store Owners

Merchant Accounts
Cool Resources
Advertise Here
"Powered by" Logos
Web Hosting Search


Contact Us
MEET's Talking Guide
The Ancient Greek Agora

AgoraCart Free User Forums

This is the official FAQ and Cool Tips guide For the AgoraCart shopping Cart software

Official Sponsors of the AgoraCart Project:


RegisterSearchFAQLog in
Reply to topic Page 1 of 1
Repeated option descriptions
Author Message
Reply with quote
Post Repeated option descriptions 
I'm using Plug-n-Pay as part of a multiple-gateway setup. I have it set to provide the entire list of purchased items (instead of a lump sum). (I added some code to calculate discounts from coupons, which is included as an item with negative value, but I don't think this is relevant to my problem.)

When Plug-n-Pay displays my item list, it displays only the last option value for all items. That is to say: if a customer orders multiple items with options, all items are displayed with the last item's option value. Even items that have no options. If an item with no options is the last item, no items will include option descriptions.

I see that the process_PlugnPay_Order and pnp_table_setup functions both set the value of $options, and the value of $options is used in print_PlugnPay_SubmitPage, appended to each item description.

Items with multiple options are even hairier.

It looks to me like the code in pnp_table_setup (I think?) needs to be modified so the options can be associated with individual items. (Perhaps a hash table?) On the other hand, the description code in print_PlugnPay_SubmitPage might need to be modified to read options directly out of the cart. (It reads the cart, after all.) I'd take this on myself, but I have no idea what the cart data looks like.

Anybody know what's going on?

View user's profile Send private message Visit poster's website
Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum