So our first example effectively attempts to map the raw JSON value of these unattached content nodes and extract out the fields that are of interest: They are instead stored in the Published content cache serialised as JSON formatted objects. Unattached, because they aren't actually part of the Content Tree and hence don't have a parent node at all. Essentially, these data types are based on the concept of using "unattached" Content Nodes and can be rendered to lists of IPublishedContent from a single property. These two can be installed using NuGet or via the Umbraco Package Manager. If you haven't come across these data types before, Nested Content is build into the Umbraco Core software, and InnerContent is an api supporting derived datatypes Stacked Content and Content List. In the first example, we're going to focus on the Nested Content and InnerContent (aka ) based data types. So we're going to look at some code to help extract the relevant information by hooking into Examine's Indexing events. Plugins like Stacked Content, along with Umbraco's built-in Grid Editor and Nested Content data types use JSON as a storage format, and that doesn't lend itself to indexing and searching without some help. The Umbraco CMS is a very flexible and open platform for building an expressive and intuitive Content Editors interface, but sometimes that comes at a price when it comes to indexing the produced content for Lucene/Examine based searching.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |