Randy,
It might require some light coding and config.
You need to uncomment this section in ecommerce\widget\CatalogScreens.xml:
<!-- Open this commented section for the demo of
Layered Navigation, navigate through Gizmo and Widgets categories to see
it in action.
<script
location="component://ecommerce/groovyScripts/catalog/LayeredNavigation.groovy"/>
<set field="detailScreen" value="LayeredCategoryDetail"/>
-->
You might need to create markup for your filters in
ecommerce\template\catalog\LayeredNavBar.ftl here for example the
default color and price range filters:
<#if showColors>
<div id="searchFilter">
<strong>${colorFeatureType.description}</strong>
<ul>
<#list colors as color>
<li>
<a
href="<@ofbizUrl>category/~category_id=${productCategoryId}?pft_${color.productFeatureTypeId}=${color.productFeatureId}&clearSearch=N<#if
currentSearchCategory??>&searchCategoryId=${currentSearchCategory.productCategoryId}</#if></@ofbizUrl>">
${color.description} (${color.featureCount})
</a>
</li>
</#list>
</ul>
</div>
</#if>
<#if showPriceRange>
<div id="searchFilter">
<strong>${uiLabelMap.EcommercePriceRange}</strong>
<ul>
<#list priceRangeList as priceRange>
<li>
<a
href="<@ofbizUrl>category/~category_id=${productCategoryId}?LIST_PRICE_LOW=${priceRange.low}&LIST_PRICE_HIGH=${priceRange.high}&clearSearch=N<#if
currentSearchCategory??>&searchCategoryId=${currentSearchCategory.productCategoryId}</#if></@ofbizUrl>">
<@ofbizCurrency amount=priceRange.low /> -
<@ofbizCurrency amount=priceRange.high /> (${priceRange.count})
</a>
<li>
</#list>
</ul>
</div>
</#if>
The variables showColors, colors, showPriceRange, priceRangeList are
prepared in ecommerce\groovyScripts\catalog\LayeredNavigation.groovy so
you can create your own here.
Like I said, some light coding required.
Jason
On 11/08/2020 21:20, Randy Evans wrote:
That sounds very interesting.
Can you tell me how to enable layered navigation? There doesn't seem
to be much information available about that.
Thanks.
On 8/11/20, Rishi Solanki <[email protected]> wrote:
Numerice range won't work as you suspect, and for search not need to do
that. You can simply tag a feature with "> 1000" and "< 1000" as string.
You can use category or feature or even atrribute. And once search is
enable of that feature then you simply need show the tagged products. Which
can be done by all routes, the catalog manager or product creation code
needs to make sure all products tagged properly.
In this way no custom code would be required. HTH!
Best Regards,
--
Rishi Solanki
*CTO, Mindpath Technology*
Intelligent Solutions
cell: +91-98932-87847
LinkedIn <https://www.linkedin.com/in/rishi-solanki-62271b7/>
On Tue, Aug 11, 2020 at 6:33 PM Jason RJ <[email protected]> wrote:
Hi Randy
We have done something similar but using Product Features to drive the
dropdown and Product Variants for each type, this supports search as
expected too since features are added to search criteria as product
keywords. Turning on layered navigation and creating custom filters in
LayeredNavBar.ftl gives you a filter list, it might be possible to build
a range filter that way.
Jason
