in

SharePoint Blogs

The Best Place for SharePoint-related Blogs

For The User

A blog for SharePoint users. If you are a SharePoint administrator or developer, feel free to read on but be warned I'll be covering stuff that may seem pretty basic to you. It's been my experience that getting started with and getting the most out of SharePoint as an end user isn't always an intuitive process. My goal is to provide information and content in the hopes of smoothing your path to becoming a master SharePoint user.

May 2008 - Posts

  • Be Vewy Vewy Quiet, We're Hunting Web Pawts...

    A while back a friend of mine was getting frustrated with a news site he was trying to get set up in MOSS and asked me for some help.  His issue seemed pretty straight-forward, he wanted to add an Announcements web part to the main page of the site but couldn't find the web part anywhere in the site's web part gallery to be added.  I'm a little embarrassed to say that the solution to our problem didn't immediately come to me, but at the same time when your brain is working in a certain direction it's all too easy to overlook the simple solutions.

    My first instinct was to check his site's Site Features and Site Collection Features in the Site Settings to see what was activated or deactivated.  His Enterprise features were enabled, as were his Standard features and Team Collaboration features.  So this wasn't a case of available functionality being disabled so that the web part couldn't be used.  Next I checked the file server of our SharePoint front end server to see if the files associated with the Announcements web part had been removed, which would prevent the web part from being in the site's gallery and could not find the files I was expecting to see.  It was at this point that I realize the folly of my actions and the fact that I was going about this situation all wrong.

    See, I was forgetting that there is no such thing as an Announcements web part in SharePoint. "But John!" you're saying... "What about the Announcements web part that is automagically added to my site's home page any time I create a new team collaboration site?" And that's the crux of the problem...what appears to be a web part specifically for Announcements (or a Calendar, or Linkset, etc) is actually a pretty general web part that SharePoint makes available anytime you create a new list within your SharePoint site.  This web part is added to your gallery to provide you with a view of your list's contents, and depending on the list template you used to create the list will format the lists contents in different ways.  Links will be shown hyperlinked, Announcements will be shown with headlines and summaries in chronological order, Calendars will be shown in a standard calendar format, and so on.

    My point is that to fix my friend's problem I didn't have to do anything more complex than create an Announcements list for his site; once I did that its associated web part appeared in the site's gallery and could be added to the page.  This is a pretty cool but often overlooked aspect of SharePoint, anytime you create a list SharePoint will automatically create a web part for that list which allows you to view its contents from somewhere other than the list's page itself.  And you can customize the data shown by that web part through the creation of custom views and filters for the list.  Pretty cool, huh?

  • A-B-P. Always Be Publishing

    "A-B-C. A-Always, B-Be, C-Closing. Always be closing, always be closing."

    These are the words of Blake, Alec Baldwin's character in the movie version of "Glengarry Glen Ross" (http://www.imdb.com/title/tt0104348), as he talks to (more like rants) a group of real estate salesmen about the art of deal.  This scene popped into my head a few days ago as I was working on a customized Internet-facing publishing site in MOSS.  Why? Because when it comes to getting new content into your publishing site, it's "A-B-P. Always Be Publishing."

    Why is this important?  If you don't, your updates won't show up and your rank and file users won't be able to see them, it's just that simple.  MOSS's content management system for publishing sites is configured so that unless your content has been checked in, published, and approved it will not be visible to anyone not in your site's authoring or approval groups.

    If you're editing content in a MOSS publishing site (often used for Internet facing websites), always make sure that you have published all of your updates.  This includes, but is not limited to, changes to your master pages, page layouts, pages, lists, web parts, and much more.  If you are working on items that require approval, you must confirm that workflows for those approvals have been started and completed in order for them to be visible to all of your site's users. (NOTE: with publishing sites you can also schedule content to start and end on specified dates, which also change the visibility of your content) 

    How do you do that?  There are a few different techniques I recommend using; you should try to do at least one of them every time you update your site and should probably do most of them together.

    • Use the MOSS Check for Unpublished Items tool:
      1. Make sure the Authoring Toolbar is displayed for your site (you should see a menu across the top of the page showing the page's version, status, publication start date and some pulldown menus)
      2. Click the Tools pulldown menu and select the Check for Unpublished Items option.
      3. You will see a message in the Authoring Toolbar saying that it is checking for unpublished items.
      4. If there are any, you will see a message stating !Unpublished items are detected on the page.  In the message, click the link full report to open a report of the items found.
      5. For each item in the list, initiate the publishing process so that they can be displayed to all users
    • Log in as an anonymous user, or as a user with limited rights to the site.  Then check the page for your new content.  If you don't see it, it needs to be published.  One trick I like to use is to make my updates in Internet Explorer and verify my content as an anonymous user in a different browser, like FireFox. This allows me to make sure everything's getting published and at the same time make sure that things look good in non-IE browsers as well.
    • Andrew Connell's STSADM Custom Commands (http://www.andrewconnell.com/blog/articles/MossStsadmWcmCommands.aspx) includes an option to publish all items in a list, which is great when you've just uploaded a ton of documents or images into a list or directory and don't want to have to go through every single workflow for every single item. Just point the tool at the list and it will publish them all for you (NOTE: you will need to be a SharePoint administrator to install and run the tool).

    So the next time you're authoring your MOSS publishing site and can't figure out why your new content isn't showing up for your users, check to make sure it's published.  And put that coffee down.  Coffee's for publishers only.


Need SharePoint Training? Attend a SharePoint Bootcamp!

Posts (c) their respective authors. Everything else (c) 2007 SharePoint Experts