Thread:Project:Support desk/my custom skin disappeared after upgrade to 1.20/reply (17)

Hi mark...here's what I have tried so far:
 * Tried changing $wgDefaultSkin = 'clayster'; to $wgDefaultSkin = 'claysterweb'; broke login.
 * Changed the name of ClaysterWeb.php to clayster.php…logon is fine (with $wgDefaultSkin = 'clayster';)
 * Changed the name of ClaysterWeb folder to clayster …logon is fine (with $wgDefaultSkin = 'clayster'; and ClaysterWeb.php as clayster.php)
 * Changed the name of ClaysterWeb.php (in skins/clayster folder) to clayster.php…logon is fine (with $wgDefaultSkin = 'clayster';)
 * substituted $wgDefaultSkin = 'clayster'; for $wgDefaultSkin = 'claysterweb'; login was fine but still didn’t get the custom skin up.
 * $wgValidSkinNames['clayster'] = "Clayster”
 * $wgAutoLoadClasses['SkinClayster'] = "$IP/skins/Clayster.php";
 * The 2 above break login with/without ClaysterWeb.php directly in skins folder so I tried them with small letter C’s (after changing ClaysterWeb.php to clayster.php)…login was fine but still didn’t get the custom skin up.
 * Preferences page is now restored… but I don’t know at what point that happened.

I'm wondering two thigs at this point:
 * 1) The Main.css file is using Google fonts...perhaps this is incompatible??
 * 2) Perhaps I should simply start again with the monobook skin and re-make the custom skin...I would guess the monobook skin with the 1.2 installation would be correctly upgraded with the installation...yes??

Thanks for all the attention, Jeff