StyleSheetCombiner Skin Versioning?

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
This thread is closed to new posts. You must sign in to post in the forums.
4/21/2011 1:19:20 PM
Gravatar
Total Posts 76

StyleSheetCombiner Skin Versioning?

I have run into an issue in my last deployment.

The mojoportal version stayed the same, but my css and skins where updated.

The StyleSheetCombiner had the same url

'/csshandler.ashx?skin=MySkin&s=1&v=2.3.6.4'

so it was cached locally on my clients... (lead to the CTO coming to complain, until he pressed F5)

I think we possible need to extend the skin's style config to have a style version number?

'/csshandler.ashx?skin=MySkin&skinv=4&s=1&v=2.3.6.4'?

<cssfiles version="4">...

Thoughts?

 

Warner

4/21/2011 1:35:39 PM
Gravatar
Total Posts 18439

Re: StyleSheetCombiner Skin Versioning?

Hi Warner,

The best solution is just to rename the skin and use a version as part of the skin name, like the skin on this site is mojo_v34 and I keep incrementing the _v part whenever I make a change.

Using the latest mojoportal you could even make small css tweaks right from the browser. Under Administration > Advanced Tools > Design Tools, there is a place where you can set a cookie to prevent your browser from caching while you edit (so you don't need to disable caching from web.config), and there is also a way to copy a skin as a new name so after you finish tweaks, you can go into your skin and copy it as yourskin_vx, (where x is the next version) then change the site to that skin and it will make all users see your changes because the skin name changed and therefore the url changed so it is not cached already.

Hope it helps,

Joe

 

4/21/2011 1:41:32 PM
Gravatar
Total Posts 76

Re: StyleSheetCombiner Skin Versioning?

Thanks Joe, smiley

I will try that out next deployment.

Warner

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