• Share
  • ?
  • Profiles ▼
  • Communities ▼
  • Apps ▼

Blogs

  • My Blogs
  • Public Blogs
  • My Updates

This community can have members from outside your organization. WebSphere Commerce Search Cookbook

  • Log in to participate

▼ Tags

▼ Similar Entries

Privacy Headaches fr...

Blog: CSE-WebSphere...
Andres Voldman 06000265WS
Updated
0 people like thisLikes 0
No CommentsComments 0

Cache Invalidation U...

Blog: CSE-WebSphere...
ShoebBihari 3100001AME
Updated
1 people likes thisLikes 1
No CommentsComments 0

Getting Started With...

Blog: CSE-WebSphere...
Eric-Scott 270006G0Q2
Updated
0 people like thisLikes 0
No CommentsComments 0

TWSearch and Saved S...

Blog: Application I...
MarkFilley 27000392R8
Updated
1 people likes thisLikes 1
No CommentsComments 0

Thoughts on type-ahe...

Blog: IBM Collabora...
Chad Scott 110000E1UB
Updated
2 people like thisLikes 2
No CommentsComments 0

▼ Archive

  • March 2015
  • February 2015
  • January 2015
  • November 2014
  • July 2014
  • June 2014
  • May 2014
  • April 2014
  • March 2014
  • January 2014
  • November 2013
  • September 2013
  • July 2013
  • May 2013
  • April 2013

▼ Blog Authors

WebSphere Commerce Search Cookbook

View All Entries
Clicking the button causes a full page refresh. The user could go to the "Entry list" region to view the new content.) Entry list

Getting Search Rules to work with normal 'click' Category Navigation

Brendon Baila 2700006C87 | | Tags:  commerce search rules solr ‎ | 4 Comments ‎ | 8,005 Views

Out of the Box, Search rules only work when you type a search term into the storefront. If you are simply clicking around different categories/facets (called 'category navigation'), search rules will not trigger. We use sequencing/sorting only for category navigation, by default

You can use the below steps as an example to get search rules working for category navigation:

1) Modify the getCatalogNavigationView expressionProvider in the get-data-config.xml. Pass in a '*' into the _wcf.search.term parameter as follows:

image

The get-data-config.xml is in the directory:

<AppServer directory>/profiles/<profile name>/installedApps/WC_<profile>_cell/WC_<profile>.ear/Stores.war/WEB-INF/config/com.ibm.commerce.catalog-fep/get-data-config.xml

Passing in the '*' like this will make the searchTerm value default to '*', if no other value has been specified from the storefront.

(The screenshot is updating the getCatalogNavigationView, you might instead need to update getCatalogNavigationViewbyCategory, depending on which ExpressionBuilder you use)

 

2) Remove the '*' from the prohibited list of search terms in the wc-component.xml:

image

The wc-component.xml is in the directory:

<AppServer directory>/profiles/<profile name>/installedApps/WC_<profile>_cell/WC_<profile>.ear/xml/config/com.ibm.commerce.catalog-fep/wc-component.xml

3) Build your search rule, for example:

image

 

4) As shown in the above screenshot, make sure to make the keyword '*':

image

 

 

 

 

 

 

 

 

 

 

 

 

If implementing this customization, testing should be done on the storefront after to make sure the search rules is influencing the results as expected.

 

If you are in fep6, update the wc-component.xml under the xml\config\com.ibm.commerce.catalog-fep directory by commenting out the following line:

<_config:property name="IgnoreLeadingPatterns" value="[\\*\\?]+"/>

 

Modified on by Brendon Baila 2700006C87
  • Add a Comment Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry
Notify Other People
notification

Send Email Notification

+

Quarantine this entry

deleteEntry
duplicateEntry

Mark as Duplicate

  • Previous Entry
  • Main
  • Next Entry
Feed for Blog Entries | Feed for Blog Comments | Feed for Comments for this Entry