Passing parameters into another template
Posted
#4938
(In Topic #996)
I was able to add a CPF for it in the catalogue, but now I just need to figure out how to pass {FIELD_10} (contains either monthly, quarterly, or annually) into the below templates:
RESULTS_cart_TABLE (to show the user before clicking 'checkout')
ECOM_CART_BUTTON_VIA_PAYPAL to let PayPal know the duration
I've noticed the price of an item is stored as {FIELD_2} and somewhere along the line it gets passed into {PRICE} for use on the above listed templates.
If it's not possible, I could sell the item as a usergroup subscription to accomplish the recurring payment, but it just complicates things more because I have to create faux secondary usergroups for each product I choose to sell (which in return would get messy if I have 10+ items selling)
Posted
Moderator
The eCommerce system is fully extendible to programmers with new subscription projects, and that is documented, but it's definitely not something you should try and achieve at the template level. There is a lot of plumbing behind the eCommerce templates to make it work. If those templates are to be used in any meaningful way, the product being purchased would need to be compatible also with all the assumptions in that plumbing. For example, any IPN coming through for a purchased shopping cart project would not be expected to have a subscription term defined for it, and thus that purchase would fail with a hack-attack alert, unless a new eCommerce product hook was custom coded up for it.
1 guest and 0 members have recently viewed this.