From the Sitecore 8 training, I remember that it said that when you edit you the shared layout of a page, it is the layout delta that is saved.
Before the 8.2 version, you could only modify the shared layout through the presentation details interface. You could modify the final layout in the Experience Editor.
Sitecore 8.2 introduced the possibility to edit both the final and shared layout in the Experience Editor. Great stuff! But there is a small issue, when editing the shared layout in Experience Editor, it saves the raw layout, not the delta.
What does that mean? If you edit the templates standard value, the changes will be seen in the pages who don’t have a shared layout value, or a delta. Why? Because the raw shared layout data takes overrides the value from the template standard value.
We brought this to the attention of the Sitecore Support, and got this patch that fixes the issue nicely: Sitecore.Support.144214.
Sitecore Training Recap
Assembling Presentation Information
- Shared Layout option uses __Rendering field
- Final Layout option use __Final Rendering Field
- Going from right to left, if a field has a layout delta, it goes to the field to its left to gather more presentation information.
AS you may know already, the European Union General Data protection Regulation (GDPR) will reform, modernize and it replaced the 1995 EU Data Protection Directive. The objective is to harmonize data protection rules across 20 EU member states by creating a single, comprehensive EU data protection framework for the processing of and free flow of data with a one=stop shop mechanism for enforcement. The reform aims to give control to EU citizens and strengthen consumer trust in digital economy.
The new law has been voted and published in 2016 and will be effective on May 25th 2018. However, according to Gartner, more than 50% of companies affected by GDPR will not be in full compliance with its requirements.
How many times you wanted to find one of the selected values in the treelist ? Sometimes is easy because you know source of selected item, sometime is harder because you don;t know the system or there are hundreds of item to chose from.
For years I’m using inspect command from my browser. It happened to me used it when I was sharing my screen with coworkers or colleagues and they ware always surprised. I decided to share it with you.
We all use Sitecore Admin Pages and DBBrowser is probably not the most frequent one. But how many times DBBrowser.aspx saved your a.. when you needed? When I joined my current team I notice that this Admin Page was looping indefinitely. If that page is not responding for you, maybe you have same issue .
My colleague – Sébastien Boissonneault– found the source of the issue. Here is his blog entry.
DBBrowser is a great tool to investigate and fix content issues that would not be doable through the content editor.
While waiting for Sitecore 9.X and xConnect we may want to get the most out of Sitecore MongoDB, to go beyond out-of-the-box dashboards and impress executives wit h deep insights. In some cases, Sitecore xDB Cloud may limit you what you can get from custom reports.
To help marketers ans BI specialists I used two tools: MongoDB Connector for BI and Tableau . Continue reading
How to use REST API reference for the xDB Cloud service is described well here. But for someone it will use it for the first time may not be that obvious. Here is a description “for dummies”.
First we have to obtain valid authentication token to make a call to xDB Cloud API. it must to be included as a HTTP header in all requests. Here are a description of this call. I use Fiddler as a tool.
Finally I managed to install Sitecore 9 on a Windows 2012 R2. As you can read in my previous blog post – Sitecore 9 Initial Release on Windows Server 2012 R2 SIF – part 1 – Sitecore Installation Framework have some issues with Certificates creation on OS with IIS 8.5 (Windows 2012 R2 and Windows 8.x).
I will describe my work around Continue reading
I followed Installation Guide for Sitecore 9 Initial Release and I found out that Sitecore Installation Framework is not working with Windows 2012 R2. Why I am writing about it ? Because Sitecore documentation is not that clear.
It says in section 2.1 Sitecore Hosting Environment Requirement that Sitecore 9 will work with IIS 8.5 and Windows Server 2012 R2 (64-bit). Later in documentation, section 5.1 Install Prerequisites is says : Important. The Sitecore Fundamentals module does not support IIS 8.0 or 8.5. The root cause is Power Shell PKI module 188.8.131.52 that reference to IIS dll.
And don’t forget to install Microsoft PoweShell version 5.1 even if documentation says 5.0 or later.
PS. Finally I mange to install Sitecore 9 on Windows 2012 R2 – you can check steps here – Sitecore 9 Initial Release on Windows Server 2012 R2 SIF – part 2
Yeah, Sitecore added support to other combined roles than stand alone. My worries are not valid any more. Please look at my edit on November 22nd.
My client licence is XP3 (3+3). We allow to have 3 production servers. It looks like for the moment (or not) the only supported role combination is XP0 (standalone) – which is recommended only for local development and testing. Here is a link to Sitecore documentation.
If you planning a fully featured Sitecore Experience Platform installation you need separated server roles: Content Delivery, Content Management, Processing, xConnect Collection, xConnect Collection Search, xDB Reference Data, xDB Automation Operations, xDB Automation Reporting. Is my old Sitecore licence good enough? I has been told on Sitecore slack by Sitecore employee : ” From a licensing perspective, you probably want to look at transitioning to the subscription licensing model by speaking with your local sales contact.”
I will you keep posted.
Added on November 8th
Based on Webinar – Sitecore Pricing Overview for Partners I can tell that all xDB processing server are PRODUCTION now.
Added on November 22nd
It looks like it was a false alarm. Sitecore yesterday added new combined roles
I has been ask by business to find out a way to not track internal visits – easy stuff – we can add internal IP, public IP into <excludedIPAddresses> node of Sitecore.Analytics.ExcludeRobots.config file.
It worked for a while. Then I has been ask to disabled only on CM, but …sometimes 😉 . Marketers, usually don’t want to see internal traffic to be tracked, but from time to time they would like to test some functionalities and to track visits. Deploying each time a config file is not an option.
I thought, it would be nice to add some logic into the same pipeline (excludeRobots) where we filter already IP to exclude.