Group items tagged

In this post I want to show how to address a missing feature that was a part of "old" lucene index implementation. This article will provide an example how one can customize Lucene search configuration so that it's possible to add custom fields to the index.

WeBlog is a blog module for Sitecore 6.2+. It is the successor to the EviBlog module. Features Windows Live Writer integration (MetaWeblog API) Page Editor support and custom WebEdit ribbon Wordpress Import CSS-based themes, with custom themes possible (one included) Various blog navigation components Comments (with author notification and optional approval workflow) Comment CAPTCHA through MSCaptcha or reCAPTCHA Gravatar Support Social sharing through ShareThis or AddThis, and other Facebook and Twitter widgets Tagging and tagcloud RSS Feeds (Sitecore Integrated RSS) Multi-server (staged architecture) support Globalized labels and messaging (English, Danish, Dutch, and Japanese translations provided) Most importantly, WeBlog has been architected to allow you to easily integrate it into your existing content and design, and to allow you to customize its templates and layout to your project requirements.

Create your own custom token hooks to fill fields. The built-in tokens are $name, $id, $parentid, $parentname, $date, $time, $now

How to implement custom "code transformers" to inject custom rendered code into a blog post

Every once in a while our customers ask if it's possible to terminate a publishing job. A demand for this functionality increased as our customers started pouring more and more content into their Sitecore implementations. Sometimes an innocent publishing job could become vicious and freeze other publications. In this blog post I'm going to present an approach that allows a user to cancel a triggered publishing job. This became possible as new publishing pipelines were introduced in Sitecore 6.

Custom 404 page ignored by IIS 7 - TrySkipIisCustomErrors

The custom ASP.NET NUnit test runner is a simple utility to allow running your NUnit tests inside your ASP.NET application. This is used to allow testing inside an HttpContext without the hassles and pitfalls of trying to fake the context for a test. I use this test runner on my Sitecore projects to allow unit testing inside the Sitecore application.

This walks you through the steps of creating a custom Time field for when you only need the Time and not the Date.

Just like our VariableReplacement

"Encrypting View State Although MAC encoding helps prevent tampering with view state data, it does not prevent users from viewing the data. You can prevent people from viewing this data in two ways: by transmitting the page over SSL, and by encrypting the view state data. Requiring the page to be sent over SSL can help prevent data-packet sniffing and unauthorized data access by people who are not the intended recipients of the page. However, the user who requested the page can still view the view state data because SSL decrypts the page to display it in the browser. This is fine if you are not concerned about authorized users having access to view state data. However, in some cases, controls might use view state to store information that no users should have access to. For example, the page might contain a data-bound control that stores item identifiers (data keys) in view state. If those identifiers contain sensitive data, such as customer IDs, you should encrypt the view state data in addition to or instead of sending the page over SSL. To encrypt the data, set the page's ViewStateEncryptionMode property to true. If you store information in view state, you can use regular read and write techniques; the page handles all encryption and decryption for you. Encrypting view state data can affect the performance of your application. Therefore, do not use encryption unless you need it. Control State Encryption Controls that use control state can require that view state be encrypted by calling the RegisterRequiresViewStateEncryption method. If any control in the page requires that view state be encrypted, all view state in the page will be encrypted. Per-user View State Encoding If a Web site authenticates users, you can set the ViewStateUserKey property in the Page_Init event handler to associate the page's view state with a specific user. This helps prevent one-click attacks, in which a malicious user creates a valid, pre-filled Web page with view state from a pre

This is a custom processor for Page Editor data source locator for a multi-site solution

Completely remove the ASPX extension or add a custom one to Sitecore pages

Create a custom section in Sitecore to show the actual URL for a media item