Blog
This tip is a must have when developing websites in Kentico's portal engine.
Since version 5.5 it is possible to setup multiple placeholders in your page templates. Simply follow the two steps below:
1. On the parent page template (i.e. Master template) add a "Page placeholder" web part
2. Add the following code in the child page template (i.e. Default template). Make sure the PagePlaceholderID matches with the Web part control ID of the Page placeholder from step 1.
<cms:CMSContent runat="server" id="cntContent" PagePlaceholderID="plcContent">
<cc1:CMSWebPartZone ID="zoneContent" runat="server" />
</cms:CMSContent>
For more information on this tip check out the excellent post by Kentico's CTO Martin Hejtmanek:
Using multiple page placeholders in Portal engine

testThe second post in the page template reduction techniques series is about specifying default page templates for specific document types.
This is the first post of a series of tips and tricks on page template reduction techniques. From my point of view it is very important that you only provide the page templates needed to your end users, making sure that they will not get lost when managing the website. This tip will show you how easy it is to create "Template scopes", to filter the "Page template selection" dialogue.
When working with users and roles in Kentico CMS it is sometimes tricky to find the needed UI permissions. This post will cover a tip for debugging the permissions needed.
In my presentation: "Creating websites from scratch using Portal Engine" at the Kentico Connection I showed you how to create a really blank site. In this tip I will show you the steps I presented.
This tip is mandatory: read Martin Hejtmanek's blog! Martin is the CTO of Kentico and he posts technical details on the current development process of Kentico CMS.
It's 2011 and time for a new Kentico CMS related tip which is very useful and can be easily overlooked.
Here is a quick tip that is useful if you work a lot with widgets in Kentico.
You might know that macros are not allowed in the widgets editing form because of security reasons. Luckily for us developers there is a nice little workaround to enable macro resolving in widgets:
Add the macro parameter as default value for the field and make sure to uncheck "Display attribute in the editing form".
In the screenshot below you can see an example of this where the title querystring is used in the news lists where condition.
A couple of weeks ago, I posted a tip and trick on how to adjust the default properties of web parts and widgets. I wrote the post so that I could easily locate the xml files whenever I needed them. Since that time I have often used the post, but didn’t want to go to the actual files to find the id’s and types of the properties. That’s why I...
This tip and trick is something I find very useful when working with web parts and widgets. You are probably aware of the dialogs that you get when adding or modifying web parts and widgets. These dialogs consist out of default properties which apply to all web parts and widgets and some custom properties which can be set per web part and widget...
It is very easy to integrate Kentico CMS Controls with Visual Studio. Simply add the CMS.Controls.dll to the Visual Studio Toolbox.
Did you ever look for a way to transforms all URLs to a specific case? Kentico provides it’s users this functionality since version 5.0 via a simple setting. To enable it, go to CMS Site Manager, then Settings and select a site. Open the URLs and SEO settings and look for the setting called: “Redirect invalid case URLs to their correct version...
Here’s just a small tip: when you are in a context menu, right click an item to open the sub context menu (if available). For example right click on a document in the context tree and then right click on “New …”.
Have you ever worked in the content tree and felt that the maximum number of displayed documents were not enough? By default this happens when a parent document contains more than 100 child documen...
After last weeks "Where did my module go?" post, I thought that I should write a "Tips and Tricks" post in which I use create a module to quickly browse to Kentico's Developer's Guide (which I often use).
Most of you are probably aware of this setting because it has been available in previous versions of Kentico (4.0/4.1). But for those that don't, you can share user accounts and allow the user to login on all sites.
One of my colleagues showed me a small well "hidden" button, which allows the user to maximize the content view. Very nice find Roel!
Hi! I thought it would be nice to cover some shortcuts in KenticoCMS which I have found useful. Please note that most of the shortcuts existed in previously versions of KenticoCMS and are not specific for Version 5.0.