Hello
I'm using DNN 4.3.5 and I encountered a strange problem when adding new (text/html) modules to a page. Sometimes when I add such a module, it shows up in a wrong container (dnn default) instead of using the portal-defined one. Refreshing the site does not help. The only workaround is to go to the module settings and click "save" without doing any changes, that fixes it. However, is there a real solution to this problem?

I've seen this little bug pop up on a few of my portals. The portal default is not correctly used, but some other container is used, although in my cases it's not the DNN default -- it just uses one of my other containers. I've searched the database tables and cannot find where it gets this. The workaround is to define your container on the page level (a lot of work if you have a lot of pages!) No one has responded to my question about this a few months ago. Any news on this bug??

The DNN default will appear if there is an error in your container, such as two definitions being of the same name (common mistake when making your own containers). If you are logged in as Admin/Host, you will get an obvious error message though. I don't think this is our problem.

---

Jason Honingford - Web & Software Developer
www.PortVista.com