locked
Importing a Design Package corrupts the Page content type RRS feed

  • Question

  • I've created a Design Package that includes a masterpage, 5 page layouts (linked to content types that inherit from Page) and some images/css.

    When I try to import that design package into another SharePoint 2013 server (same language, empty publishing site) the default 'Page' content types loses some columns. The Rollup Image, Meta Description, Meta Keywords, Hide Physical URls columns all disappear from the out of the box ‘Page’ Content Type.

    Does anyone have a clue why this is happening?

    Tuesday, January 8, 2013 1:49 PM

All replies

  • I'm seeing this too. Importing a design package will clobber these columns. 
    Wednesday, February 27, 2013 6:15 PM
  • Could you give a bit more information about this one, I'd like to try to recreate it and make sure I've got all the details.

    John Ross
    SharePoint Server MVP | Sr. Consultant Rackspace: SharePoint Consulting
    Blog: http://johnrossjr.wordpress.com
    Twitter: @JohnRossJr

    SharePoint 2013 Branding and User Interface Design
    Professional SharePoint 2010 Branding and User Interface Design (Wrox Programmer to Programmer)

    Thursday, March 7, 2013 1:31 PM
  • Hi everyone,

    I just found out about this problem myself and am curious as to what is going on. John, maybe you can help shed some light on this.

    First, I have been trying to help someone else who encountered this problem and he wrote a great blog post on his solution. JoostHaneveer, this may solve your problem as well.

    http://www.bondbyte.com/Blog/tabid/55/EntryId/24/SharePoint-2013-Design-Packages-broken.aspx

    After some research I am at a loss. To test, I have two different SharePoint 2013 RTM servers and four web applications (2 on each server). Each web application has one url based site collection. All four site collections have one root web based on the publishing site template. In effect they all should be the same.

    All of these site collections have a "Page" content type which is to be expected. 3 of the site collections only have 9 visible site columns while one has 15. Basically the same as the blog post above. I can find no other differences of these sites or site collections. How or why did the Page content type get more columns in the one site collection.

    This then leads us to our other issue with Design Packages. If you create a design package from a site with the shorter list of columns in the page CT, then deploy this Design Package to another site that expects the Page CT to have all 15 columns, you are out of luck. The Design Manager will replace your Page content type with what is in the Design Package.

    I consider this a huge issue which makes me re-evaluate Design Packages in general.

    John, any idea why or how the Page CT is different across different site collections? Is there a way to force the Page CT to include all 15 fields without having to create them manually?


    Eric Overfield - PixelMill - blog.pixelmill.com/ericoverfield - @EricOverfield

    Thursday, March 14, 2013 10:45 PM
  • What I'm finding is that OOB Page Content Type contains the 15 fields required by a Publishing site as mentioned in my blog. When the Design Package is exported the Content Type Manifest (ElementsContentType.xml) within the WSP contains....

      <ContentType ID="0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB064584E219954237AF39" Name="Page" Group="Publishing Content Types" Description="Page is a system content type template created by the Publishing Resources feature. The column templates from Page will be added to all Pages libraries created by the Publishing feature." Overwrite="TRUE" FeatureId="{59e01efd-f2f7-4e62-ad2d-bd42028ae437}">
        <Folder TargetName="_cts/Page" />
        <FieldRefs>
          <FieldRef ID="{c042a256-787d-4a6f-8a8a-cf6ab767f12d}" Name="ContentType" />
          <FieldRef ID="{5f47e085-2150-41dc-b661-442f3027f552}" Name="SelectFilename" />
          <FieldRef ID="{8553196d-ec8d-4564-9861-3dbe931050c8}" Name="FileLeafRef" Required="TRUE" />
          <FieldRef ID="{8c06beca-0777-48f7-91c7-6da68bc07b69}" Name="Created" Hidden="TRUE" />
          <FieldRef ID="{fa564e0f-0c70-4ab9-b863-0177e6ddd247}" Name="Title" Required="FALSE" ShowInNewForm="FALSE" ShowInEditForm="TRUE" />
          <FieldRef ID="{28cf69c5-fa48-462a-b5cd-27b6f9d2bd5f}" Name="Modified" Hidden="TRUE" />
          <FieldRef ID="{822c78e3-1ea9-4943-b449-57863ad33ca9}" Name="Modified_x0020_By" Hidden="FALSE" />
          <FieldRef ID="{4dd7e525-8d6b-4cb4-9d3e-44ee25f973eb}" Name="Created_x0020_By" Hidden="FALSE" />
          <FieldRef ID="{9da97a8a-1da5-4a77-98d3-4bc10456e700}" Name="Comments" />
          <FieldRef ID="{51d39414-03dc-4bd0-b777-d3e20cb350f7}" Name="PublishingStartDate" />
          <FieldRef ID="{a990e64f-faa3-49c1-aafa-885fda79de62}" Name="PublishingExpirationDate" />
          <FieldRef ID="{aea1a4dd-0f19-417d-8721-95a1d28762ab}" Name="PublishingContact" />
          <FieldRef ID="{c79dba91-e60b-400e-973d-c6d06f192720}" Name="PublishingContactEmail" />
          <FieldRef ID="{7546ad0d-6c33-4501-b470-fb3003ca14ba}" Name="PublishingContactName" />
          <FieldRef ID="{dc47d55f-9bf9-494a-8d5b-e619214dd19a}" Name="PublishingContactPicture" />
          <FieldRef ID="{0f800910-b30d-4c8f-b011-8189b2297094}" Name="PublishingPageLayout" />
          <FieldRef ID="{914fdb80-7d4f-4500-bf4c-ce46ad7484a4}" Name="PublishingVariationGroupID" />
          <FieldRef ID="{766da693-38e5-4b1b-997f-e830b6dfcc7b}" Name="PublishingVariationRelationshipLinkFieldID" />
          <FieldRef ID="{61cbb965-1e04-4273-b658-eedaa662f48d}" Name="Audience" />
        </FieldRefs>

    However the ContentTypes.Definition column in the Site Collection database contains

    <ContentType ID="0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB064584E219954237AF39" Name="$Resources:cmscore,contenttype_page_name;" Group="$Resources:cmscore,group_publishingcontenttypes;" Description="$Resources:cmscore,contenttype_page_description;" Version="3">
    	<Folder TargetName="_cts/Page" />
    		<FieldRefs>
    			<FieldRef ID="{c042a256-787d-4a6f-8a8a-cf6ab767f12d}" Name="ContentType" />
    			<FieldRef ID="{5f47e085-2150-41dc-b661-442f3027f552}" Name="SelectFilename" />
    			<FieldRef ID="{8553196d-ec8d-4564-9861-3dbe931050c8}" Name="FileLeafRef" Required="TRUE" />
    			<FieldRef ID="{8c06beca-0777-48f7-91c7-6da68bc07b69}" Name="Created" Hidden="TRUE" />
    			<FieldRef ID="{fa564e0f-0c70-4ab9-b863-0177e6ddd247}" Name="Title" Required="FALSE" ShowInNewForm="FALSE" ShowInEditForm="TRUE" />
    			<FieldRef ID="{28cf69c5-fa48-462a-b5cd-27b6f9d2bd5f}" Name="Modified" Hidden="TRUE" />
    			<FieldRef ID="{822c78e3-1ea9-4943-b449-57863ad33ca9}" Name="Modified_x0020_By" Hidden="FALSE" />
    			<FieldRef ID="{4dd7e525-8d6b-4cb4-9d3e-44ee25f973eb}" Name="Created_x0020_By" Hidden="FALSE" />
    			<FieldRef ID="{9da97a8a-1da5-4a77-98d3-4bc10456e700}" Name="Comments" />
    			<FieldRef ID="{51d39414-03dc-4bd0-b777-d3e20cb350f7}" Name="PublishingStartDate" />
    			<FieldRef ID="{a990e64f-faa3-49c1-aafa-885fda79de62}" Name="PublishingExpirationDate" />
    			<FieldRef ID="{aea1a4dd-0f19-417d-8721-95a1d28762ab}" Name="PublishingContact" />
    			<FieldRef ID="{c79dba91-e60b-400e-973d-c6d06f192720}" Name="PublishingContactEmail" />
    			<FieldRef ID="{7546ad0d-6c33-4501-b470-fb3003ca14ba}" Name="PublishingContactName" />
    			<FieldRef ID="{dc47d55f-9bf9-494a-8d5b-e619214dd19a}" Name="PublishingContactPicture" />
    			<FieldRef ID="{0f800910-b30d-4c8f-b011-8189b2297094}" Name="PublishingPageLayout" />
    			<FieldRef ID="{914fdb80-7d4f-4500-bf4c-ce46ad7484a4}" Name="PublishingVariationGroupID" />
    			<FieldRef ID="{766da693-38e5-4b1b-997f-e830b6dfcc7b}" Name="PublishingVariationRelationshipLinkFieldID" />
    			<FieldRef ID="{543bc2cf-1f30-488e-8f25-6fe3b689d9ac}" Name="PublishingRollupImage" />
    			<FieldRef ID="{61cbb965-1e04-4273-b658-eedaa662f48d}" Name="Audience" />
    			<FieldRef ID="{50631c24-1371-4ecf-a5ae-ed41b03f4499}" Name="PublishingIsFurlPage" />
    			<FieldRef ID="{ff92f929-d18b-46d4-9879-521378c689ef}" Name="SeoBrowserTitle" />
    			<FieldRef ID="{d83897e5-2430-4df7-8e5a-9bc06c664992}" Name="SeoMetaDescription" />
    			<FieldRef ID="{45ae2169-585c-440b-aa4c-1d5e981fbbe5}" Name="SeoKeywords" />
    			<FieldRef ID="{325c00dd-fd91-468b-81cf-5bb9951abba1}" Name="RobotsNoIndex" />
    		</FieldRefs>
    The problem/bug is on export and it doesn't get corrupted until the next import.

    I renamed the *.WSP to *.CAB, extracted the ElementContentType.XML file and edited it. However, I wasn't able to recreate the WSP without creating a whole Visual Studio Project.
    Thursday, March 14, 2013 11:34 PM
  • I'm going to ask around and see if I can get some additional info.  Good stuff here.

    John Ross
    SharePoint Server MVP | Sr. Consultant Rackspace: SharePoint Consulting
    Blog: http://johnrossjr.wordpress.com
    Twitter: @JohnRossJr

    SharePoint 2013 Branding and User Interface Design
    Professional SharePoint 2010 Branding and User Interface Design (Wrox Programmer to Programmer)

    Friday, March 15, 2013 12:09 AM
  • CoderBond,

    After more digging I came to the same conclusion. I built a few more site collections and the Page Content Type always had the correct columns. When I then created a Design Package with no actual customizations even, the Design Package contained not only a definition of the Page Content Type but also a definition missing some columns.

    When I then go and apply the Design Package to a fresh site, the Page Content Type becomes corrupt with missing columns.

    My conclusion? Design Packages have a bug that needs to be fixed by Microsoft before they should be used by anyone. Otherwise CoderBond's techinque of adding the columns back to the wsp is brilliant and is a reasonable workaround. Thanks for the detailed code.


    Eric Overfield - PixelMill - blog.pixelmill.com/ericoverfield - @EricOverfield

    Friday, March 15, 2013 12:17 AM
  • Just a quick note to say that I'm experiencing the same thing, so thanks for raising it.

    Looks like I'll go back to creating my own wsp in VS to deploy my branding files.

    Monday, April 29, 2013 4:05 AM
  • it appears to impact other content type besides just "page". we are seeing corruption in "article page" and "welcome page" as well.

    article page is missing:

    Page content, Summary Links, Byline, ArticleDate, Image Caption

    Welcome page is missing:

    Page content, Summary Links, Summary Links 2

    working on documenting all the content types that are not being exported fully.




    Friday, May 10, 2013 5:35 PM
  • Experienced the same errors after deleting an old version of our design package. Deleted site columns (even default SharePoint ones), corrupted content types, missing page layouts and broken (publishing) features.

    The whole site collection seems corrupted. It there a way to fix this issue on an existing site collection?  I don't want to do all our work again. 

    I have written a blog post about it
    http://blog.amtopm.be/2013/07/12/design-manager-fatal-bug/

    Monday, July 15, 2013 6:11 AM
  • Hi,

    Yeah, you made the fatal flaw of removing a Design Package. The rumors I heard from MS was that was a big no-no. Design Packages are not meant to be removed, which unfortunately also decreases their value for the time being.

    As you noticed you lost the page layout content types. You would have to remove or rename the "Pages" library so that the publishing feature can recreate this for you when it is also re-adding your missing content types. You could also try re-adding your design package solution as that also has copies of your missing content types.

    When I create a Design Package, I always open this in VS to make some modifications. In the ListInstances folder, update the elementsContentType.xml and ElementsFields.xml files to not include OOTB CT's or Fields. Just be careful if for some reason you updated the OOTB CT's, hopefully you did not.


    Eric Overfield - PixelMill - blog.pixelmill.com/ericoverfield - @EricOverfield

    Monday, July 15, 2013 6:28 AM
  • Thanks for your quick reply. 

    I think they should disable the delete option if the design packages are not meant to be deleted. 

    Luckily I did't change any OOB content types or other artifacts. Uploading the latest design package did solve the missing site column issues. Not that 'm completely confident that all the quirks are solved. 

    Back to deploying page layouts with features. 


    Wouter - AM 2 PM - http://blog.amtopm.be/ - @wlaureys

    Monday, July 15, 2013 12:41 PM
  • Wouter,

    Since Design Packages use the 2010 sandboxed solution method of packaging and installation, I do not believe there would have been a way to remove the deactivate/delete methods.

    My frustration has been why was OOTB CT's such as Page and page layout included in the first place? I have to assume that was because of basic inheritance and also in case the OOTB components were modified in any way. But then why are some of the columns missing from CT's such as originally posted in this thread.

    I have found that creating a Design Package and then using VS to modify it still saves quite a bit of time than packaging the solutions by hand, so it is still worth it.


    Eric Overfield - PixelMill - blog.pixelmill.com/ericoverfield - @EricOverfield

    Monday, July 15, 2013 4:29 PM
  • You use the id of the list's, you may use the name of list in link;
    Wednesday, September 4, 2013 6:24 PM
  • The SharePoint 2013 Server August 2013 CU seems to (partly?) address this issue. The description of KB2717607 (which is included in the CU update) states:

    "When you export a design package from a SharePoint Server 2013 site, some out-of-box (OOB) fields are missing from the content types."

    To download the CU update:
    http://support.microsoft.com/kb/2817616

    The KB2817607 can be found here:
    http://support.microsoft.com/kb/2817607


    Wouter - AM 2 PM - http://blog.amtopm.be/ - @wlaureys

    Monday, September 9, 2013 7:59 PM