Carlos Rodriguez

The process of taking advantage of the Ignition framework when it comes to building models is to pass data successfully to the view’s agent so it can use its PopulateModel method to transfer the data to view’s model or perform any other logic necessary to properly render the Sitecore component. Through MVC’s architecture, a query […]

I was creating a component in Sitecore where the item structure was three tiered meaning that the component’s datasource, its children and grandchildren from its structure in the content tree would have to be accessed to properly populate the component.  An example of this structure is shown below where the component’s datasource is the top […]

The Ignition framework contains an overridden version of the View() method which is used to not only call the view file which is to be rendered but also has a variety of options to support sophisticated logic associated with rendering the view.  The View() method full signature is defined as follows in Ignition. return View<TAgent, […]

The Ignition framework has as a standard for using a constants file as opposed to having constants randomly assigned to variables throughout the application.  When a new Ignition project is created, an IgnitionConstants.cs file is added to the Ignition.Sc project within the Presentation folder of the Ignition solution. Example of the type of constants oriented […]

Using the Ignition Framework, we have variety of methods in our disposal for setting the view path to find the view.  The methods of setting the view path which will be discussed in more detail will be… Inherit folder structure Within the View Model itself Using the View Agent Using Agent Parameters Inherit Folder Structure […]

For most situations when the view path for a component is specified in code, it is either implied by its folder location coinciding with its controller call or directly referenced in the view model used by the view.  However, it is sometimes preferable to make a view model as re-useable as possible by multiple Sitecore […]

Usually the Home Item in a Sitecore site infrastructure is a key item since all other pages of the site are descendants of this one item so if the wrong thing happens to this item, the site can go down.  So this particular item tends to get protected from a security stand point. A short […]

This is will be a quick blog about a detail involving Sitecore which I find myself using more and more.  Often in Sitecore, we have a component which can be added multiple times to a page but we need the means to identify a specific instance of that component in code to perform some activity […]

Recently, I had installed Microsoft’s IIS URL Rewrite 2.0 application within my local Sitecore development environment.  For those who are not familiar, this application is used to redirect certain URL calls to other URL locations.  As part of this environment set-up we are using Hedgehog TDS to manage and track Sitecore items. However, when I […]

I was tasked with setting up the security settings which was needed for the content editors providing the content of the Sitecore site we are working on. While Sitecore provides an author role, it does not provide an editor role which allows a content editor to edit existing items and well as add new items […]

I have been working in a Sitecore environment where in code, I am checking the branch template ID of an item when searching for those items using Coveo.  Once I completed my unit testing of this functionality in my local development environment, to move things along, I created a package of these items to install […]

In this blog I want to discuss what to look out for if you are re-installing the Coveo package unto Sitecore 8.  In developing within a Sitecore 8 site recently I had installed the Coveo version 1266 package on the site but needed to replace it with the Coveo version 1226.  Each time I tried […]