The last year has been pretty quiet with Glass.Mapper.Sc, we have been mostly supporting users via Slack and Consultancy. I have also been working on another project that took up a lot of my spare time.
A problem that often occurs on Sitecore solutions is the accidental large publish. A user mistakenly selects a top level Sitecore item, checks Sub-items and Related Items and then clicks publish.
Kam had written an interesting blog post on how to Precompiled view support has been added to Sitecore 8.2 (http://kamsar.net/index.php/2016/09/Precompiled-Views-with-Sitecore-8-2/) I wanted to implement this on 8.1 U3.
This blog post gives you early information on Release 4.3 of Glass.Mapper.Sc! Check out the new features and let us know what you think.
The latest release 4.2.0.184 of Glass.Mapper.Sc is designed to make it easier for developers to customise and also contribute to the project.
A quick browse through the Sitecore config finds the following publish events:
<event name="publish:complete">
</event>
<event name="publish:complete:remote">
</event>
You may notice that by default Sitecore does most of it's events processing in the publish:end event. However there are a few problems with the publish:end event, firstly it isn't called for every language that is published and it isn't possible to easily get a list of all the languages that were published.
Yesterday on Slack the question of how to handle fields that contain a space came up on Slack. In this post we will look at the different ways we can handle this scenario.
.NET introduced the ability to create extension methods on existing classes. This feature allows us to easily add our own methods to exist classes without the need to create a sub-type.
Language Fallback has always been a little tricky when using Glass.Mapper.Sc because it was necessary to use the VersionCountDisabler class. This was required because Glass.Mapper checks the number of version of an item in the requested language and returns null if there are no versions. The VersionCountDisabled stops this check from happening and returns a model using the empty Item that Sitecore returns allowing you to map shared fields to the model.
Much has been said about upgrading Sitecore solutions with the two main approaches being: