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.

- Panels are HTML Content (can be anything). - Multiple AnythingSliders allowable per-page. - Infinite/Continuous sliding (always slides in the direction you are going, even at "last" slide). - Optionally resize each panel (specified per panel in css). - Optional Next / Previous Panel Arrows. - Use keyboard navigation or tabs that are built and added dynamically (any number of panels). - Link to specific slides or go forward or back one slide from static text links - go to Slide 4 (Quote #2) in second example. - Each panel has a hashtag (can link directly to specific panels). - Optional custom function for formatting navigation text. - Auto-playing slideshow (optional feature, can start playing or stopped) - Pauses playing YouTube videos when not in view and resumes them when in view (only in non-IE browsers & if files are hosted on the web). - Pauses slideshow on hover (optional). - Optionally play the slideshow once through, stopping on the last page.

By default, all popular Web browsers assume the HTTP protocol. In doing so, the software prepends the 'http://' onto the requested URL and automatically connect to the HTTP server on port 80. Why then do many pages explictly set http on all hypertext links? Surely it is easier to type "domain.com" than "http://domain.com". HTTP is also deprecated due to the ever-evolving web: The HyperText Transfer Protocol is no longer used to transfer hypertext. It is increasingly becoming used a means to transfer any content over port 80. Thus the definition "http" no longer means anything in the context of a URL since you are unlikely to be requesting hypertext. As the web evolves, next generation protocols will begin to replace http. By explicitly using "http://domain.com" in your links you are forcing your viewers of the future into using an obsolete protocol. By using "//domain.com" you will guarantee the protocol of tomorrow will work with your pages of today. Succinctly, use of the http protocol is redundant and time consuming to communicate. The internet, media, and society are all better off without it.

This blog post describes how you can validate that users do not create internal links to items with no layout details

Remove outline when clicking a image link: a { outline: none; }

Automatic "Top of Page" link added to page

"Manipulating Sitecore Links"

"Sitecore 6 Link Management"

jQuery browser history / deep-linking

A common problem

A free light weight jQuery plugin that enables you to display related information with the hovered label, link, or any html element of your choice.

"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

"External Links Tracker module"

Scrolling down a page will reveal an unobtrusive 'Back to Top' link

A New Way of Linking

You can use content parts to edit a portion of a site theme with a custom message, link list, or other less dynamic content.

Click a link and it will slide the page over and put in new content

C5 provides functionality and data structures not provided by the standard .Net System.Collections.Generic namespace, such as persistent tree data structures, heap based priority queues, hash indexed array lists and linked lists, and events on collection changes