Heads Up - Breaking changes in search index just landed in the source code repository

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
This thread is closed to new posts. You must sign in to post in the forums.
1/21/2013 4:47:39 PM
Gravatar
Total Posts 18444

Heads Up - Breaking changes in search index just landed in the source code repository

Hey Everyone,

We try to very hard to avoid changes that might break 3rd party custom features but every now and then we can't avoid it if we want to move forward.

Some major improvements to the site search index were just completed and this resulted in a breaking change for anyone who has implemented search in their custom features building on top of our internal lucene.net search index.

Fixing your broken code is straightforward. Get the latest mojoPortal code and then compile your feature against it. Anywhere that it breaks (doesn't build) on search index related code just add:

using mojoPortal.SearchIndex;

and re-compile.

Other than that, in your indexbuilder you should assign new properties on IndexItem for CreatedUtc and LastModUtc to reflect those properties on your content. Also if your feature has a separate field for an excerpt, abstract, or summary, you should assign that on indexItem.ContentAbstract. There is also a new property for indexItem.Author that you can populate if it makes sense for your feature to show that in search results.

​Sorry for the inconvenience but I think it will be worth it having these search index improvements for the long term.

Best,

Joe

You must sign in to post in the forums. This thread is closed to new posts.