Hi - I just upgraded a client's site from 2.3.7.5 to 2.3.9.7. The scripts all completed successfully, so everything is good from that perspective, however, the styles are clearly messed up. They have their own skins (that were not changed in the upgrade). I am assuming that some other .css has changed that has affected their custom one. I'm seeing things like footer divs that used to go all the way across that are now crunched all the way to the left, divs on top of other divs, things like that.

My question is, what would be a likely place to start looking? There are many .css files in addition to their custom one, I'm hoping that there is a common place that things get confused in an upgrade.

Thanks for any direction you can give me.

-Harriet

Thanks very much - sorry I don't have experience with mojoportal, just got assigned to do the upgrade.

Skin upgrade page says:

To update an existing skin created in Artisteer 3.0, download the extra-skins.zip from our codeplex download page and copy the theme.skin file from one of the artisteer30 skins included in the zip.

I'm not clear what it means by "copy the theme.skin file" - copy the file to where? Am I just taking the whole file and putting it somewhere, or am I looking at the contents and modifying an existing file in my installation based on that file?

Hi - I reviewed the skin changes since my client last updated, and it seemed like the only one related to styles was the one for 2.3.7.6. I did get a new theme.skin file (for 3.0, their Artisteer version) and replaced the ones in their 3 custom skin folders. However, this did nothing. The css is still messed up.

Am I misunderstanding about not needing the other skin update changes listed? They seemed specific to facebook, jquery plugins, or playing video, or other things not happening on this site, which is why I only applied the one related to css and Artisteer.

Alternately, is there something else you could recommend that I look at that could be the problem? 

Thanks again for your help - Harriet

Thanks for your reply. This upgrade was done on an internal dev version so can't be seen from an outward facing URL. (Good that they didn't break the real site, but bad that I can't have you look at it).

They are .NET 4.0/ full trust. I tried copying the theme.skin where you said anyway just to try it, but it didn't help.

Regarding the javascript suggestion, when I run it in IE8 I get jQuery.browser.msie is null or not an object on line 120 of ScriptResource.axd. In Chrome it says "Uncaught TypeError: Cannot read property 'msie' of undefined" on the same line. This is part of the begin Menu code that looks like it's trying to change art-hmenu. The menu doesn't seem to have a problem, it's more other columns on the page and the footer (on top of each other, not in right place). Do you think that error could cause general style problems?

Thanks - Harriet

Hi - in the layout.master file, on the line that says:

<portal:ScriptLoader ID="ScriptLoader1" runat="server"/>

I changed it to:

<portal:ScriptLoader ID="ScriptLoader1" runat="server" IncludeJQueryMigrate="true" />

Now in the javascript console window I get:

JQMIGRATE: jquery.browser is depricated

​I no longer get the other javascript error, but it made no change at all in the layout/css being trashed.

Did I understand the change correctly? Any other thoughts?

Here is one thing I have noticed. They have three skins created in Artisteer. The one that is used only for the home page is the worst - columns on top of each other lots of stuff in the wrong place. But another of their skins that's used for internal pages is fine. Is that any clue? Could there be particular things they did in one artisteer-created skin that is likely to cause problems?

Thanks for your help. I know this is dragging on, but it isn't something I can spend much time on. I do appreciate your ideas and expertise.

Thanks - Harriet