Group items tagged

Sometimes it is required to get all Items in the database based on a given template. Iterating through the entire database may be a very expensive operation though. However in this particular case, we can resort to the Link database. Link database is used by Sitecore to resolve all the linking issues - what referrers and what references the Item has. And if an item is based on a template, it also counts as a reference from the item to the template. The solution then is very simple: get all the referrers for a given template item.

"' Set the mail server configuration Set objConfig=CreateObject("CDO.Configuration") objConfig.Fields.Item("http://schemas.microsoft.com/cdo/configuration/sendusing")=2 objConfig.Fields.Item("http://schemas.microsoft.com/cdo/configuration/smtpserver")="localhost" objConfig.Fields.Item("http://schemas.microsoft.com/cdo/configuration/smtpserverport") = 25 objConfig.Fields.Update Set objMail=CreateObject("CDO.Message") Set objMail.Configuration=objConfig objMail.From = fromemail objMail.To = toemail objMail.Subject = "Test Email" objMail.TextBody = "Test Email" objMail.Send"

You can use the PublishingSpider workflow action to publish the items referenced by the workflow item, including required ancestors of that item.

"I don't know if you can do it on-demand, but you can enable the option "Track Active Item in Solution Explorer" (options->Projects and Solutions) which will always select the active tab item in the solution explorer."

Extends a treelist to show the hierarchy of parent items in case multiple items in the list have the same name

"using (new SecurityDisabler()) 74 { 75 Item context = Sitecore.Context.Item; 76 context.Editing.BeginEdit(); 77 System.Web.Security.MembershipUser mUser = System.Web.Security.Membership.GetUser(user.Name); 78 mUser.ChangePassword(txtOldPassword.Text, txtNewPassword.Text); 79 context.Editing.EndEdit(); 80 } "

So by simply adding a workflow action before the Auto Publish action with the logic below, you will ensure that the relations will be published before the actual item:

PROBLEM:Users cannot create Hyperlink, File, and Image Library items in Workarea

jQuery plugin for one-directional scrolling with item based navigation support

Package ALL dependencies of items into an update package

fancy item selector (like facebook friends selector)

jQuery.suggest, a simple inline autosuggest jQuery plugin. It takes an array of terms as haystack and suggests the user the first item that matches what has been typed to this point. The suggestion is updated with every keystroke. Tab or Enter will accept the suggestion and update the input field accordingly.

The Sitecore Social Connected module contains several independent tools: Social Connector allows website visitors to log in your website using credentials from their social network accounts. Your website receives more information about the visitor from the social network profile. You can use it to personalize the website. Social Publishing allows posting automatic updates to the social networks along with publishing Sitecore items. Putting Like and Tweet buttons on the webpage. You can put the buttons as Sitecore controls and track users' activity using Sitecore analytics.

"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

Copy, cut and delete items in bulk!