I'm trying to enable ajax on search core results webpart so that the pagination can be realized in an asynchronous manner. But this is not working. Is this normal? Do you succeed to configure search core results and paging webparts to work asynchronously?

Thanks for your help.

  • It would be much easier to help you if you provided particular problem which you're facing. What have you tried, which options values have you set up, and what errors (in ULS or on the page) or visual results have you got? Jan 5, 2012 at 15:56
  • In fact it is just not doing asynchronous calls. When I click on a page number, I get a normal postback.
    – Win
    Jan 5, 2012 at 18:27
  • Anyone can help on that? Did you already see the ajax on search core results working?
    – Win
    Jan 6, 2012 at 9:47

2 Answers 2


Most likely, the problem is that there are two separate webparts in Search Center: Core Results Web Part and Search Paging Web Part. And while Core Results Web Part supports asynchronous functioning, the paging webpart doesn't seem to have any ajax-related properties.

Actually, CoreResultsWebPart is inherited from DataFormWebPart - that's why we've got the Ajax parameters section, and the DataFormWebPart undoubtedly does support asynchronous postbacks.

So I assume if you want to configure AJAX paging, the only option could be to give up the Search Paging Web Part, and try to implement paging through XSLT. Probably it will be not very cool paging, but it will be asynchronous.

To implement paging using XSLT, you have to add some XSLT code to CoreResultsWebPart, as described in the following article:

I haven't tried this solution myself, but the idea seems logically strong :)

  • Thank you. I will take a look to this link and try several approaches.
    – Win
    Jan 6, 2012 at 10:45
  • One more question, in the link you gave me, the author seems to add params at the top of the xsl section. Do you know where he will get the values for these parameters? Thanks.
    – Win
    Jan 6, 2012 at 17:43
  • Usually they're passed through ParameterBindings: msdn.microsoft.com/en-us/library/ff806155.aspx Jan 6, 2012 at 19:24

..."And while Core Results Web Part supports asynchronous functioning". I believe this is the problem right there. The initial load of CRWP does indeed work when asynchronous is turned on, but refresh or automatic refresh does not. The asynchronous refresh functions send the part into loading mode and never return.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.