I'd really like to see an update on this matter too. I have great concerns over the future of Perch and the viability of using for clients sites, as a result of the almost total lack of communication from Perch HQ on such matters.
How do you change the precedence of product options?
That would make sense… cheers Drew (I think the community could do with a "where we're at" update re: version 4… )
Do products have to sold in whole numbers? or is it possible to purchase X.1, X.4 or X.7 of something… 2.5kg of nails?
Is it possible to create a minium quantity for a product variant and have that passed through to the cart when the product is added?
If a user is logged in and has a certain tag I'm automatically applying a discount, however if that user logs out the discount is still displaying is it possible to remove or unset the discount on logout?
Anyone out there got a work around to enable multiple trade prices?
I can display different 'trade' prices on the product page base on whether the user is logged in and has a specific tag e.g. trade25, traed30 &c. But can't pass that price on with the product to the cart.
If I just go with the standard trade_price (i.e. the single trade price functionality that ships with perch) all works OK.
Could I achieve the same thing bay applying a discount code? can this be done automatically?
Drew: Is this (multiple trade prices) something that could be included in release 4?
ellimondo: Thank you, it was the <perch:variant> namespace tags I was missing.
I think this is casued by using perch:categories and perch:variants together. Drew could you please confirm whether or not they can be used together in this way (i.e Can variants be assigned to categories?)
with the help of Hussein I've kind of got this working withCode
- <div class="primary-content">
- <ul class="listing">
- <perch:categories id="colours" set="colours">
- <perch:if id="catPath" value="colours/light-blues/">
- <a href="fabric/<perch:variant id="slug" type="slug">"><img src="<perch:variant id="imageVariant" type="text">" alt="Colour swatch"/></a>
- <a href="fabric/<perch:variant id="slug" type="slug">"><perch:variant id="title" type="text">: <perch:variant id="colorVariant" type="text"></a>
However for every match its generating two sets of <li> tags the first set is identical to the second bar the image having no src.
Page attributes work at treat - thank for the pointer.
I've created a page to list all products that are red
In variants.html I've added an image and a categoryCode
- <perch:group label="Variant">
- <perch:shop id="sku" type="text" label="SKU" required="true" order="1" />
- <perch:shop id="imageVariant" type="image" label="Variant image" order="5" width="800" />
- <perch:shop id="imageVariant" type="image" width="84" height="84" density="1.6" crop="true" />
- <perch:group label="Categories">
- <perch:categories id="colours" label="Colours" set="colours" display-as="checkboxes"/>
- <perch:categories id="neutrals" label="Neutrals" set="neutrals" display-as="checkboxes"/>
In 'fabric_list_rd.html' I'm using
to get the path of the image (will be wrappered with an image tag). However this returns all the image paths for all the Variant images. I would like it to only return the image path of those Variants that are in the category "Reds" I've tried various perch:if statements to no effect, I've also tried
Any help would be much appreciated.
I wish. Any thoughts thought?
Great, I'll take a look, cheers Drew.
WHy has this thread been mark as resolved when clearly it hasn't been - as there are no replies?
Anyone know if its possible to associate an image with a navigation group item? e.g. asign an icon or image to display next to nav item text
When listing product variants is it possible to filter based on product options using <perch:if option="[Value]"> or <perch:if exists="[Option]"> ?
I'm outputting various details using <perch:variants> but only want to output variants that meet a certain condition
Good point about field groups.
Just added field groups on product.html (will also add to other template) definitiely makes things more manageable (helps make the code more readable and the edit forms more compact for the admin/editors) On long forms using collapse also makes the "content" more visible. I had to make a few tweaks to styles.css to stop the <dt><dd> overlapping (in Firefox).
Thanks Hussein (also thanks for your help earlier - I'm slowly making progress!).
Am I alone in thinking that this is a bit of a limitation (from a maintenance point of view) if you have lots different products with different specifications and they all have to be input via the one form template, maintaining it and also using the admin "add product" form could become unmanageble very quickly.
Do all products have to use product.html? or can different types of product use different templates? If so how do I get to select which one to use in the backend when adding products?