R – How to set the setuppath of an incorrectly provisioned file

sharepoint

I have a feature that provisions a heap of files including layouts and images into a MOSS site. Over the lifetime of this site we have altered the provisioning file, the Elements manifest, a number of times: adding files, removing files, and changing the file structure in the feature folder. Unfortunately we have discovered that if you remove a file from a provisioning document then reactivate the feature the SPFile of the removed file remains in the content database.

Since these files are ghostable they have a property in the sharepoint content db called 'SetupPath', which is basically the Template folder relative path of the original file. This file is presumably used when the file is in its unghosted state. Since I have changed my feature this setup path refers to a file that doesnt exist.

The ramifications are: I cant update the file in the API any longer, It doesnt appear via the GUI and when I run a content deployment, a full content deployment, I get file not found errors. Worse, given there is a good 1000 of these files that have been removed, there are something like 3.5k errors on every full content deployment. The push doesn't stop, but so many errors are disconcerting and hide any actual catastrophic errors should they occur.

Finally if I update a file, giving it a new path, then when that file is referenced in sharepoint a 404 is thrown. Super bad if the file happens to be a layout (all pages using it fail).

I've coded up code to delete SPFiles that have are no longer provisioned, problem solved. However files that are still being used but just have an incorrect setup path, I am at a lost.

I can go SPFile.Properties["vti_setuppath"] and see the incorrect setup path. However, though I can set this property I cannot seem to make it stick. SPFile.Update() doesnt work, and neither does checking the file in and out.

Any help would be appreciated.

Best Answer

There is an workaround that you can try. Now that you have finalized the path of the Layout Pages. You can create a new Page Layout with the path you want and call it version 2, deploy it and in SharePoint you can change the Page layout of the Instance Pages. Now you can remove all the Old Page Layouts.

Related Solutions

R – Find out if a SharePoint URL is a file or not – MOSS out of the box web service

I would seriously consider going with propfind (webdav). I can't give you an exact answer on how to check for file or document library or list, but I can post a function that can serve as a base for something you might implement... here it is....

/// <summary>
        /// Checks if MOSS resource exists.
        /// </summary>
        /// <param name="url">
        /// The url to the resource.
        /// </param>
        /// <returns>
        /// True or false.
        /// </returns>
        /// <exception cref="Exception">
        /// </exception>
        private bool MossResourceExists(string url)
        {
            // Create the web request object
            var oReq = (HttpWebRequest) WebRequest.Create(url);

            // Set the needed properties
            oReq.Method = "PROPFIND";
            oReq.Credentials = wsLists.Credentials; // Use same credentials as wsLists. 
            oReq.AllowAutoRedirect = true;
            oReq.UserAgent = "Microsoft-WebDAV-MiniRedir/6.1.7600";

            try
            {
                // Enumerate through top level only, increasing the depth will find children.
                oReq.Headers["Depth"] = "0";
                oReq.Headers["translate"] = "f";
                var oRequest = new StreamWriter(oReq.GetRequestStream());
                oRequest.WriteLine();
                oRequest.Close();
                oReq.GetResponse();
                ////done with the webclient stuff, check the results

                //var oMyDoc = new XmlDocument();
                //oMyDoc.LoadXml(sResponse);
                //var oNsMgr = new XmlNamespaceManager(oMyDoc.NameTable);
                //oNsMgr.AddNamespace("D", "DAV:");

                //XmlNodeList oAllResponses = oMyDoc.SelectNodes(".//D:multistatus/D:response", oNsMgr);

                //foreach (XmlNode oNode in oAllResponses)
                //{
                //    if ()
                //    string oNodeURL = oNode.SelectSingleNode("./D:href", oNsMgr).InnerText.ToLower()
                //    Console.WriteLine("Name: " + 
                //                      oNode.SelectSingleNode("./D:propstat/D:prop/D:displayname",
                //                      oNsMgr).InnerText);

                //    if (oNode.SelectNodes("./D:propstat/D:prop/D:isFolder", oNsMgr).Count > 0)
                //    {
                //        Console.WriteLine("Is folder: " +
                //                oNode.SelectSingleNode("./D:propstat/D:prop/D:isFolder",
                //                oNsMgr).InnerText);
                //    }
                //    else
                //    {
                //        Console.WriteLine("Is folder: f");
                //    }
                //    Console.WriteLine();
                //}
            }
            catch (WebException ex)
            {
                var errorResponse = ex.Response as HttpWebResponse;

                if (errorResponse != null)
                    if (errorResponse.StatusCode == HttpStatusCode.NotFound)
                    {
                        return false;
                    }
                    else
                    {
                        throw new Exception("Error checking if URL exists:" + url + ";Status Code:" +
                                            errorResponse.StatusCode + ";Error Message:" + ex.Message);
                    }
            }
            return true;
}

C# – How to programmatically create editable wiki pages within the Pages library of an Enterprise Wiki site

With help from my other thread on sharepoint.stackexchange.com, I came up with this solution:

Instead of targeting the Pages library with regular wiki manipulation routines, we need to create a new Publishing Page and update Content type properties accordingly.

For the benefit of others, here's the code that worked for me:

using (SPSite site = new SPSite(SPContext.Current.Web.Url))
{
    SPWeb rootWeb = site.RootWeb;
    rootWeb.AllowUnsafeUpdates = true;
    SPList wiki = rootWeb.Lists["Pages"];
    String url = wiki.RootFolder.ServerRelativeUrl.ToString();
    PublishingSite pubSite = new PublishingSite(rootWeb.Site);
    string pageLayoutName = "EnterpriseWiki.aspx"; //Page Layout Name
    string layoutURL = rootWeb.Url + "/_catalogs/masterpage/" + pageLayoutName;
    PageLayout layout = pubSite.PageLayouts[layoutURL];
    PublishingWeb publishingWeb = PublishingWeb.GetPublishingWeb(rootWeb);
    PublishingPage newWikiPage;
    string myWikiPage = "MyWikiPage.aspx"; //Page name
    newWikiPage = publishingWeb.GetPublishingPages().Add(myWikiPage, layout);
    newWikiPage.Title = "My Wiki Page";
    newWikiPage.Update();
    rootWeb.AllowUnsafeUpdates = false;
}

Related Topic