Or maybe you have an unsused file within your skin folder that references Sidebar 2.

If the file is there b2evo can't know that you actually never use it.

I'll look again. I noticed it didn't leave when I added a container and reloaded the skin, so I used Agent Ransack to find "Sidebar 2" in the skins folder and it showed up - in the evocamp skin (of course). But yeah I'll look again because it doesn't make any sense.

Okay I think I got it.

What *appears* to be happening is that when it reloads a skin and discovers a bunch of containers, it will add containers that are new and of course do nothing with containers it finds that it already knows about, but it didn't remove reference to the container that it didn't discover anew. I did not cruise through code on this one: simply went to the database and deleted reference to that container in that skin from the skins__container table.

I suppose deleting the skin and re-installing it would have solved the problem without direct intervention in the database, but that would entail more than it would be worth to remove mention of an unused container.

And hey in the grand scheme of things this is a tiny little issue yah?

Yup, tricky issue.

I am planning to have the skins declare their containers explicitely though which should allow for much more flexibility (and less detection errors :p)