At the SharePoint Conference 2011 I had a discussion with Christian Ståhl and Laura Curtis if it will be possible to cleanup old versions in SharePoint using a script or command line application. I thought to myself that this should be a big task to accomplish but a useful. The slow way to clean up old versions is to loop through all the site collections, webs, lists and items. From each item check the versions and delete them. In SharePoint 2010 Server there is a much smarter way to do this by using a helper that exists in SharePoint Server. The class I’m talking about is called ContentIterator and can be found in Microsoft.SharePoint.Server.Utilities namespace.
The smart thing about the ContentIterator it prevents SharePoint from blocking the database with requests. The only side effect of this is that items in the meantime can be modified because this method is not thread safe.[Read more]
SharePoint Designer is a great tool for prototyping but it can really mess up your installation. I want to show a new way / old way how customized form could be make centralised manageable.
For example if you want to create a list form that has certain columns visible to users with a special permission. The fastest way to get there is to create a custom list form is in SharePoint Designer. A tutorial for this can be found at Microsoft Create a custom list form using SharePoint Designer – SharePoint ….
Customising form works great as long as you have a single list and a single form in your portal. If someone saved the list as template and created new instance, the problem start to begin when something needs to be changed in the form.[Read more]
* Update: The official description to this problem can be found in the Knowledgebase Article KB2596519. There is also a hotfix avaliable that can be downloaded here. A big thanks to the Microsoft Support Team. *
One of my customers stumbles upon a strange bug in SharePoint that relies on the list views in combination with meta data and the meta data Navigation. In a special case the list view returns a false result.[Read more]
So this blog post is the result of a funny story happened today. Since the last couple of weeks I daily check out awwwards and css design awards both sites present all the latest and best web designs in the web. Today the site of the day was deep time by Jamie Brightmore (@jaybee). The site is a really great user interface and shows the possibilities in current web design. Deep Time is an interactive info graphic built for the modern web and iPad. It offers a visual way to explore the various stages of the Earth’s history using a 12 hour clock analogy.
I liked the design and so I published it to Facebook. A couple of minutes later I was messaged by a friend that the web site won’t open in IE9. I was not really amused because awwwards and css design awards nominated web sites normally work in all mayor and latest version of browser. I wrote a comment about the deep time web site at awwwards and twittered Jaime Brightmore that I don’t like when site were nominated that don’t support all latest browser versions.
Jaime replied that he have tested it in IE9 and the animation there was quite slow and svg wasn’t loaded correct. The problem Jaime had is one that many people have and especially when they are not using windows every day. It is also easy to solve.
Jaime as a web designer and developer use a make and made the testing in a VmWare and used IE9, but not the 32-bit Version he installed and tested it in 64 bit. The 64 Bit Version is not intended to be used to browse the web it is for development purpose the same way it behaves like with Microsoft Office. The intention behind the 64 Bit Versions is to allow developer all around the world to upgrade their add-ons and plugins to 64 Bit.
In Windows the 64 Bit Version of Internet Explorer 9 is not intended to be used for normal web surfing. Eric Law from Microsoft has a Q&A for IE9 64 bit vs. 32 bit which is worth reading. The 32 Bit Version and the 64 Bit Version are both installed on Windows but the 64 Bit version is hidden to normal users with reason.
At the end I told Jaime that I wanted to give it a try on IE9 and test his web site. He sent me a link because he blocked IE Browsers completely because of the poor performance and different false look. The result was that all worked the same way as it worked in Google Chrome or Safari. Not one pixel was different in IE compared to other browsers and the performance was really amazing. All was tested with the 32 bit version of the Microsoft Browser and at the end he removed the blocking of IE9 and changed it to IE8 which somehow makes sense.
Before you develop a new web project consider the following things that you should know:
First of all for testing only use the 32 Bit Version of Internet Explorer. By pressing the F12 key the developer tools will be shown and the Browser Version can be configured to IE9, IE8 and IE7. That switch will render the site natively in the older versions and the tests matches one to one with the older versions.
The new developer tools are really handy and let fire bug to look old, but still cannot compete to the Safari Developer tools what I like most.
I think Microsoft has done a great job on the new version of Internet Explorer. Internet Explorer is much better than its reputation.
One of the most powerful web parts since SharePoint 2007 is the Content Query Web Part but it has some strange limitations. To be more specific not the web part has the limitation it seems more that SharePoint has, from my point of view, a big architectural failure. Let me explain why.[Read more]
In modern web design many sites use web fonts. Nearly since the beginning of the Internet there were always intentions to bring desktop fonts to the web. Nowadays the support for web typography in modern browser is in really big. Netscape introduced the <font> Tag in 1995 as a first attempt to bring different fonts to the web. Internet Explorer 4 was the first browser as far as I know that allows font embedding back in 1997.
In general some really good articles about web typography can be found on http://www.alistapart.com/topics/design/web-fonts/ which is worth reading to deep dive into web typography.[Read more]
From an end user perspective it looks like there is only one field type that creates only a single taxonomy field in sharepoint; but this is not the whole story behind managed metadata fields. If a managed metadata field will be created SharePoint creates two fields instead. For this post I create a field called “TaxTest” which creates the field itself and a field “TaxTest_0”. I will use this field name for reference.
Let’s take a closer look on both fields that was created
- “TaxTest” Field is type of “TaxonomyFieldType”
- “TaxTest_0” field is type of “Multiple lines of text”
The TaxTest field is basically a lookup field. The target to look up is a hidden list in every site collection called TaxonomyHiddenList. This list only exists once per site collection and stores ever Managed Metadata term that ever was used in your site collection. The list cannot be found in SharePoint because it is a hidden list but can be located using the following URL pattern:
http://<yourserver>/<sitecollection root>/Lists/TaxonomyHiddenList or root site collection.
Field values stored in this field has also the same pattern as lookup fields and look like this: “1;#Test Term”
The “TaxTest_0” field will only store key/value pairs which looks like this:
<Term value from Taxonomy Store>|<Term Guid from Taxonomy Store>
That’s all for now from these fields I will continue later on with this.[Read more]
Imaging the following situation where you want to export an XSLT List View web part and embed it on a different site. So the good thing about this it’s easy to accomplish. I came across a great article posted by Glyn on his blog how to export an xslt viewer web part. He shows in his article some really great insight how the xslt viewer web part can be exported. The only thing he left out is that you can export XSLT List View web parts using SharePoint Designer. This feature is really well hidden in the ribbon.
In SharePoint Designer simply select the XSLT List View web part you want to export. In the Ribbon you will find a specific menu for this web part. Ribbon for the web part comes up you can select inside the “Web Part” Tab. In the far right area of the ribbon you will find two really helpful menus.
The “To Site Gallery” option will copy the web part to your site collection web part gallery. You will also be asked how you want to name your web part, description and you will be able to change properties.
Another option to select is if you want to use it relative to any site where the web part will be embedded or get data only from the current site.
The “To File” option will open the download dialog to store the web part and the configuration to a file.
As you see it’s easy to export a XSLT list view web part and use it the way you like. You can also cross embed lists from one web into another.