Package generation with Search Operations

Hi, It's a short tutorial with regard to search operations. Search operations is used for performing actions on collections of items. By default you can copy, move, serialize, clone, delete, publish the results. On the other hand, you can extend the list of commands with your own commands. It is available from Sitecore 7.0.

So let's add a simple command, which generates a sitecore package from the search result.

Step 1: Create command item and register it.

Create (or duplicate an existing ) command to here: /sitecore/system/Settings/Buckets/Settings/Search Operations/Fields. Fill the "Type", "List Name", "Enable" field.

Finally, register your command in commands.config or create a new config.

Step 2: Create code base for command

Your CommandContext contains the search query and the context item. So you can perform the same search and add items to the package. Here is the code:

That's all! It's really easy to customize search operations.

Comments

Sitecore 8.1 upgrade from 7.2

In the following post, I would like to share my experiences with regard to Sitecore upgrading and highlight some points. We have a project which is running on Sitecore 7.2 update 4. (This project was originally developed on Sitecore 6.5, but we upgraded it a few months ago) We have decided to upgrade that project to 8.1. Probably you know there are more ways to move a project to Sitecore 8. e.g: You can create a new Sitecore 8 instance and transfer your content into the new instance. But we wanted to try the in-place upgrade process when the process modifies the existing instance. Moreover, we were curious how we can move old DMS data to xDB. Step 1: Upgrade to 7.5 (Initial release) If you are already on Sitecore 7.2 you can move your solution to 7.5. Probably this is the hardest and slowest part of the path. Note: Always read and follow the upgrade notes from Sitecore before you start. Before you start 7.5 upgrade, you will need: 7.5 update package (initial release)

Create custom Sitecore Search Crawler

Hello, I would like to show an implementation of a custom crawler which prevents indexing items under specific paths. This is useful when you want to exclude a whole subtree from your index configurations. e.g: You have a multi-site structure which contains 3 sites. You want to implement search funcationlity on one of the sites (call site A) and visitors should be able to search in site B content, but content from site C should not be visible, and you dont want to break relevancy of the search result. The first step is create a class, call CustomCrawler.cs. This class should be derived from SitecoreItemCrawler class. Now, you can overwrite IsExcludedFromIndex method. If you are ready, you should change crawler in the search config. Add paths to ExcludeRoot node and seperate them by pipes. That's all. Now items are not indexed from the excluded paths, and you don't break the relevancy.

Sitecore SPEAK 3 UI collection

Hi, I would like to present my Sitecore SPEAK 3 UI library to you in the hope it will be a helpful template. Please check out a previous Sitecore SPEAK3 related post here . I've created a SPEAK 3 application, in which several SPEAK 3 components and styling are collected. You can download it from GitHub and check what different sitecore/angular components look like and check predefined styles, etc Moreover, I am calling on you all to contribute, because SPEAK 3 is really awesome, and it is quite fun even if you have never used Angular 4 before. How to use the sample code 1) Clone this repository . 2) Run 'npm install ' command in the project directory 3) Run ' npm run start ' command in the project directory 4) Open http://localhost:4123 in your browser How to use directives/components in your SPEAK3 application In this example we are going to add the BackButton , Tabs component and Table directive to our application. 1) Make sure if the @speak

Mitya's Sitecore Tech Blog

Search This Blog