Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more

Per Magne Skuseth
Feb 27, 2015
  11016
(15 votes)

Inspect In Index for EPiServer Find

Have you ever found yourself in the situation where you’ve been wondering if your index content is correct, updated or there at all? I have. Often. So, to save me from having to go to the Find Explore view and search for the content, I created another content view to inspect the index for the currently selected content. So simple, but SO useful!

iii 

The view shows the current content’s raw form in the EPiServer Find index. From the view you may also index, re-index or delete the content from the index. It will show the content for the currently selected language. Works for pages, blocks, media and custom IContent.

Note: Since non-developers are most likely not interested in the view, it will by default only be visible for users that are members of the “CmsAdmins” or  the “SearchAdmins” role.

Want to try it? It’s in the EPiServer NuGet Feed: Install-Package EPiCode.InspectInIndex

Source code and documentation: github.com/BVNetwork/InspectInIndex/

Feb 27, 2015

Comments

Henrik Fransas
Henrik Fransas Feb 27, 2015 12:14 PM

Nice work as always!

Feb 27, 2015 01:07 PM

Awesome! I am spreading the word here in Finland.

Feb 27, 2015 01:11 PM

Awesome stuff! Straight into my toolbox!

Janne Kuusela Kuusela
Janne Kuusela Kuusela Feb 27, 2015 02:49 PM

Cool and really useful!

K Khan
K Khan Feb 27, 2015 03:17 PM

very helpful indeed, Bundle of Thanks!

Feb 27, 2015 10:21 PM

I must join in on the comment love train. This is sweet! :)

Malik
Malik Dec 23, 2021 10:55 AM

Hi Team,

I tried the solution in Alloy sample site, for few languages it works and for few it gives below error. Any clue to resolve this?

Error:

An unexpected error occurred: RequestError: Unable to load /EPiServer/Find/proxy/MalikAlloy_Models_Pages_StandardPage/_579871c7-6ec0-4a2b-b7b7-bd3c24af776c_da?language_routing=da status: 400

Thanks in Advance!

Please login to comment.
Latest blogs
Save The Date - London 2025 Summer Meetup

Following last years very succesful meetup in London July 2024 https://world.optimizely.com/blogs/scott-reed/dates/2024/7/optimizely-london-dev-mee...

Scott Reed | Mar 25, 2025

Revalidate Page in Next.js after Publishing Content in Headless Optimizely PaaS CMS.

Headless CMS implementations are becoming increasingly popular. In this approach, the CMS and the front-end application are decoupled and can use...

Tomek Juranek | Mar 25, 2025

Getting 404 when expecting 401

A short story about the mysterious behavior of an API in headless architecture.

Damian Smutek | Mar 25, 2025 |

A Free Course for Building Headless Applications with Next.js and Optimizely SaaS CMS

I am excited to announce the transformation of Optimizely Headless CMS webinar into a comprehensive, completely free self-paced course that's...

Szymon Uryga | Mar 24, 2025