Hey guys,
while I’m watching the Euro 2008 or Formula 1 I’m writing about the new layout editor in crestone.
If you are a user with page designing features, you get a button in the page editor at the top (first screenshot) and if you click on it; the new page editor opens at the top of your page. As you see in the second screenshot you have a list with all aviable placeholders (and a description and/or an image - if you add a so called “placeholder definitoon”). All of you know the problem, you have to remember the given placeholder key or you have to open the layout and look for it.
At the top you can set the layout as well.
Look at the “blue arrow” in the screenshot, you can see where the placeholder is. Pretty nice 
You can also set allowed controls for a special placeholder, nobody can add a rendering which isn’t for this placeholder. You can set a description for a rendering / sublayout as well.
All this features are rendered in realtime, you click on add and the rendering gets inserted in the placeholder you selected.
The old school property editor is still alive and is still be used, as you might see in my last screenshot.
I still don’t know I like this feature or not 
, if you are a smart reader of my blog you might know the placeholder selection for Sitecore 5.3. To be honest, I really love this! In my last days I forgot to write an entry, because I was so interested in building a new site in Crestone instead of writing.
Have a nice weekend, and enjoy the Euro 2008. cheers
Hey guys,
as you might see in my last post I added a new feature called gallery. It pissed me off last night to write a text in wordpress with inline images. So you see there is a gallery in the post, there are still some bugs. I try to solve them in the next couple of days.
Maybe I have to update my text due to the comments on the images, but I hope you still understand my last post.
cheers chris
update: Due to Phil Heltewig: I don’t mean the inline editor in Crestone, I hate to write a blog entry with inline images
So,
our next stop on the way to Crestone is the whole new webedit client in Crestone, now called “Page Editor”. The upcoming Sitecore version finally supports inline editing of content.
So, if you want to edit the current site, you have an edit button at the top at your page. And if you click on it you get a menu: Save, Save & Close, Close (without saving the changes), Ribbon. On the screenshot to the left you see the new onsite editing. You can change or insert an image as well (the question mark). That’s a feature what everybody wanted to have, you can see how it looks like, live. No more preview ;-).
If you click on the “Ribbon” button, the well know ribbon strip in the content editor is inserted at the top. You can change the versions, duplicate or navigate thorugh the tree for example. Pretty handy and useful for every content editor. Â
Sitecore changed a lot in the security concept, so my Crestone beta comes with a preinstalled starter kit. On the left site you see a couple of new Sitecore roles, “minimal authoring features” for example. Or with “page designing features” - sounds pretty interesting, he? I will write about that in my next entry.
Sitecore introduces three different types of content editor rights: minimal, limited or normal. See the differences in the screenshots below.
Well guys, the time passed and I have to finish. Hope I could give you some insights of Sitecore Crestone. Good night
Hey guys,
as you might know Sitecore version 6 alias Crestone is coming up at the end of June. As you might have heard there will be a public beta of Crestone in the next couple of weeks. And after some chats with Lars he allowed me to write about some new features and major changes in Sitecore. I’m using Sitecore Crestone build 2 at the moment.
So let’s start with the changes in the web.config.
- I guess the most important is the change from .net 2.0 to .net 3.5. Based on this ajax is automatically included in the project. As well as the .net membership provider - and of course it’s used by sitecore.
- There are only 3 databases (Core, Master and Web) which intend that Crestone is “leighter” than Sitecore version 5.
- I found some new events:
- publish:itemProcessing
- publish:itemProcessed
Which can help you to indentify and handle problems in the publishing process more comfortable.
- In the initialize pipeline I found a new processor: <processor type=“Sitecore.Pipelines.Loader.InitializeAgilityPack, Sitecore.Kernel“/>
- There is also a new pipeline called “preprocessrequest”:
<preprocessRequest help=“Processors should derive from Sitecore.Pipelines.PreprocessRequest.PreprocessRequestProcessor“>
<processor type=“Sitecore.Pipelines.PreprocessRequest.NormalizeRawUrl, Sitecore.Kernel“/>
<processor type=“Sitecore.Pipelines.PreprocessRequest.IIS404Handler, Sitecore.Kernel“/>
<processor type=“Sitecore.Pipelines.PreprocessRequest.FilterUrlExtensions, Sitecore.Kernel“>
<param desc=“Allowed extensions (comma separated)“>aspx, ashx, axd, asmx</param>
<param desc=“Blocked extensions (comma separated)“>*</param>
<param desc=“Blocked extensions that stream files (comma separated)“>*</param>
<param desc=“Blocked extensions that do not stream files (comma separated)“></param></processor>
<processor type=“Sitecore.Pipelines.PreprocessRequest.StripLanguage, Sitecore.Kernel“/>
</preprocessRequest>
- In the httpRequestBegine pipeline they changed the order from: site-, database-, begin diagnostics, device-, security-, language-resolver to: site-, user-, database-, begin diagnostics, device-, device-, language-resolver (They removed the security resolver and added the user resolver). They also added the DynamicLinkResolver.
- I found the publish item and publish pipeline as well:
<publishItem help=“Processors should derive from Sitecore.Publishing.Pipelines.PublishItem.PublishItemProcessor“>
<processor type=“Sitecore.Publishing.Pipelines.PublishItem.RaiseProcessingEvent, Sitecore.Kernel“/>
<processor type=“Sitecore.Publishing.Pipelines.PublishItem.CheckVirtualItem, Sitecore.Kernel“/>
<processor type=“Sitecore.Publishing.Pipelines.PublishItem.CheckSecurity, Sitecore.Kernel“/>
<processor type=“Sitecore.Publishing.Pipelines.PublishItem.DetermineAction, Sitecore.Kernel“/>
<processor type=“Sitecore.Publishing.Pipelines.PublishItem.PerformAction, Sitecore.Kernel“/>
<processor type=“Sitecore.Publishing.Pipelines.PublishItem.RemoveUnknownChildren, Sitecore.Kernel“/>
<processor type=“Sitecore.Publishing.Pipelines.PublishItem.MoveItems, Sitecore.Kernel“/>
<processor type=“Sitecore.Publishing.Pipelines.PublishItem.RaiseProcessedEvent, Sitecore.Kernel“ runIfAborted=“true“/>
<processor type=“Sitecore.Publishing.Pipelines.PublishItem.UpdateStatistics, Sitecore.Kernel“ runIfAborted=“true“>
<traceToLog>false</traceToLog>
</processor>
</publishItem><publish help=“Processors should derive from Sitecore.Publishing.Pipelines.Publish.PublishProcessor“>
<processor type=“Sitecore.Publishing.Pipelines.Publish.AddLanguagesToQueue, Sitecore.Kernel“/>
<processor type=“Sitecore.Publishing.Pipelines.Publish.AddItemsToQueue, Sitecore.Kernel“/>
<processor type=“Sitecore.Publishing.Pipelines.Publish.ProcessQueue, Sitecore.Kernel“/>
</publish>
- I’m not going that deep into the structure of the web.config, but I guess these are the most important parts of the pipeline part. In fact they added a bunch of new pipelines, but because this would be to overwhelming I don’t copy & paste every new pipeline here. Some new pipelines sound pretty interesting, because it allowes you to customize Sitecore a lot more than before, and easier of course.
- Another major change is the security concept based on the .net membership provider, but I will point this feature out some other time.
- They improved a bunch of new configuration blocks like mediaPath which handles the mediaPathProvider and let you intercept this with your own providers for example.
- I saw two new xslt extension controls: The WebEditRibbon and the StringUtil.
Well, I’m going to spend my time on the settings another day, but all this changes mean that sitecore is more flexible than ever before. I hope that’s enough for the first time. I will write some more, but for today I’m done.
Good night
Loading ...
