As hard-core Notes Migrator for SharePoint users know, there are about five ways to migrate Notes documents to web pages in SharePoint 2007:
- HTML pages
- Basic pages
- Wiki pages
- Web Part pages
- Publishing pages
In our extensive regression testing with SharePoint 2010, we noticed that the rules have changed a few interesting ways. Here are four basic changes you should be aware of:
1. HTML pages have been “secured” – If you populate a SharePoint document library with migrated HTML pages, everything migrates correctly, but SharePoint does not display the pages the same way when a user clicks on one of them. Instead of displaying the page in the browser, SharePoint forces the user to download the HTML file and view it locally. This is annoying at a minimum, but if the file contains relative links to other images or attachments, they will not work at all when opened from a different location.
The reason for this is that Microsoft decided that displaying HTML files indiscriminately was a security risk and they added safeguards to prevent that by default. The remedy to this is to turn the new security feature off. In Central Administration, go to Manage Web Applications -> General Settings and select “Permissive” as your Browser File Handling Option.
Be sure to read the description on this option and make sure you understand the security implications. Going “Permissive” is really no less secure than what we had in SharePoint 2007, but if you have users you don’t trust uploading content to your site, you might be better off choosing a different type of page to migrate to.
2. Basic pages are gone… sort of – If you go to the Create menu in a typical SharePoint 2010 team site, you will see that there is no longer a “Basic Page” option. As described below, I think there is a good reason for it.
If you use Notes Migrator for SharePoint to generate a bunch of Basic pages, it actually does still work. Each page looks nice but all the window dressing is gone and you are stuck in read-only mode. Notice in the screen shot below that there is no Quick Launch menu and the Edit buttons are disabled.
Perhaps some of the new site templates I have not experimented with yet still expose the ‘Basic Page” construct, but I suggest that most of us move on to Wiki pages.
3. Wiki pages are king! – In SharePoint 2007, Wiki pages were a cute, but somewhat limited, list type that not many people used. In SharePoint 2010, they have become something that is greatly improved and now pretty ubiquitous. When you create a new “Page” using the Create menu in a team site, you are now creating a Wiki page. And the “Site Pages” library that (by default) holds pages that users create is now a Wiki Page Library.
Microsoft basically merged the concept of Basic pages, Wiki pages and Web Part pages into a single construct that is much more powerful – and much more user friendly – than before. Remember that crappy rich text editor in SharePoint 2007? Now the editor sizzles. End users can upload images and files and can even embed Web Parts in their rich content (similar to the way they used to embed OLE objects in their Windows applications).
NOTE: Don’t attempt to migrate to SharePoint 2010 Wiki Pages in Notes Migrator for SharePoint version 5.3. Somewhere between the 2010 beta and RTM, there was a breaking change in how one of the SharePoint APIs worked and we had to make a two line change to accommodate it in our product. Notes Migrator for SharePoint 5.3.1 fixes this issue which will RTM in a couple weeks. If you can’t wait that long, contact me through your Quest rep and we will get you a build.
4. Put your Assets in the right place – When migrating to any of the above page types, it has been common practice to put the associated images and attachments in a subfolder inside the same document library you were putting the pages in (described in this post). That’s not the 2010 way to do it, and there are some cases where it actually does not work out very well.
Page Libraries in particular are not really designed for holding binary files. Our tool will let you migrate attachments and images there, but the result is not always satisfying. For one thing, you loose some of the nice integration that you have between Office applications and “normal” document libraries. We have seen cases where Word will not open .doc files from a folder in a Page Library.
The right solution here is to put images and attachments in the “Site Assets” library, or whatever place the designer of your site template intended such things to go. As shown below, this matches perfectly what users will be encouraged to do when they upload new attachments while editing a new page. Putting images and attachments into different libraries is nothing new for Notes Migrator for SharePoint and the technique is pretty simple (described in this post).
I will have a lot more to say about SharePoint pages – especially Wiki pages – in future posts. Web Part pages and Publishing pages still exist as distinct page types and migrating to these work pretty much the same as they did in SharePoint 2007.