On one of our Sitecore based projects we initiated an upgrade from Sitecore 9.2 to Sitecore 9.3. Upgrade was straightforward, with one exception.
The original project was using Glass.Mapper in its 9.2 version (5.5.28), and during upgrade we updated Glass.Mapper to its 9.3 version 5.6.160, including the takeover of original, vanilla, configuration files.
The following exception was … little bit unwanted result of the upgrade process.
22248 11:45:18 WARN Could not find constructor in ReflectionUtil.CreateObject: Glass.Mapper.Sc.Pipelines.GetChromeData.EditFrameBuilder. The constructor parameters may not match or it may be an abstract class. Parameter info: Count: 0
Continue reading Glass Mapper and Sitecore 9.3 Upgrading Issues
Why customize the default Sitecore workflow?
Sitecore is by default shipped with Simple Workflow covering simple draft – approval – publish scenario.
In this scenario, publish state of the workflow is set as final. This fact causes that when the content author needs to edit item fields, a new version of the item is created automatically, and changed content is subject to the approval process.
Some customers may need to extend this workflow by an additional state to control the moment when the item is published (and they don’t want to use time-based publishing) by adding the additional step between approval and published states.
The resulting workflow then looks like
draft – approving – approved – publish
with publish state as the only with final flag.
Everything looks fine, but…
… there is one unpleasant side effect. It allows content editors to change values of items in approved state without enforcing of creation of the new version.
Insert options, and their proper configuration is the crucial part of the solution development. It is the only way how to provide a way to the content editors to create new content.
Unfortunately, regardless that Helix is the current buzzword, still, there are some areas, where Sitecore does not provide out-of-the-box support for the stricter following of Helix principles.
One of them are Insert options configuration.
Continue reading Helix Compatible Insert Options
Sitecore 9.1 was finally released. Although everyone expected to have at least of technical preview of new UX experience “Horizon”, it is not included. But, still, there are couple features to be explored.
The first updated and improved experience include installation process. In comparison with previous Sitecore versions, few improvements were added to setup Sitecore with less effort.
Continue reading Sitecore 9.1 – Updated installation experience
Sitecore recently announced that Web Form For Marketers (WFFM) will be no longer officially supported. Sitecore plan to focus only on the development of Sitecore Forms, a new application to design forms, which was introduced with Sitecore version 9.0 initial version. Since many of Sitecore implementations use WFFM or custom developed forms you might think about using Sitecore Forms instead. I’ll give you five reasons from Sitecore user perspective why to do it. Continue reading 5 reasons to migrate to Sitecore Forms
Namely in multilingual solutions you may face request to limit content editors to edit just specified language variant of content.
In Sitecore, the way how to reach this objective is very quick and effective, but “by default” the way how to perform this restriction is hidden, and you need to do some additional steps.
Continue reading How to restrict content editor to edit content only in specified languages?
Recently, I played (and destroyed) with Sitecore Email Experience Manager (EXM) on our Actum’s Sitecore playground. I was wondering, what is proper configuration and development requirements delivered before you can send your first newsletter campaign. I have summarized for you the most common requirements for most EXM implementation. Continue reading All you need to know before using Sitecore Email Experience Manager
I often receive question if Sitecore can also a platform for lead management. Sure, it can. On the one hand, Sitecore can evaluate the quality of your leads and on the other, Sitecore might provide personalised content to increase the quality of unqualified leads. And when the leads ready to make a purchase? Let Sitecore automatically inform your sales department that you have a lead ready for them. Let’s have a look how to simply evaluate the lead quality in Sitecore. Continue reading Simple lead qualification with Sitecore Marketing Automation
How do you check if your campaigns perform well? Simply, you check Google Analytics and based on UTM parameters identify your campaigns and analyze collected conversions. But, can you see how all campaigns related to single business unit in specific location perform? Maybe campaign view for specific product or service? And can you see with same classification performance your offline campaigns as well? In Google Analytics it would be rather difficult, but with Sitecore, it can be easy.
You only need to define the proper classification of your campaigns and track ’em all!
I’m not telling you to get rid of UTM tracking but combine them with Sitecore Campaign tracking and benefit from both. Let’s have a look how to simply use Sitecore Campaign Creator to generate both Sitecore Campaign & UTM tracking parameters. Continue reading UTM and Sitecore campaign tracking: side by side approach
Do you remember how Sitecore configuration files for multiple environments and server configurations were handled? Times, when files needed to be removed during deployment process, renamed, overwritten or transformed? These times are definitively out!
Continue reading Sitecore 9: Rule based configuration