css class names capitalized after moving on production

This is the place to report bugs and get support. When posting in this forum, please always provide as much detail as possible.

Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum, do not report it as a bug.

This is the place to report bugs and get support

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.
Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum.
This thread is closed to new posts. You must sign in to post in the forums.
9/1/2010 11:00:43 AM
sorvik
Gravatar
Total Posts 87
View Posts

css class names capitalized after moving on production

Hi,

very strange issue, i tried to use artistee family of skins, on my test server it works great, but after i moved site to godaddy shared hosting something strange happened - some css classes stopped to work, it took a while to figure out that in HTML markup on my test server css class is art-post but on Godaddy HTML markup shows "art-Post"(this happens with some other classes but not all!?!). Only difference betwin two servers is medium trust of shared hosting, the site is xcopy of my dev site.

Can someone advise where to find this magic capitalization source?

Regards,

Victor

P.S. my temporary solution for this problem - i made copies of few needed css classes in css file and make it with capitalization. not too good but works.

9/1/2010 11:14:00 AM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: css class names capitalized after moving on production

These things are controlled by the theme.skin file. The problem under .NET 3.5 medium trust is that VirtualPathProviders do not work, so instead of using the theme.skin file from the skin folder, all skins use the one from /App_Themes/default. So you can solve it by copying the theme.skin file from one of your skins into the /App_Themes/default folder replacing the one that is already there. As long as all your skins are from the same version of Artisteer it should work fine. Artisteer 2.3 used mixed case class names whereas in Artisteer 2.4 they changed to all lower case.

Note that under .NET 4 VirtualPathProvider does work in medium trust.

Hope it helps,

Joe

You must sign in to post in the forums. This thread is closed to new posts.