Um, I take that back.  When I tried to change the container a second time at the Admin level, I STILL GET THE SAME ERROR!  Man this is a nightmare.  I wish someone on the core team could explain to me what's happening and how to fix it.

Ok. Well I now see where the bug is.  The container assignment at the administrative and host level doesn't work properly.  If I put a 'Container' folder in the [dnnfolder]/portals/0 folder, and then put a 'mycontainers' folder off of that.  It screws up the path.  It's *supposed* to look at the [L] and see this is a portal container, but it doesn't.  Instead it points to the _default folder.  Even worse, it adds an extra '/[dnnfolder]' *AFTER* the '...Containers' folder.

If this was a bug (and it sure looks like one to me, all I did was use apply a container I could *see*), I sure wish someone would have told me two weeks ago.  At least I know how to fix it now, but I guess I should wait before I put this version of DNN into production.  Me thinks there are still a few glitches to work out...either that or I don't know what.  If I saved this portal, and then upgrade the actual site w/3.0.13 and then apply this exported portal, will this problem happen again?

And I truly thank you Jan for your help.  Seems like if it wasn't for you, I'd be awful lonely with this question around my neck.

Oh yeah, for anyone that's wondering.  To fix this you need to query your database, or open it in Enterprise Manager (for MSSQL anyway), and open the 'Skins' table.  There you'll see the list of Skins you've assigned at the host and portal level.  If it's empty, then you are using the default skin (or have a Skin assignment for each page/module).  If it has an [L] at the beginning, then it's a *portal* skin/container, and will have a path that includes the portal assigned that skin/container.  If it has a ['G'] (had to insert single quotes in here or it displays a gift icon)  in the front, then it's a host level assigned skin or container, and the path should have the '_default' folder in it.  But somewhere in the assignment code, it's futzing this path up.  Where, I have no clue.

I dont follow you now.

The container should bee in portals/_default/containers/yourcontainer folder for host containers

and portals/0/containers/yourcontainer folder for portal containers.

I cant reproduce the error here , where exact do you have it.

I asume you can assign the dnn-blue conteiner and all standard containers.

jan_olsmar wrote:

I dont follow you now. The container should bee in portals/_default/containers/yourcontainer folder for host containers and portals/0/containers/yourcontainer folder for portal containers. I cant reproduce the error here , where exact do you have it. I asume you can assign the dnn-blue conteiner and all standard containers.

That's correct Jan.  And that's what I state above.  I have placed the containers in my portal folder (see above) in [dnnfolder]/portals/0/Containers/mycontainers.  Then I go to the Admin->Skins and *attempt* to apply ANY of the 'mycontainers'.  I get the error I've listed above three times so I won't bother you with it again.  It's not parsing the path correctly when I apply the container.  And it has happened to me multiple times.  By multiple times EVERY TIME I REINSTALL, the plop the 'mycontainers' folder in the place I describe in a previous sentence.  So I am able to reproduce this error from scratch everytime.

I'm also still trying to get an answer as to what your thinking was to have me try all these other things.  Could you explain so that others who have this problem will understand?  Thanks in advance.

I just trying to track your error down.

I cant reproduce it. It works smoth and and I havent heard anybody ells getting the eror so I asume you have som wierd in your installation.

Did you test dnn-blue???

Hey Jan:

Yes, but those are all host containers, not admin/portal containers.  All I know is that the path was screwed up.  You asked me to try a couple of other container load places like modules and such...I *still* don't understand any of your reasoning behind asking me this.  Put a container folder in your 0/containers/ folder.  Then try to apply the container (heck, use *my* container...it doesn't get any simpler than the one above! ;-)) by going to Admin->Skins  I get the error every time.  Well, I don't get it if I apply a module container, and THEN for ONE TIME go back to the Admin->Skins and load one of the containers like above.  But as soon as I load any other one, I get the above error.  This has happened *four* times starting from scratch (deleting dnn folder, reinstalling dnn, etc..), so it's not something strange about my install.  I think it's a DNN bug.  In fact I know it is, because it is NOT specifying the path properly if a container is put in the 0/containers folder.  As you can see above by the path it's looking for and the multiple times I've specified the path it *should* be looking for.