This project is read-only.


Selected facet value doesn't pass as an encoded string


Faceted Search V2.0 is installed on the server and we have faceted search configured. Wnenever user clicks on the facet, value gets passed without encoding. And it causes issue in our custom application as one of the faceted value contains "&" and when user clicks on that perticular facet, it passes it as a "&" (it should be passed as a %26---encoded value for &).
Now, I would like to know whether it's an known bug in the V2.0 and got fixed in next version?


leonidly wrote Jun 19, 2009 at 3:50 AM

Faceted Search 3.0 addressed "&" encoding

deepakbadki wrote Jun 23, 2009 at 8:23 PM

Thanks Leonidly!

One strange thing happening in my dev server :(. If the facets webpart and core results webpart are on the same page then the query parameter value is passed as encoded string in request URL (address & issue). But when I use the facets with some custom webpart on the same page, selection of facet results in passing the query parameter values <b>without</b> encoding.

Let me know if you have any idea.

leonidly wrote Jun 25, 2009 at 3:30 AM

Hard to say anything when it involves unknown custom webpart that impacts behaviour.

deepakbadki wrote Jun 25, 2009 at 4:15 AM

Got the solution!
On click of facets, it wipes out the parameters which custom webpart passes as a query params and those parameters are not know to the Faceted search. In my case, I am passing pNo=1&pHitCount=10 as the query parameters which gets wiped out on click of any facet postback.


wrote Jul 12, 2009 at 2:28 AM

wrote Feb 14, 2013 at 3:41 AM

wrote May 16, 2013 at 8:10 AM

wrote May 16, 2013 at 8:10 AM

wrote Jun 14, 2013 at 7:52 AM