Problems with skinning (SVN revision 4398)

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.
11/9/2008 7:52:13 AM
Slaven Brumec
Gravatar
Total Posts 55
View Posts

Problems with skinning (SVN revision 4398)

Hello!

After updating (revision 4398) and running Setup/Default.aspx, mojoPortal skinning doesn't work. I get plain-text mojoPortal. It stays that way even after changing my current skin (somewhat modified andreasviklund-04) to any of mojoPortal's standard included skins. And yes, portal stays plain-text even after cleaning temporary files and folders in all browsers I have installed (IE, Firefox 3 and Chrome).

I use Win XP development machine with SQL Server. Being currently interested mostly in mojoPortal's data access features, I'm not quite at home with skinning features and so I kindly request help for this strange bug.

11/9/2008 7:56:47 AM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Problems with skinning (SVN revision 4398)

Hi Slaven,

Are you using a custom skin or an included one? There are recent changes to skinning that I have not yet documented. I implemented a solution to combine and minify css files.

For a custom skin, you should remove the <portal:StyleSheet control from layout.master and replace it with this:

<portal:StyleSheetCombiner id="StyleSheetCombiner"  runat="server" />

Then copy a css.config file from one of the included skins into your skin folder.

Then you may need to touch Web.config to clear the cache, and you may also need to clear your browser cache.

Hope it helps,

Joe

11/9/2008 11:05:30 AM
Slaven Brumec
Gravatar
Total Posts 55
View Posts

Re: Problems with skinning

I've used modified andreasviklund-04 skin. However, even when I change skin to some included version, for example styleshout bright side of life, problem remains: only heading picture (grassland) appears and the rest of portal is still plain text. In the mean time, I've dowloaded another SVN revision without effect.

Then I've looked into App_MasterPages/layout.master as you instructed me. There is no line that says:

<portal:StyleSheetCombiner id="StyleSheetCombiner" runat="server" />

...but there is still (old?) line that says:

<portal:StyleSheet id="StyleSheet" runat="server" />

Note that my SVN client does not report any conflict in entire App_MasterPages folder.

In Data/Skins/<SkinName> and in Data/Sites/1/Skins/<SkinName> layout.Master files do have StyleSheetCombiner. But, in entire solution folder, there's no any css.config file!

11/9/2008 11:15:08 AM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Problems with skinning (SVN revision 4398)

Hi Slaven,

My bad, I meant style.config not css.config, there is a copy of this file in each skin folder.

It doesn't matter about the /App_MasterPages file, just the ones in the skin folders are used at runtime.

Hope it helps,

Joe

11/9/2008 11:20:57 AM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Problems with skinning (SVN revision 4398)

Make sure you have this in your Web.config <httpHandlers section

<add verb="*" path="*csshandler.ashx" type="mojoPortal.Web.UI.CssHandler, mojoPortal.Web" />

It should already be there unless you had any conflicts with svn update.

To troubleshoot it I would view the source of the rendered page and see where it is getting its css from then view the css url in the browser to see the actual css.

Another setting you can try is

<add key="MinifyCSS" value="true"/>

You may try setting it to false. The Css is still combined but its not minified.

Hope it helps,

Joe

ps, I've got major changes to land in trunk tomorrow

11/9/2008 11:38:20 AM
Slaven Brumec
Gravatar
Total Posts 55
View Posts

Re: Problems with skinning

I have both http handlers section and minifycss key correct but still have plain text mojoPortal, even after setting minifycss to false. Never mind, I'll wait for those major changes in trunk tomorrow.

11/9/2008 11:44:04 AM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Problems with skinning (SVN revision 4398)

Ok, I just now updated this site to the latest code from my sandbox which wil merge to trunk by tomorrow. I did major surgery and moved all of the features except the Html module out of the core projects and into mojoPortal.Features.

Hopefully I didn't introduce any new bugs, it seems ok so far on this site.

Best,

Joe

11/10/2008 6:46:39 AM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Problems with skinning (SVN revision 4398)

Hi Slaven,

I woke up this morning and realized what was causing this, was able to produce it and fix it on my system and I committed the corrections to trunk.

Should be fixed if you do svn update, rebuild solution, visit /Setup/Default.aspx, clear your browser cache.

I'm still working on the big merge of other changes, it timed out and I had to restart, having connectivity issues with the repository.

Best,

Joe

11/10/2008 11:17:47 AM
Slaven Brumec
Gravatar
Total Posts 55
View Posts

Re: Problems with skinning (SVN revision 4398)

Now, everything works fine.

I noticed that lot of files and folders are not included in project any more: Poll and WebStore folder and RSS*.* files and Blog*.*, for example. I presume that's because of moving those files and folders to mojoPortals.Features.UI project. So, is it safe to delete those unincludes? It seems to me that code in Setup.aspx.cs doest not contain any file deleting methods.

11/10/2008 11:32:13 AM
Joe Audette
Gravatar
Total Posts 18439
View Posts

Re: Problems with skinning (SVN revision 4398)

I deleted what could be deleted safely. Those files are needed for backward compatibility of upgraded installations.

Example the old forum pages does 301 redirect to new forum pages to prevent broken links and search results.

BlogView.aspx must be there or old blog posts whose real url was mapped to BlogView.aspx in mp_FreindlyUrls will still work.

If you look inside the files in question you will see notes that they "can" be deleted for new installations. But you don't want to delete them if working from svn, they will just come back when you do svn update.

Best,

Joe

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