Would you like to not index the files, or just not want the files to be shown in the public search results ?

are you using Find (Search & Navigation)

Thanks Quan.  Yes, we are using Search & Nav.

I can't think of why any of our uploaded files need to be indexed, but either way should achieve the immediate goal.

You can add a convention to prevent those files from being indexed. P/s you should update to latest version of Form if you haven't already

Adding a convention is one thing I was looking at, but how do I target files specifically uploaded via the FileUpload element?

Re: EPiServer.Forms, I am on the latest

A quick way to do it - not bulletproof but probably good enough, is check a file of type IContentMedia if it belongs to folder named EPiServer.Forms.Constants.FileUploadFolderName before indexing 

Quan, I'm making a guess you are referring to something like:

ContentIndexer.Instance.Conventions.ForInstancesOf<IContentMedia>().ShouldIndex(x => x.???)

If so, how would I check for it's containing folder?

If not, can you share more info on how to do this?

Yes, you can get its parent, something like this (pseudo code of course) 

x =>  {

var parent = _contentRepo.Get<ContentFolder>(x.ParentLink);

if (parent.Name == EPiServer.Forms.Constants.FileUploadFolderName) { return false ; }

return true;

}

I'll try this.  I'll add this to our SearchInitialization module, which I assume is used during indexing.  I am wondering though... could this approach have a significant impact on performance of indexing?  I suppose I needn't be too concerned about the overnight job, but wanted to check.

it depends on how many files you have - and under how many folders. if you have many files but only a few folders it would not take a lot of time (Get<T> is cached )

If we take a step back, this should not happen. Can you please reach out to support at support@optimizely.com, refer to this thread and cc me (quan.mai [at] optimizely.com ) ? we are interested in looking into this. thank you

Hello all,

I had to reopen this issue.  The offered solution did function as suggested, and I thought all was well.

However, it had the side effect of including files from other locations (namely globalassets) in the search that weren't there before.  My code (based on Quan's) was:

var _contentRepo = ServiceLocator.Current.GetInstance<IContentRepository>();
ContentIndexer.Instance.Conventions.ForInstancesOf<IContentMedia>().ShouldIndex(x => _contentRepo.Get<ContentFolder>(x.ParentLink).Name != EPiServer.Forms.Constants.FileUploadFolderName);

Without this code, I have no idea how globassets are excluded, but with it they are included.  I suppose other types of files were incorrectly included too, but I didn't scour our thousands of results.

Any ideas on why, and how to fix it so uploaded files are added to files to exclude?

I suggest to find if you have any other conventions with IContentMedia which this overrides, and merge them into one 

I have no other conventions with IContentMedia that I could merge.

It turns out that the originally suggested code aslo broke our search statistics, and we don't know why.  Anyway, my resolution to this issue also fixed our search statistics & autocomplete functionality.

The code that ended up working was:

var _contentRepo = ServiceLocator.Current.GetInstance<IContentRepository>();
ContentIndexer.Instance.Conventions
	.ForInstancesOf<IContentMedia>()
	.ShouldIndex(x => x is not ImageData && _contentRepo.Get<ContentFolder>(x.ParentLink).Name != EPiServer.Forms.Constants.FileUploadFolderName);