View Full Version : voucher codes
Hello
How do you go about enabling the new voucher code part of V3? On the product_display_list.tpl and the product_display.tpl theres {$oProduct->sPromotion}, however this isnt displaying voucher codes. Say you search Currys products, {$oProduct->sPromotion} displays numbers like:
LE40B750U1WXXU for a SAMSUNG LE40B750 £999.00 when the code should be CODE15
VBA230KU01 for a NIKON D9018-105 D/SLR £799.00 when the code should be CODE15
Comet isnt displaying any promotions when theres like 22 voucher codes.
Getting fedup with me yet :rolleyes:
Nole
ljackson09
18-08-09, 02:44
i'd like to know the answer to this also :)
Hey guys,
Glad to see you have spotted that one. Unfortunately this is not functionality provided by 'default' installs. It requires a small amount of extra development work to get these extras installed.
Probably worth noting, voucher codes are not down to product levels at the moment but merely on merchant/category levels. This functionality will hopefully be introduced in the future.
Cheers
Hey guys,
Glad to see you have spotted that one. Unfortunately this is not functionality provided by 'default' installs. It requires a small amount of extra development work to get these extras installed.
Probably worth noting, voucher codes are not down to product levels at the moment but merely on merchant/category levels. This functionality will hopefully be introduced in the future.
Cheers
Any chance you are going to actually share with us what this extra development work is? Is it something that could be done from user level and if so how? Or is it something else that we are missing out on and why is it not completed now, surely your not actually seriously expecting people to redo their custom shops from scratch again for a V4, just because stuff like this has not been added properly into this version which we've been waiting patiently for for months and months as it is?
Any chance you are going to actually share with us what this extra development work is? Is it something that could be done from user level and if so how? Or is it something else that we are missing out on and why is it not completed now, surely your not actually seriously expecting people to redo their custom shops from scratch again for a V4, just because stuff like this has not been added properly into this version which we've been waiting patiently for for months and months as it is?
Hey Amoochi,
I appreciate what you are saying but unfortunately many do not agree. The ShopWindow team provides a basic vanilla client to get affiliates started. We expect a certain level of customisation from affiliates to set their shops apart from other users. As a result, there are parts of the ShopWindow platform that are not included in the default client. This has always been the case and always will be the case.
We want to allow affiliates to innovate and provide new and exciting sites which help enhance web and user experiences all over rather than replicate existing sties that adversely affect all affiliates which in the end reduce commissions for everyone.
To point out, the upgrade from V2 to V3 was kept very simple. You should not have to redo an entire shop from scratch. Only major upgrades are actually required to get your old installs working and there are very few of these (user auth and caching). The upgrade from V1 to V2 was inevitable as the changes were so major (as with many initial BETA versions). But we now aim to introduce backwards compatibility where possible. Which is why we provide both classes and elements directory's. The classes directory generally does not need editing and updates can just be written over to ensure sites work when new versions are released.
Hey Amoochi,
I appreciate what you are saying but unfortunately many do not agree. The ShopWindow team provides a basic vanilla client to get affiliates started. We expect a certain level of customisation from affiliates to set their shops apart from other users. As a result, there are parts of the ShopWindow platform that are not included in the default client. This has always been the case and always will be the case.
We want to allow affiliates to innovate and provide new and exciting sites which help enhance web and user experiences all over rather than replicate existing sties that adversely affect all affiliates which in the end reduce commissions for everyone.
To point out, the upgrade from V2 to V3 was kept very simple. You should not have to redo an entire shop from scratch. Only major upgrades are actually required to get your old installs working and there are very few of these (user auth and caching). The upgrade from V1 to V2 was inevitable as the changes were so major (as with many initial BETA versions). But we now aim to introduce backwards compatibility where possible. Which is why we provide both classes and elements directory's. The classes directory generally does not need editing and updates can just be written over to ensure sites work when new versions are released.
Your kinda defeating yourself with what your saying there, but i'll let you work that out for yourself.
It would appear that there's a pattern emerging here... :rolleyes:
I mean c'mon, what's the point of trying to customise something, if the code isn't even complete in the first place??? What else doesn't work, that we only find out about when someone spots it and mentions it?
Hi
So are we saying, yes the data is there but we need to build the soap api calls and build them into our own installs.
Or
come clean now
No its not something we have finished
?
$oProduct->sPromotion has always been there
Ok thanks
will keep looking learing etc, i have no probs trying to do things myself or paying for those who can.
I would call a V.code a promotion, think 15% off whatever is a promtion.
Nole
$oProduct->sPromotion has always been there.. yeah but wasnt it mostly empty and wouldnt it be prefect for the code.
Hi
So are we saying, yes the data is there but we need to build the soap api calls and build them into our own installs.
Or
come clean now
No its not something we have finished
?
Before I get into the code, I'd like to know the answer to this too. Can you confirm there is voucher code data available to Community users?
So are we saying, yes the data is there but we need to build the soap api calls and build them into our own installs.
Option A.
The functionality is provided in the API if anyone wants to use it. The vanilla client is just that - Vanilla. It does not by any means have all the bells and whistles and never unfortunately will.
We provide it as a framework to help affiliates modify and build upon to build something great and awe inspiring.
EDIT: Yes, this is available to community version users too!
ok thanks for info Ollie
nole
First good news I've heard all day ;)
Thanks Ollie.