Group items tagged

- 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.

With the program Check Host you can easily monitor a server or the services of a server. Therefore define which host or ip address should be monitored. Additionally you can choose the check method: either with a ping or by establishing a socket connection (optionally TCP or UDP) on any port.

jQuery.carouFredSel is a plugin that turns any kind of HTML element into an infinite, circular carousel. It can scroll one or multiple items simultaneously, horizontal or vertical, automatically, by pressing buttons or keys on the keyboard.

Videola is an enterprise-level video management system and video delivery platform. It allows you to create paid-access or free-access video websites which can serve video to the desktop, mobile, or television-based devices. Create your own Netflix On-Demand style (subscription), Hulu style (ad supported), or Blockbuster / Amazon style (rental) streaming video websites with your own video content.

"Cross Site Request Forgery (CSRF) This article assumes you already understand what CSRF is and how it works. If you don't, do a quick Google search and it will clear it up. CSRF can be done using POST or GET, but GET is much easier to implement. By default, ASP.Net forms and other functionality work via the POST method. If we could submit a GET instead of a POST it would open up the attack surface a great deal. No longer do we need someone to visit a page with a form on it, but we could actually embed the GET request (a link) in emails or other medium. Fortunately for the attacker, unfortunately for the developer, .Net uses Value Shadowing for its controls. This means all server side controls, ie. Viewstate, EventValidation, EventCommand, EventArguments, etc.. It is possible to take the values that would be submitted as part of the form and just add them to the Querystring instead. Now there is a GET request that is comparable to the POST request. ASP.Net Webforms does not check whether a post back comes from GET or POST. The one thing to keep in mind is that the URL in a GET is limited in size. If the form is large and the viewstate is very large, this could block this technique from working. This depends on the way the application is configured (more later)."

""Image corrupt or truncated: " It only appears in Firebug's console in Firefox (it did not show up in IE or Chrome)."

jQuery plugin that will sort any nodetype by it's text- or attribute value, or by that of one of it's children.

"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

ELMAH (Error Logging Modules and Handlers) is an application-wide error logging facility that is completely pluggable. It can be dynamically added to a running ASP.NET web application, or even all ASP.NET web applications on a machine, without any need for re-compilation or re-deployment.

This is an agile HTML parser that builds a read/write DOM and supports plain XPATH or XSLT (you actually don't HAVE to understand XPATH nor XSLT to use it, don't worry...). It is a .NET code library that allows you to parse "out of the web" HTML files. The parser is very tolerant with "real world" malformed HTML. The object model is very similar to what proposes System.Xml, but for HTML documents (or streams).

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.

"Restore or repair the database"

"Event ID 490 is logged, and you receive the following error message when you try to mount the mailbox store or the public store in Exchange Server: "ID No: c1041724""

"Mailbox Store or a Public Store May Not Mount with Error -344"

"Moving an Exchange Mailbox Database to Another Server or Storage Group"

"IE8 - 'eval' is null or not an object"

"Visio 2007 crashes, or the Visio.exe process is still running after you exit Visio 2007 on a Windows Vista-based computer"

This happened to me all the time when I was running Vista

The Sitecore License Expiration Module 2.0 checks the expiration date of the Sitecore license. It shows a Content Editor Warning message or/and send email to notify when the Sitecore license is about to expire.

Everything you thought you knew about the semantics of navigation may be wrong!