Try our conversational search powered by Generative AI!

Ian Causton
Jun 8, 2011
(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.


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.



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


Andreas Thente
Andreas Thente Jun 8, 2011 09:28 PM

This has been a major problem with Composer. Categories, access rights and other critical information have disappeared several times in my projects, both in the development phase and in live environments. This made both me and my clients pretty nervous since noone could understand where the problem came from, making it impossible to reproduce the behavoiur and report it as a bug. However, I tought it would have been solved in the last release but no... Good luck finding the erroring functionality. EPiServer should look into this deeper which I hope they do.

Best regards,

Jun 14, 2011 10:41 AM

We haven't seen this problem before but our support team will reach out to you to get more information to be able to investigate it further. Thanks.

Andreas Thente
Andreas Thente Jun 14, 2011 03:14 PM

Thanks Peter. I think I´ve had this problems in multi language sites, not sure if it exists in single language sites. Maybe you can provide us with more info, Ian?

I think the xml data somehow resets in the Extension Data Container, when and how do I not know.

Ian Causton
Ian Causton Jul 1, 2011 05:14 PM

Hi Guys,
Thanks for your interest. As this stage I can only give you general information because it was only happening intermittently and only in the production environment. The site is single language and the issue would arise after a deployment to production and as Andreas suggests it is as if the xml data has reset itself.

Thanks Mar 29, 2012 02:33 PM

I'm having a similar problem with a live single language EPiServer 5R2 Composer 3.2.5 site.
At random points all composer elements lose their access rights. This has now happened 3 times over the last 2 months - only in the production environment - and I haven't been able to reproduce it or figure out what caused it.

Any information regarding this is much appreciated since we're still struggling! Also if anyone has any ideas how to recreate these settings without too much hazzle...


Please login to comment.
Latest blogs
Headless forms reloaded (beta)

Forms is used on the vast majority of CMS installations. But using Forms in a headless setup is a bit of pain since the rendering pipeline is based...

MartinOttosen | Mar 1, 2024

Uploading blobs to Optimizely DXP via PowerShell

We had a client moving from an On-Prem v11 Optimizely instance to DXP v12 and we had a lot of blobs (over 40 GB) needing uploading to DXP as a part...

Nick Hamlin | Mar 1, 2024 | Syndicated blog

DbLocalizationProvider v8.0 Released

I’m pleased to announce that Localization Provider v8.0 is finally out.

valdis | Feb 28, 2024 | Syndicated blog

Epinova DXP deployment extension – With Octopus deploy

Example how you can use Epinova DXP deployment extension in Octopus deployment.

Ove Lartelius | Feb 28, 2024 | Syndicated blog

Identify Azure web app instance id's for an Optimizely CMS site

When running Optimizely CMS in Azure, you will be using an instance bound cloud license. What instances are counted, and how can you check them? Le...

Tomas Hensrud Gulla | Feb 27, 2024 | Syndicated blog

Introducing Image Transformer - AI Assistant for Optimizely

We've got something super cool to share with you, and it's all about giving your images a fresh spin. Image Transformer, the latest feature from ou...

Luc Gosso (MVP) | Feb 26, 2024 | Syndicated blog