volume_up

A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

volume_up

A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

episerver search

I'm following this example to get a fully functional search engine in episerver 8:

episerver example

Unfortunally I don't recieve any results. I think the example might be incomplete. I call the method FindPages, but get empty result.

I inted to search for content. Whould it be preferably to use FindPagesWithCriteria instead?

Kind regards

Daniel

#122171
May 27, 2015 15:17

I keep getting: ERROR SearchSettings: Send batch for named index 'serviceName' failed. Items are left in queue..

And also I get a Remote Server returned an error 400. Been search world, but the solutions do not seem to be working for me.

Can anyone please help?

#122222
May 28, 2015 14:20

I would not use Findpageswithcritera if you do a search page, since it is not good in performance.

Regarding the error.

You could try to delete the index-folder and reindex all by this adress:

 http://yoursite/EPiServer/CMS/Admin/IndexContent.aspx

#122250
May 28, 2015 15:21

Thanks Fredrik. I've done that, but without any luck. Now I try to copy from Alloy site, hence I got it to work there. Holding my thumbs.

#122252
May 28, 2015 15:28

Do that. Propably it has to do with some settings in web.config or simular.
EPiServer Search are often a pain in the ass to get to work propably and if you can use EPiServer Find, it is much better and more fun to work with

#122253
May 28, 2015 15:35

Unfortunaly Episerver search is the path chosen in this project.

As mentioned earlier I try to implement the search functionality found in alloy to my site, but with low success rate. Just as before, the result is zero.

Henrik: Can you ellaborate on what might be tricky in the web.config file? As far as I see in the guidlines, it should be pretty straight forward. But is seldom is, is it= ;)

#122261
May 28, 2015 17:00

The key thing in web.config is to get it to allow the right ip-range and to have the keys correctly.
It is also very important that you do not have the indexed shared by many updaters because that will kill your lucene-index. Only one server can update the index.

Read more here:

http://world.episerver.com/Forum/Developer-forum/-EPiServer-75-CMS/Thread-Container/2014/9/Is-my-EPiServer-Search-functioning-correctly/

http://world.episerver.com/Modules/Forum/Pages/Thread.aspx?id=121895

http://world.episerver.com/Modules/Forum/Pages/Thread.aspx?id=120933

#122265
May 28, 2015 20:58

Thanks Henrik.

I'm still getting this in the episerver log:

2015-05-29 14:03:38,208 [11] ERROR SearchSettings: Update batch could not be sent to service uri 'http://local.mysite.se/IndexingService/IndexingService.svc/update/?accesskey=local'. Message: 'Fjärrservern returnerade ett fel: (400) Felaktig begäran.   vid System.Net.HttpWebRequest.GetResponse()

Any thoughts on that? when I run that url in the web browser I recieve a text message stating Method not allowed.

#122296
May 29, 2015 14:07

Since the web site I'm developing doesn't contain very much content, I will use FindPagesWithCriteria instead.

#122358
Jun 01, 2015 9:53

Sorry, had a busy weekend.

That sounds strange, and yes if you have a small site that might work.

Hope that EPiServer will add some effort into EPiServer Search, or replace it.

#122359
Jun 01, 2015 11:05

I'm now using FindPagesWithCriteria. I'm searching in properties of type XHtmlString. To my disappointment I only get results from one of many, althoug they all include my searchword. It really bugs me out.

#122399
Jun 02, 2015 9:50

Hi Dejan,

I red your comment a few days ago, but hadn't got time to look into it. Seemed interesting, but pretty similiar to EPiServer Search? Why did you erase the comment?

#122536
Jun 04, 2015 12:44

I didn't want it to look like advertising :)

Here's the link to the original blog post: http://dcaric.com/blog/episerver-simple-search-and-shared-blocks

It's built on top of Lucene.NET, same as standard EPiServer search, and uses content events to automatically re-index all affected pages.

Why I think it could be useful to other EPiServer developers?

- In the case when the client doesn't want to invest more than a day in custom search solution. When he needs something very simple
- It's free, in terms of hosting, maintenance, what not
- It doesn't require any kind of configuration in web.config. If something goes wrong, you have the full source code so you can easily debug it, extend it, what not
- There are a few very good blog posts on how to extend the built-in EPi search functionality and how to index custom fields (blocks, for example). My SimpleSearch solution will index not just the current page, but all affected pages as well, which I believe is very important.

It has a few limitations as well, for example:
- Lucene.NET doesn't work very well with shared folders
- I didn't build the functionality for indexing the files (PDFs, office files, etc.)
- It doesn't have multi-language support
etc.

I always recommend EPiFind or custom search solution built on top of Apache Solr / Elasticsearch, but if that's not an option, my SimpleSearch solution will serve you well :)

#122539
Jun 04, 2015 14:14
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.