6 Results for Category Sitecore Presentation
Few years ago, I had written a blog on how to quickly view the actual physical file location of a presentation rendering/sublayout from within presentation settings of a sitecore item in content editor (View presentation control code path). That was on Sitecore 8.1. As mentioned there, it is very useful especially when you are mid-way in a Sitecore project or are in the process of reviewing client's existing Sitecore project.
Today I am going to talk about viewing the presentation file location from within Sitecore 9.2 experience editor itself.
I am sure you must be surprised with the topic here. We all know how to open a link on a new window using the "Target" attribute, and we can set this up on the Sitecore field level when using the "General Link" field. In other words, along with the field value we can also specify the target attribute value in there. But what if there is a situation where we have thousands and thousands of such sitecore items with various values for "General Link" pointing to Sitecore media file of type say "pdf" and you wish to now change those ("General Link") values to indicate the Target to open on a new window. Earlier it was specified with the default same window.
We have all seen the title “Sitecore Platinum Partner” and may have a vague understanding of what this title really means. However, with Sitecore Symposium on the horizon, I felt it was time to dig into what sets this elite group of firms apart from the rest. In my research, I found six key characteristics that this group, of fewer than 20 firms globally, has in common.
Sitecore components and placeholder are one of the main tools that allow content editors to take charge of a page, and control what a site visitor might see. It is often necessary to design components with ease-of-use, as well as re-use in mind. One of the drawbacks of the standard Sitecore placeholder is that it cannot be used multiple times on the same page; Sitecore ends up populating all instances of that placeholder with the same content. This was a problem for me in a recent project, which prompted me to create a Dynamic Placeholders extension. For this post, I will be sharing the process I went through to get Dynamic Placeholder functional in a Sitecore MVC project.
Recently, there was a question in Sitecore Stack Exchange asking whether we can prevent users from editing renderings under shared layout. The requirement was that the users should be able to see the shared layout rendering list but should not be able to perform edits like add or remove renderings.
This article outlines the research and steps I have taken in order to handle it…