SharePoint Joel's SharePoint Land

7/16/2008

How can I easily force the SharePoint Web Part Maintenance Page?

Append ?contents=1 to your querystring. Example: http://www.foo.com/default.aspx?contents=1 Try it. It's cool. Thanks Shane Young for pointing this out in our Survival class. :)

We were talking in class about deleting closed web parts... it's a pain to try to get to the UI where you can delete "closed web parts." I find that most page perf issues I see are related to bad web parts that are actually closed.

I'm not a fan of any closed web parts. I think it's a poor feature. Just my 2 cents. The idea of closing web parts for private views... just didn't work like it was designed and has more downsides than up.

Posted at 10:40 AM by Joel Oleson | Category: Performance and Optimization | Permalink | Email this Post | Comments (5)

Comments

How about a hidden Site Settings page?

If the Site Settings menu has been hidden you can go to it similiarly by using "http://www.foo.com/default.aspx?ToolPaneView=2" as well. Devs sometimes hide this through CSS file modifications.

at 7/16/2008 12:24 PM

Closed Web Parts = bad news

I agree - I have seen more than one example of poorly performing pages with multiple closed Web Parts. My favorite had literally DOZENS of closed Web Parts and the client couldn’t understand why a page with 1 Web Part would load so slow.

at 7/16/2008 2:20 PM

Closed Web Parts = Class SharePoint Issue

We see this issue all the time so we made a screencast about it. It is not uncommon to find 12,15 or 20 closed web parts on a single page.

http://blog.sharepointhosting.com/Lists/Posts/Post.aspx?ID=55

at 7/17/2008 1:44 PM

Closing web parts...

Closing web parts just confuses the average punter. Not worth the trouble.

contents=1 has helped me get out of many tricky spots with bad web parts. Especially during migrations.

at 7/22/2008 7:02 PM

Question about BreadCrumb Navigation

I know this is not the right thread but can someone point out to me where to go to resolve this annoying issue:

In a WSS environment, if you try to creat:

Top level site
   Subsite1 >> another site collection sub site 1a
   Subsite2
   ...

Now when you are at subsite 1a, if you look at the breadcrumb navigation, you won't know which tab (subsite 1, 2,..) you are on currently. A minor but annoying usability issues...Any pointers would be appreciated.

samir88@gmail.com

at 8/1/2008 2:53 PM

Add Comment

Title

Body *

Please include your name in the body as well for the display. Feel free to include links to blogs, etc...

CommentUrl

Do you love SharePoint? *

What is Todays Date? (Anti Spam) *

Attachments