World is now on Opti ID! Learn more

Ian Causton
Jun 8, 2011
  4244
(0 votes)

Composer 4 and the case of the disappearing categories

After deploying an update to a recent EPiServer 6 and Composer 4 based site I received notification from a concerned client that the Composer toolbox had lost all it’s categorisation.

composerToolBox

The site had over 30 Composer content functions all of which were now within the uncategorized list, making the job of adding content that much harder. Furthermore, setting up the categories in the first place proved quite time consuming so they were, understandably, reluctant to revisit the task.

At once, I mobilised all my forces and began focussing our efforts on discovering where in the episerver db schema the categorization was stored and thereby rectify the situation. After many fruitless hours pouring over this and analysing sql profiler results I had an epiphany! And began looking in the site tree, within which I discovered the source of Composer’s Categorization.

I therefore provide this information in the hope of helping others should they face a similar mystery. If you login to edit mode and examine the ContainerPageProperty within the ‘[Extension data container]’ ‘page’ you will discover in the xml the ‘CategoryDataCollection’ node, this is where Composer stores the categorization used in the toolbox and admin mode.

 

extensionDataContainer

Unfortunately this ‘page’ does not have a publishing history to enable any sort of rollback so without looking further into why the data was initially lost (it has happened 2 or 3 times now) I am taking manual backups of this property prior to a deployment.

If anyone could shed any light on this/has any further information it would be much appreciated. But for the time being this case is closed.

Jun 08, 2011

Comments

Please login to comment.
Latest blogs
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |