Hello helfenj
The problem is not in the new DNN update, but in the way the page is skinned.

You put hard coded CSS in the Default.aspx page.
If you install an update, the default.aspx page is being overwritten, and your CSS is gone.
In fact you are not really using skinning on this page since skinning means you separate the layout from the content.
If you want to use DNN updates without these kind of problems you should make sure everthing that influences the layout is in the skin files (outside any .ascx / .aspx file)
So....
Just copy all the CSS lines in your original default.aspx to one of the skinning CSS files...
Skin.css of the current skin, or portal.css.
And you site will look fine.

e.g. I'm sure you will have the same problem with the javascript in the default.aspx file...

---

Hmmm...
Is there a skin error if you login as Admin?
Are there any errors if you login as host and choose > skins > select the skin package > parse skin package?
Do you have ftp access to the installation?

---

To answer your previous post.

No errors when logged in admin, but the css is not applied. same results as when host or admin.
No errors doing a parsing of the skin file. (no errors on upload either)
Yes. I have ftp access to all my domains.

As for this post.

I have not tried adding the css to the defaults of portal css files because in my opinion that is not the way to develop a skin. I can try it jsut for kicks tonight, but I think it would be the wrong solution.

The multiple heads in my 4.3.4 are not in my skin file they must be added when the file is uploaded to DNN. Which might raise other questions.

I looked at the thread you linked to and see that a fix may have caused this and thats fine, but how do I avoid it now? I don't mind changing the skin if thats what it takes.

I have sent the skin file to your yahoo account, but if you are gone for a week I hope that someone else can look into this as well.

Thanks.