Contractually we have several products that we are looking to designate as "Call for Pricing" on our storefront. I know there are various ways of performing this, was looking for a mod to perform the function of replacing the PRICE field with text"Call for Pricing". Is there an easy way of doing this ? Anybody doing ? Any information would be much appreciated ? Thank you !!
Announcement
Collapse
No announcement yet.
Call for Pricing feature
Collapse
X
-
Perhaps the "easiest" way to do this would be to use a Product Custom Field and the combination of a 0.00 price. Something like:
Code:<mvt:if expr="l.settings:product:price EQ 0"> &mvt:product:customfield_values:customfields:You_Custom_Code; <mvt:else> The product price code here. </mvt:if>
Note: If you have other products that have a 0.00 price then some further thought will need to be put into this. That's why I suggested using a Product Custom Field. If this is the only time you might use 0.00 for the price, then you don't need to create a Product Custom Field. You can just insert your "Call for Pricing" message instead of the Product Custom Field.Leslie Kirk
Miva Certified Developer
Miva Merchant Specialist since 1997
Previously of Webs Your Way (aka Leslie Nord leslienord)
Email me: [email protected]
www.lesliekirk.com
Follow me: Twitter | Facebook | FourSquare | Pinterest | Flickr
-
A custom PROD page template is another way. Create another product page template, I'd start by copying and pasting the current one over then modifying it. Remove the order form and replace it with the messaging you need for "call for pricing".
The custom field method above is faster. No doubt about it!
But I can tell you from experience that sometimes it pays to have separate PROD templates. We have an awful lot of customizations using conditionals and custom fields and they get really messy and tricky the more you have.
Comment
-
Originally posted by Mark Stephens View PostA custom PROD page template is another way. Create another product page template, I'd start by copying and pasting the current one over then modifying it. Remove the order form and replace it with the messaging you need for "call for pricing".
The custom field method above is faster. No doubt about it!
But I can tell you from experience that sometimes it pays to have separate PROD templates. We have an awful lot of customizations using conditionals and custom fields and they get really messy and tricky the more you have.Leslie Kirk
Miva Certified Developer
Miva Merchant Specialist since 1997
Previously of Webs Your Way (aka Leslie Nord leslienord)
Email me: [email protected]
www.lesliekirk.com
Follow me: Twitter | Facebook | FourSquare | Pinterest | Flickr
Comment
-
Its definitely a balance thing. Back in the Product Display Manager days (3rd party modules) I saw many instances where people would use a new 'template' for AS the one conditional on the page. So, if a product template change was needed, you often had to update several to dozens of templates.
Clarity is probably a good barometer as, even if a change needs to be done on multiple templates, if you can clearly see the difference, than it might be worth the additional work.
But clarity can also be achieved in other ways:
1) Comment, comment, and comment on your comments...seriously. Every bit of code you change or add should have a comment...if only to say you've inserted it and can therefore find the difference between standard and customized templates. Typically, we tried to note: a) who is making the change. b) the RESULT desired. c) requirements, for example, 'l.settings:some_array:variable from some-other customization. i.e., <mvt:comment> accepts the difference from price/cost from g.myOwnVar:diffprice and displays it as percentage of savings -BWG</mvt:comment>
2) Formatting: Keeping the tab indentations consistent helps a lot in reading code:
Code:<mvt:if expr="l.settings:thisVar"> <p>Do this</p> <mvt:else> <p>Do something else</p> </mvt:if> <mvt:if expr="l.settings:somotherVar"> <p>Do this</p> <mvt:else> <p>Do something else</p> </mvt:if>
Code:<mvt:if expr="l.settings:thisVar"> <p>Do this</p> <mvt:else> <p>Do something else</p> </mvt:if> <mvt:if expr="l.settings:somotherVar"> <p>Do this</p> <mvt:else> <p>Do something else</p> </mvt:if>
Bruce Golub
Phosphor Media - "Your Success is our Business"
Improve Your Customer Service | Get MORE Customers | Edit CSS/Javascript/HTML Easily | Make Your Site Faster | Get Indexed by Google | Free Modules | Follow Us on Facebook
phosphormedia.com
Comment
-
Originally posted by Bruce - PhosphorMedia View Post
Comment, comment, and comment on your comments...seriously. Every bit of code you change or add should have a comment...
And also NEVER-NEVER-NEVER do anything like that:
Code:<mvt:if expr="l.settings:somotherVar"> <div> This is a test message <mvt:else> <div> This is a test message </mvt:if> </div>
Comment
-
my fav is:
Code:<mvt:if expr="l.settings:something"> Here's what we need to happen <mvt:else> </mvt:if>
Code:<mvt:if expr="'SomethingHere' CIN l.settings:thisVar"/>
Code:<mvt:if expr="somethinghere' IN tolower(l.settings:thisVar)"/>
Bruce Golub
Phosphor Media - "Your Success is our Business"
Improve Your Customer Service | Get MORE Customers | Edit CSS/Javascript/HTML Easily | Make Your Site Faster | Get Indexed by Google | Free Modules | Follow Us on Facebook
phosphormedia.com
Comment
Comment