Woody Windischman

May-52011

The Sanity Point is Now On SharePoint 2010

wpe4It's About Time!

I'm pleased to announce that The Sanity Point is now at long last running on SharePoint 2010. Specifically, Search Server 2010 Express. I confess, this took a lot longer than I had planned.

Though the big stumbling blocks had to do with migrating my content, and getting the Community Kit for SharePoint - Enhanced Blog Edition (CKS:EBE) to work correctly, I can't totally blame the tools. My life has been pretty busy these last few months, so my troubleshooting time (along with writing time) was quite limited. Still, look for a post describing my new environment and the actual trials and tribulations of getting it set up in the near future, as there are definitely some "gotchas".

In the mean time, thanks for your patience, and I'll see y'all at Tech-Ed in Atlanta!

*UPDATE*

There is apparently yet another glitch with CKS:EBE. Sometimes, post links aren't working. It doesn't happen consistently (otherwise I would have caught it). Please bear with me as I try to work out this last kink. Thanks for your patience!


Oct-202010

Simulating Explorer View in SharePoint 2010

Getting back what was taken…

SharePoint 2010 is leaps and bounds better than any previous version in many ways. However, there are areas where some folks feel a little bit was lost in the translation. One of these areas was the ability to create a view of a document library that actually used Windows Explorer “behind the scenes” to let you perform drag and drop style file manipulation. For SharePoint 2010, the Explorer View was replaced with an icon in the Library toolbar to “Open with Explorer”. This opens your library in a separate window, using the full Windows Explorer.

Note: Depending on your window size, the labels for Outlook, Excel, and Explorer may not be displayed.

While there are a lot of reasons the Explorer View option for Web Parts was taken out, the desire for that feature is still going strong. Although it isn’t exactly the same, the following workaround will get you pretty close to the old Explorer View. This is accomplished through a venerable web part that has been a part of SharePoint since the very beginning – the Page Viewer. A page viewer, in essence, is an HTML IFrame that you control through the SharePoint interface. It is capable of displaying almost any content that you can point a browser at.

To add a page viewer, start by editing a SharePoint page. Either in a Wiki Content zone or a Web Part zone (depending on your page type), select Insert, and click the Web Part tool in the ribbon, as shown below:

Select the Page Viewer part from the Media and Content category, and click the Add button. In the web part’s context menu, select “Edit Web Part”. Change the view type to Folder, and enter the UNC path to the document library you want to view (e.g. \\shareppointserver\site\library), as shown here:

Click OK or Apply, and voila! You will now have an explorer window on your page, that points to your document library. You can Edit the properties to give it a more reasonable title, or to make it an appropriate size for the page at hand.

There are a couple of caveats when doing this, however. The biggest one being that you don’t want to use this function on an Internet Facing web site, or on a population with browsers other than Internet Explorer. The other thing is, like the original Explorer view, you can’t control the window settings your users may have. Thus each person may get a slightly different experience.

Still, if you miss the Explorer View of a document library for embedding in a page, this is the only way I have found to make it happen.


Nov-272009

FeedBurner Under Control

MCBD07000_0000[1]The Fix is In, Thanks to Tom Resing

I have great news, thanks to fellow SharePointer Tom Resing. In my previous post I mentioned the problems the Community Kit for SharePoint:Enhanced Blog Edition has with the new link tracking parameters FeedBurner just started adding to their links.

In that post, I talked about the trials and tribulations of trying to get CKS:EBE working by installing an updated version. It turns out there was another approach to the problem. Although Google made the change to FeedBurner effective by default, Tom pointed out that they do offer an option to turn it off.

The Quick Fix

So, for those of you using both FeedBurner and CKS:EBE, here's the scoop. On the left menu in your FeedBurner Feed Stats Dashboard, in the Services section, is an option called "Configure Stats":

image

When you select Configure Stats, you have a section called "Reach", which has several options. You need to uncheck the box for "Track Clicks as a traffic source in Google Analytics":

image

That's all there is to it! Save the settings, and everything should be back to "normal".

Of course, it would have been nice if Google had posted a more conspicuous notice that they were making this change, and where it could be configured. It would have been even nicer if they had made the change "opt in" instead of "opt out".

Nevertheless, what's done is done. You should now be able to click through from my RSS feed directly to the articles you are interested in.

I apologize for any inconvenience.


Nov-252009

Burned by FeedBurner

MCj04314980000[1]At Least They Didn't Burn the Turkey

Just a quick note before I run off for the Thanksgiving holiday (USA). If you have been a subscriber to my RSS feed, you may have noticed a problem clicking through to my blog posts lately. This is because of a change that FeedBurner made a few weeks ago. They added extra parameter information to the connection string of links back to the blog.

This is theoretically a good thing, as it allows site logging to better determine where visitors are coming from. However, this blog uses the Community Kit for SharePoint: Enhanced Blogging Edition (CKS:EBE). The way CKS:EBE handles URLs doesn't allow it to correctly interpret these additional parameters. This resulted in broken page displays. You can still eventually navigate back to the right page, but it isn't as convenient as it should be.

I have just tested a patched version of CKS:EBE to resolve that problem. While the patch for the FeedBurner problem seems to work correctly, there are significant issues with other changes to the patched build of CKS:EBE. I noticed that my tag cloud was no longer resizing the keyword links to their proportions, for example, and there were major authentication problems. These glitches are bad enough that I decided to retract the update.

I apologize for the inconvenience. Rest assured, I'll continue working on getting links from FeedBurner working (without breaking everything else).

In the mean time, Have a Happy Turkey Day!