Henrik Fransas
Mar 11, 2014
  6293
(1 votes)

Indexing only referenced files with EPiServer Find 7.5

Henrik wrote a very good blog post on this for the previous version of Find that you can find here:

http://www.lindstromhenrik.com/indexing-only-referenced-vpp-files-with-episerver-find/

If you want it to work with iContent all you have to change this:

Remove this:

FileIndexer.Instance.Conventions.ShouldIndexVPPConvention = new ShouldIndexVPPConvention(x => true);
 
Change this:
FileIndexer.Instance.Conventions.ForInstancesOf<UnifiedFile>().ShouldIndex(x =>
To:
ContentIndexer.Instance.Conventions.ForInstancesOf<IContentMedia>().ShouldIndex(x =>
 
Then change this row:
var softLinks = contentSoftLinkRepository.Load(x.VirtualPath);
To:
var softLinks = contentSoftLinkRepository.Load(x.ContentLink, true);
 
And it should be up and running!

Good luck!

Mar 11, 2014

Comments

Kim Medin
Kim Medin May 19, 2014 02:32 PM

This doesn't seem to work if the reference is from a property on a page that doesn't have a template (settings page, container pages etc).
Any ideas if that can be solved?

Henrik Fransas
Henrik Fransas May 19, 2014 02:41 PM

Kim, I didn't know that, thanks for the information. It must be that those links does not register as softlinks. It should not be hard to extend the function to also search through all the properties that are contentreference to a mediadata-content. I do not have the time to fix that right now, but will look into it

Chaudhry Mohsin Ali
Chaudhry Mohsin Ali Jun 20, 2018 10:15 AM

Where should we include this file? Should it be in an init module?

Chaudhry Mohsin Ali
Chaudhry Mohsin Ali Jun 20, 2018 11:02 AM

And when we unlink the file what should happen then?

For example when we add a file in the content area it should appear in the search result but after deleting the file from the content how should we update the index, so that the file is not included next time?

Please login to comment.
Latest blogs
“Learning by Doing – Optimizely OPAL Series” | Episode 02 is Live!

Introduction With Optimizely OPAL, we’re not just generating content—we’re designing intelligent workflows. But after working with teams and...

Ratish | Jun 14, 2026 |

Content Variations in CMS 13, Part 3: Audiences vs Audiences

Executive summary. Part 2 left the experiment running against Everyone . Real projects don't look like that. So this part wires those same CMS...

Piotr | Jun 14, 2026

Hiding Pages in the Optimizely CMS 13 Page Tree

When working with large Optimizely CMS solutions, the page tree can quickly become one of the biggest sources of editor frustration. This is...

Pär Wissmark | Jun 13, 2026 |

Four database surprises when upgrading from CMS 11 to CMS 13

We're in the middle of migrating a fairly large site from CMS 11 / .NET Framework to CMS 13 / .NET 10. The code migration is one thing, but the...

Per Nergård (MVP) | Jun 12, 2026