I’ve previously posted both a list of Content Types as well as a list of Fields that appear in SharePoint 2007 and 2010. But what if you want to find out what Fields a Content Type uses? Here is a (hopefully) complete list of SharePoint 2007 Content Types and associated Fields.
I’ve previously posted PowerShell scripts that allow you to extract Content Types or Fields from a SharePoint site. But last week a commenter by the named Jeff posed a valid question. What if I want to extract all Content Types in a SharePoint site, and show the associated Fields for each of them?
I'm currently working on creating some custom discussion boards in SharePoint 2007 for a client. With that comes creation of features and content types, which in turn requires GUIDs to be generated. Generating a GUID in Visual Studio is easy. Just click Tools on the menu, followed by Create GUID. So what's the big deal?
When creating a bunch of content types I find that it becomes cumbersome to click the menu, copy a GUID, then paste it into the document before finally removing braces and dashes. So I've created two short macros to speed up the process with simple keyboard shortcuts. This is mostly a reminder for myself so I remember how to do this next time I'm setting up a new Dev environment, but I'm sure it can come in handy for someone else as well.
Sometimes you need to change the properties of a Web Part without browsing to the page itself and set it. There could be numerous reasons as to why you would want or need to do this. A while back I created a really simple redirect web part for one of my clients. It had two custom properties, EnableRedirect and Url. If EnableRedirect was true, it would redirect the user to the specified Url. Obviously, if you want to change either of these properties while the EnableRedirect is true, that's going to be a problem.
Fast forward and the redirect web parts need to be changed and/or disabled. Obviously we can't navigate to the page and just change it, because the page will redirect you. But it can be done relatively easy using PowerShell.
A colleague of mine, lets call him Jereme, came across this and he suggested I post it on my blog, so here goes. One of his clients where having issues with one of their search scopes. Whenever a user would try to do a search with one of the custom scopes, they would receive an error saying "Your search cannot be completed because of a service error. Try your search again or contact your administrator for more information.". It only occurred with this one search scope.