WCM content may loose Category after Syndication in a migrated environment

WCM content may loose Category after Syndication in a migrated environment

In 6.1, categories selected in the profile section of a content were saved on the node in the jcr property named icm:categories .

In 7.0 or later, categories selected in the profile section of a content are stored in a new property named ibmcontentwcm:explicitCategories. The earlier property icm:categories will contain the combined set of categories selected in the profile as well as categories selected in option selection elements on the content .(Category selection in option selection elements is a new feature in 7.0 or later).

As you can see, for any data migrated from 6.1 or 6.0 to 7.0 or 8.0, the migration logic would have to ensure that all the categories in icm:categories should also be copied to ibmcontentwcm:explicitCategories to make it consistent with 7.0 or later. So we introduced the task named update-wcm-profile-categories to copy categories from icm:categories to ibmcontentwcm:explicitCategories.
When we introduced this task in a Cumulative Fix , we also made sure that categories would be missing from profile section if the task was not run and that we would know the problem right away.
That said, the only reason why categories would be missing from profile section on subscriber server is if the node that was sent from the syndicator was not rightly formed.

Running ConfigEngine task update-wcm-profile-categories on syndicator would resolve the issue.