#SharePoint - An Enterprise Solution for What? - More pre-blogspot than pre-posterous. Issue with Web capture webpart configuration. SharePoint 2007 RSS Aggregation Web Part - Eric Shupps. SharePoint RSS Reader – Authenticated Feeds. If you are trying to setup a blog in SharePoint and want to aggregate its feed to a parent site, you’ll find that if you’re using NTLM you’ll get the following error: The RSS webpart does not support authenticated feeds This seems frustrating at first as you begin to wonder why you can create a blog, add RSS feed viewers, but can’t combine the two.
Basically this appears to come down to an authentication issue, and NTLM’s lack of ability to delegate credentials. The solution: Kerberos, and what appears to be a very simple solution at that. Basically just change the default Authentication Provider in SharePoint Central admin to Negotiate (Kerberos), use SetSPN to register an SPN for your App Pool account on your domain controller and allow that App Pool account to delegate through “trusted through delegation.” More details on this can be found at: Mark Arend: RSS Viewer web part and authenticated feeds Credentials and Delegation The download for the setspn tool for Server 2003 is at:
List of MOSS 2007 ActiveX controls (created searching the visible code) - Jose Barreto's Blog. I was looking for a list for all ActiveX controls used by Microsoft Office SharePoint Server (MOSS) 2007, but it seems like this list is not available at this time. The best references I could find was the SharePoint team blog post on web browser compatibility at the documentation on browser compatibility at and the Client Side API reference at However, each one of those misses at least a few of the controls. Web browser compatibility is, by the way, was my main motivation to working on this list. I need to figure out what features would be missing if you're running Firefox or Safari. For this reason, I am also trying to list what happens in those clients that do not support these ActiveX controls and what possible workarounds exist. PersonalSiteServer Files: None?
Share photos on twitter.
Updating Content Types and Site Columns That Were Deployed as a Feature - Becky Bertram's Blog. How many times have you come across this scenario? You create several Site Columns as well as a Content Type or two in your Feature. Then you want to update it. Since you deployed it via a Feature (as opposed to editing it in the browser), being a good developer, you decide you want to execute your update through a Feature as well. However, you run into several problems: When you deactivate your Feature, it keeps some Site Columns and deletes other ones.You notice some of the Site Columns and Content Types are still hanging around in the lists you applied them to, even after you deactivated your Feature.You try doing an in-place upgrade of your Feature, and nothing happens; everything looks exactly like before.
The columns in your Content Type haven't changed or anything. This can be very confusing and aggravating, and this is a scenario I've walked through with several clients. Deactivating Your FeatureWhat happens when you deactivate your feature? Using calculated columns to write HTML " Path to SharePoint. Update [6/8/2009]: A new version of the script is now available, more details here. Updates I am now expanding the scope of this method: - list views (flat views and expanded grouping): this article - list views (collapsed grouping): this article - display forms (DispForm.aspx): published on 10/01/2008- calendar views: published on 11/15/2008 - using calculated columns to write scripts: published on 2/26/2009 - preview panes: added on 7/9/2009 - filters: not published yet Also note the troubleshooting section.
Update [09/10/2008] I have added a few lines to the initial script to address the case of collapsed views. Also, see my note at the end of this post. Your feedback is important to me. Big thanks to Fernando, Jeff and the others who reported the limitations of the initial version! A technical note: considering that 1/ the script is generic and 2/ it may still evolve in the future, a good practice is to store it in a separate text file on your site.
Let’s take a look at our list: 2. Toggle Quick Launch | SharePoint. This article the third in The Power of Content Editor WebPart series. Other parts: Armed with knowledge about locating and getting to the object we can start some more serious DOM manipulation. In this article we’ll be expanding the SharePoint’s working area by hiding the Quick Launch bar. There are already JavaScripts available for showing or hiding Quick Launch, let’s do this example anyway to show how to do it yourself and additional we’ll be "injecting" some HTML to certain DOM element. Our objective is as follows: So let’s insert the webpart. After inserting the Content Editor WebPart into page, let’s make this in two steps. Showing / Hiding Quick Launch We can show or hide Quick Launch (as well as any other DOM element in the page) by using CSS property display.
You will see the selected element with a blue border. In the case above we can still select a node higher in the nested hierarchy. When we’ve selected the table row, we’ve gone too far up. Perfect. And it would do the trick. Hide New / Actions / Upload / Settings menus in SharePoint Lists / document libraries.