Cliff, there is a breaking change, which shall be rolled back in future version: pane names are case sensitive, make sure, it is spelled ContentPane.

I have the content panes all named correctly. I thought it might be a child portal issue, so I pointed one of my test domains to the site and made it a parent portal. Still no success.

You are right in that I did do a 4.9.1 upgrade and I have two portals on this one DNN install for the same client. If something doesn't come up soon to resolve this, I will just create a new DNN install for this particular site and then install the skin on it. I have create most of the menu structure, but I can recreate that pretty quick. Or should I try a DNN 5.0 upgrade? I wanted to wait for 5.0.1 to come out that is a little more stable.

When I look in the event viewer it shows that the Text HTML modules were created, they just don't show up on the page.

But ultimately, it would be nice to know the issue.

UPDATE: OK, I'm stupid. I tried putting on a couple of other skins with the same problem. Then I reverted to a DNN Plain Blue skin and it popped up a message that the Portal was expired. So no content was being displayed. What needs to be coded into a custom skin so that this message would display. I know I have other portals with custom skins that do show if expired. So why did this one not show the expiration message?