Sharepoint – create blank page with only webpart

sharepointsharepoint-2007

A client has asked that I create a series of filters on a list, with some heavily customised output. To get the output correct I'll need to style a content query webpart using XSL – which is fine, that's pretty simple.

However, my main problem is how to apply multiple filters to the webpart. I don't know how to have one webpart insert parameters into a content query webpart, so my solution was to use Ajax to load seperate pages (containing webparts) into the page.

So… unless this is all crazy and a bad idea, how can I create a .asp page which has absolutely NOTHING except a single webpart which I can preconfigure and then hard code into the .asp page?

I'm not a .asp man, in fact I'm only really doing this as a favour, so please don't respond saying that I need to do xyz in SharePoint Designer (to which I don't have access) or build a custom module from scratch. 🙂

Any ideas?

Best Answer

Since you are specific about not wanting a SharePoint Designer solution, I will give you one using 'Tommy'

In 'Tommy':
File => New => ASPX Page
Insert => SharePoint Controls => WebPartZone

Go in the browser, http://server/mycustompage.aspx Edit, insert your WebPart.

'Tommy' is a free download, by the way, get it here.

Related Solutions

R – programmatically replace one webpart with another in Sharepoint

I would write a console application for this.

Open the root Web and iterate through its sub webs. Do the work needed for each page, by opening the WebPartManager.

Here are some pseudo code to get you started.

string SourceUrl = "http://ThisWeb";

using (SPSite sourceSite = new SPSite(SourceURL))
{
    using (SPWeb sourceWeb = sourceSite.OpenWeb(SourceURL))
    {
        IterateSubWebsProd(sourceWeb):
    }
}

private void IterateSubWebsProd(SPWeb sourceWeb)
{
    // This is the migration function
    DoThingyWithThisWeb(sourceWeb);

    foreach (SPWeb subWeb in sourceWeb.Webs)
    {
      IterateSubWebsProd(subWeb);
      subWeb.Dispose();
    }
}

private void DoThingyWithThisWeb(SPWeb sourceWeb)
{
    PublishingPage currentPage = null;

    string currentPageName = "<something>";
    // Find the pages that you want to modify, with a CAML query for example
    SPQuery query = new SPQuery();
    query.Query = string.Format("" +
    "<Where>" +
      "<Eq>" +
         "<FieldRef Name='FileLeafRef' />" +
         "<Value Type='File'>{0}</Value>" +
      "</Eq>" +
    "</Where>" +
    "", currentPageName);


     // This codesnippet is from a Publishing web example
     PublishingWeb publishingWeb = PublishingWeb.GetPublishingWeb(sourceWeb);
    PublishingPageCollection pageColl = publishingWeb.GetPublishingPages(query);
    if (pageColl.Count > 0)
    {
        currentPage = pageColl[0];
    }

    using (SPLimitedWebPartManager wpMan = currentPage.ListItem.File.GetLimitedWebPartManager(System.Web.UI.WebControls.WebParts.PersonalizationScope.Shared))
    {
        foreach (WebPart wp in wpMan.WebParts)
        {
            if (wp.GetType().Equals(typeof(Microsoft.SharePoint.WebPartPages.ContentEditorWebPart)))
            {
                Microsoft.SharePoint.WebPartPages.ContentEditorWebPart thisWebPart = wp as Microsoft.SharePoint.WebPartPages.ContentEditorWebPart;

                // This is just dummy code, here you will do your content migration 
                XmlDocument xmlDoc = new XmlDocument();
                XmlElement xmlElement = xmlDoc.CreateElement("RootElement");
                xmlElement.InnerText = sourceItem[SourceField].ToString();
                thisWebPart.Content = xmlElement;

                wpMan.SaveChanges(thisWebPart);
            }
        }
    }
}

R – Import webparts to page layout in SharePoint

try adding the code from the .webpart into the layout directly. (e.g. open in notepad copy-paste into SharePoint designer).

Note: You should look up examples already in some layout pages as there are a few minor changes required to the webpart format (I vaguely recall).

Be sure to version your layout pages as SharePoint designer can sometimes take liberties with your code and stuff the page up (and refuse to load/save it ever again). If this happens, use the web site to revert the page to a previous (working) version.

Best Answer

Related Solutions

R – programmatically replace one webpart with another in Sharepoint

R – Import webparts to page layout in SharePoint

Related Topic