The FieldId elements defining the columns in question were missing two attributes: RichText="TRUE" and RichTextMode="FullHtml". New sites based on this template are now working correctly but MS has recommended we not change the site template for the sake of existing sites. We're therefore exporting content, recreating the site, and importing content back in--a hassle but should do the trick.
RichText="TRUE"
<Field
ID="{EE8A6F4B-E0B9-4aa8-B923-967D25CE1154}"
Type="HTML"
Group="Custom"
Name="PublishingPageContentBottom"
DisplayName="Publishing Page Content Bottom"
StaticName="PublishingPageContentBottom"
Hidden="FALSE"
Required="FALSE"
Sealed="FALSE"
RichTextMode="FullHtml"
/>
The MSDN documentation currently reflects this structure but I'm not positive it did previously... our mistake either way but at least it's fixed now and the doco is accurate.
Good for people to know.
ReplyDeleteHi,
ReplyDeleteHow did you export all the content? With content deployment or with a custom tool?
thx!
Hi Frederik--
ReplyDeleteOne of the guys on my team wrote a custom throwaway app using the API but you might be able to use the SharePoint Content Deployment Wizard (http://www.codeplex.com/SPDeploymentWizard). It will create a backup file of your content you can later import into your site.
Hi Michhes,
ReplyDeleteThx for your feedback. When I try it with content deployment, the problem stays with the imported files. New pages works fine after.
kind regards,
Frederik
Hmm--that makes sense if the content deployment technique is importing the *same* page and its associated bits. Our API-based app exports page content field by field, creates a new page, and populates the new page with the exported content.
ReplyDeleteThx Michhes!
ReplyDelete