Closing (or X’ing) is not Deleting Webparts
SharePoint WebPart pages often have ‘Closed’ WebParts being loaded everytime the page loads because the page editor may have incorrectly ‘closed’ a WebPart rather than ‘deleting’ the WebPart. (Or never removes it after closing it.)
Everyone who works with SharePoint sees and most likely runs into this (often :().
This is by no means ‘new’. In fact it’s been around since back in the 2003 days and here are a couple good posts that already exist on it:
- Etc etc
The point being you can easily fix this for all your pages by adding the ?contents=1 to each page and managing it that way (see linked articles above for description of how this works, or my previous post: https://sharepointkb.wordpress.com/2008/07/25/sharepoint-webpart-error/) or you can add each closed webpart individually (using the advanced webpart pane). The why this is a good thing is pretty straight forward, it provides you with a way to restore webparts just in case you didn’t mean to ‘remove’ them from the page.
The why you should go through ALL of your landing pages, home pages, or often updated pages and do this ‘clean up’ work *regularly* (until it’s no longer an issue) is because it still retrieves these webparts (and all their lovely properties) when it loads the page, it just doesn’t render them to the end user. This makes for much slower response rates and can be easily improved.
So seriously, if you read this and haven’t checked how many closed webparts are on your pages (in the past month) go do that right now and clean them up. Set up a scheduled task each week to do this, write a script, or train people to manage page content so that it doesn’t happen anymore. Do anything but leave it alone. Then tell other people, and make this one of those checks you do when working with pages. You will be surprised by how much it can often help page load times.
Let’s also hope that Microsoft makes these ‘closed’ parts expire in the future… since recycling bin already does this. *nudge nudge* *wink wink* to MS.
Hope this helps,