if I have three levels of listing, each at a different price, what is the variable I can use in templates to show the prices?
For example, If I am writing a bot at the top of the suggest page that explains the price structure, I need a variable I can use for each listing type to display the price, so that when I adjust the prices I don't have to edit all of my templates.
We used to have such a variable, now we don't seem to have it.
The default 'submit listing' template uses this code:
<ul> <!-- BEGIN SPONSORED LIST --> <li>{TYPENAME} costs {LANG_GENERAL_CURRENCY}{PRICE} for {DURATION} days.</li> <!-- END SPONSORED LIST --> </ul>
I'm not sure if you can use it more than once in the same template though -- let me know if it doesn't work the second time.
The old version where you used {SPONSORPRICE[levelid]} didn't make much sense because the level id wasn't obvious and was subject to change. For more flexibility though I'll make the $sponsordata object functions available to templates, this means you can use {SPONSORDATAGETCHARGEBYTYPE[type name here]} in 6.1.9 Beta 6.
0/5
1
2
3
4
5
Sorry, you don't have permission to post posts. Log in, or register if you haven't yet.
Comments on Sponsor Price Variables
Forum Regular
Usergroup: Customer
Joined: Nov 27, 2006
Total Topics: 187
Total Comments: 465
if I have three levels of listing, each at a different price, what is the variable I can use in templates to show the prices?
For example, If I am writing a bot at the top of the suggest page that explains the price structure, I need a variable I can use for each listing type to display the price, so that when I adjust the prices I don't have to edit all of my templates.
We used to have such a variable, now we don't seem to have it.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
The default 'submit listing' template uses this code:
I'm not sure if you can use it more than once in the same template though -- let me know if it doesn't work the second time.
The old version where you used {SPONSORPRICE[levelid]} didn't make much sense because the level id wasn't obvious and was subject to change. For more flexibility though I'll make the $sponsordata object functions available to templates, this means you can use {SPONSORDATAGETCHARGEBYTYPE[type name here]} in 6.1.9 Beta 6.