I was recently tasked with installing an update to a live SharePoint 2013 extranet site that is actively used by staff as well as external clients. Since the update caused our extranet site to be unavailable for several hours, I found myself wishing for a simple but effective way to alert all SharePoint 2013 site users about upcoming scheduled maintenance. I could send e-mails, but prefer not to do so since we have quite a few people who have access to the SharePoint site, but very few active users. Instead of sending out alerts to more than one hundred employees letting them know that a service they may or may not use will be unavailable, I wanted to publish a notice to the SharePoint site itself.
I need to find a way to publish a notice of anticipated service interruptions on every page of my SharePoint 2013 site. This seemed simple enough at first, until I began to consider the fact that I have multiple site collections, each with multiple sites in my extranet Web Application. Users access the site from a wide variety of links, so publishing a notice on the home page would not be effective. Every site has unique permissions, depending on which users need access to the site’s contents, so publishing announcements on a site-by-site basis would be a real chore.
I am using a pretty generic out-of-the-box SharePoint 2013 installation, so my site is using the default Seattle master pages. I thought about customizing the master pages to include a message, but I would have to do the same for every site collection in my Web Application, which seems to be more trouble than it’s probably worth.
Meeting Workspaces are a great way to collaborate with team members. They provide a place to store all of the documents, agenda items, attendee information, and other important meeting notes across multiple meetings. Microsoft Outlook can be used to generate new meeting instances for new dates, and all attendees can be given a quick link directly to the site to review pertinent information before and after the meeting is over.
Unfortunately, both Microsoft Outlook and SharePoint have a common problem: There are usually many different ways to achieve a task, but only one way is the “right” way that actually works as anticipated. Meeting Workspaces have the same problem.
Several times now I’ve been asked to help resolve a problem a colleague was having with Meeting Workspaces. In each case, my colleague had set up a Meeting Workspace and created multiple meeting instances (dates) and sent out the invitations to attendees. All appeared to be working correctly. But as my colleague went in to try to update specific information related to a certain meeting instance (such as the agenda items), we discovered that the meeting-specific information was not being displayed on the correct meeting dates. If my colleague added an item to the agenda for the second, third, fourth, etc. meeting, it wouldn’t show up. But when we went back to the first meeting in the series, we found the new agenda item to be listed there with all agenda items for all instances of the meeting.
All of the Meeting Workspaces settings were correct, and there was nothing to indicate what the problem might be. My colleague had successfully created other Meeting Workspaces following the same procedures, and each of those Meeting Workspaces was working correctly.
It took some time, but eventually I discovered the apparent cause of the error. In each of the Meeting Workspaces that was working properly, the URL had no spaces in it (Keep in mind that a space in a URL may be displayed in your address bar by the character string “%20”). In each of the Meeting Workspaces that did not work, the URL had spaces (%20) in it. So, for example, a Meeting Workspace with the URL of http://sharepointserver/team/MeetingWorkspace would work correctly, while a Meeting Workspace with the URL of http://sharepointserver/team/Meeting%20Workspace would not list the meeting-specific information on the correct meeting date.
NOTE: The two hyperlinks used above are examples only and do not point to real sites.
I’ve been using a linux-based Asus Eee PC (p701) for several years now, and one of my favorite features available is the desktop wallpaper “slideshow” option. I can set up my computer to randomly display a new desktop wallpaper as often as I want. All I have to do is point to the folder(s) the images are stored in and set the frequency, and viola my desktop wallpaper changes “automagically.”
I’ve almost given up on wallpapers for my home and office Windows machines, however. While it’s certainly not hard to change the desktop wallpaper, it’s not something I like to think about. To be honest, the desktop is always covered by the applications I’m working in, so I rarely even think about it. But a few months ago, I stumbled across the Microsoft Digital Photography Winter Fun Pack 2003. While most of the features are uninteresting to me, one of them caught my eye. The Winter Wallpaper Changer feature automatically changes your desktop wallpaper anywhere from once every 15 minutes to once a week. You can point the program to whatever folder you want that contains the background images. Even better, you can set it up so that on certain days (someone’s birthday, a holiday, or whatever), you can choose from a different set of wallpaper images!
I installed this application, and was immediately thrilled with how it worked. I like my wallpaper to change very frequently, so I had my wallpaper changed every fifteen minutes throughout the day. I never knew how easy it would be to brighten up my day just by changing my computer’s wallpaper!
That being said, let me describe one of the first problems I encountered in my new programming scenario:
I am building a website to allow users to add, edit, and delete items in a list of events. I am using an ASP.NET/Visual Studio MultiView control to manage the process flow for selecting and editing the events. The first view that the user sees is a GridView control displaying the complete list of events in the database.
Listgarden is a very powerful RSS creation and management tool that runs on Windows, Mac, and Linux platforms, and can be configured as a Web-based application.
For those of you who subscribe to all of my feeds, let me apologize…I know that I’ve mentioned Listgarden several times: in this blog, the Lockworld Herald News, and my Resources feed.
I think the program deserves all of these mentions, however, because it is so versatile and so simple. Without any knowledge of RSS or XML structure or rules, you can create and edit as many feeds as you want to. You have the options of creating the feeds as local files on your computer, or uploaded to your FTP server (or both). My favorite feature of Listgarden is that you can optionally export an HTML version of your feed containing some or all of your feed items as a Web-based file. This can allow you to offer a preview of your latest feed items to your site visitors or an alternate way to view “what’s new” on your site. Read more»
It’s hard to believe, but The Web for You is already a year old! I know it’s been a very interesting year for me as I tried my hand at blogging for the first time, and I hope that you have found some useful tips, tricks, and ideas along the way. For anyone who might be a new reader, I’d like to take a short moment to review some of the more interesting posts from the past year. Read more»