CSS not updating

A place for discussion about skinning and design. Before posting questions here you should review the documentation about creating skins.

This thread is closed to new posts. You must sign in to post in the forums.
7/20/2012 2:15:14 PM
Gravatar
Total Posts 30

CSS not updating

What operating system - Win Server 2003, SP2 (so that's IIS 6)
What database platform? MS SQL 2008
What version of mojoPortal? 2.3.9.0
What browser? FireFox 14.0.1 (latest)

I installed the CMS, and am now walking through the post-setup steps and testing. In looking at the settings and clicking the "?" button to get help info, the help text is running outside of the box making it non-readable. I have spent hours looking through different search results on the mojoportal.com site to attempt to find a fix and do my part before opening an issue/thread. I found the CSS setting I need (adding "min-width: 0;" to the "body.help-page" section. That's what works in Firefox using Firebug, because the CSS inherits min-width: 1000px; from the main body tags, even in this help iframe - so you've got the help divs and iframe scaled to below 900px but the body text still goes out to 1000px like the page... Problem is I cannot get the CSS to update/cooperate. Either not using the right CSS file, which I believe I am, or it's not clearing cache, which I've done.

I have added that specific CSS setting to that specific section of the \Data\skins\artisteer31-green\style-artisteer-overrides.css file. Saved it. I have refreshed web.config and user.config and also recycled the app pool. I also set these to false in both user.config and web.config: MinifyCSS, CacheCssOnServer, CacheCssInBrowser. I also tried loading the admin pages in IE 9, so nothing was cached. Nothing seems to let the new CSS in that overrides.css file through.

Is there any way to disable the combine css function? That would make skinning alot easier. Any guesses as to why CSS changes I make are not taking after server and browser caching are disabled in configs and local browser cache is cleared?

PS. If you go to your demo site and click on help links in admin settings, you'll see the text disappear passed the help box too.

Oh, and 2nd PS. Noticed you can edit the help text, and read up on that on mojoPortal. Wonderful feature. Problem is, content editor has no save button, so editing help text doesn't work because it won't save the content.

Thanks in advance for any help. Need to get this hiccup figured out, as any CSS and skinning will be really hard if I can't find the right files or stop/clear the caching...

Spencer

7/20/2012 2:20:46 PM
Gravatar
Total Posts 18439

Re: CSS not updating

Hi Spencer,

It doesn't use skins from /Data/skins, that is just the catalog of skins that are copied to a new site upon site creation.

A site uses skins from under /Data/Sites/[SiteID]/skins

Possibly something failed to copy the during setup, if so you can manually copy the /Data/skins folder into /Data/Sites/1 so it lands as  /Data/Sites/1/skins

You may also need to go to Administration > Site Settings

Choose a skin from the skin dropdown then save site settings.

Hope that helps,

Joe

7/20/2012 2:42:23 PM
Gravatar
Total Posts 30

Re: CSS not updating

Well that makes sense now that I see it. Hard part about new CMS is learning the ins and outs and file structure. I made that change in the correct place under site/skins like you said and BAM it's effective =) Thanks! Should be able to work on skinning and formatting easier now that I'm in the right places. Now off to find a skin I like and start customizing. Thanks for all your work - it really shows on your website, documentation pages, and now in quick forum responses too.

PS. that css change fixed the other issue, and now I see Save and Cancel buttons when editing the help text box. I don't know if that help overlay/frame is global to all skins or not. Maybe there's a place I can set it once and it fixes help pop-up for all skins? If I find anything I'll post back - as changing that in your files would be good to help out of the box experiences for the help pop up text staying in the box.

Thx again!

7/20/2012 3:37:36 PM
Gravatar
Total Posts 30

Re: CSS not updating

You know more about all the different skins and which ones use that help iframe pop-up with "help-page" class (I'm trying out the extra ones too, so there's like 83), but this change seems to have gotten it globally instead of editing each skin override files.

File: Data\style\common\style.css

New Line: body.help-page {min-width: 0;}

Hope it helps someone else. Thx again for everything!

7/21/2012 12:07:49 PM
Gravatar
Total Posts 18439

Re: CSS not updating

Hi Spencer,

Really I think that problem is only caused by the artisteer skins,they put something like min-width: 1000px; on the body for some reason in their css and it makes things overflow the editor. So this fix of yours is really only needed to override the artisteer css, I'm thinking I will add it to the style-artisteroverrides.css files instead of putting it in the common css, just to keep the common css as small as possible. Even though this is a pretty small thing to add every little bit adds up.

Thanks,

Joe

4/15/2013 7:53:32 PM
Gravatar
Total Posts 3

Re: CSS not updating

 Hello , I am having the similar problem, running the current mojoProtal on localhost and trying to make the changes on style.css but it is not updating with changes. 

Action taken:  

1. disable cached disabled on user.config 
<add key="CacheCssOnServer" value="false"/> <add key="CacheCssInBrowser" value="false"/> 

2. tryed with different browser, force refresh, deleted the css class from the style.css but it is still showing on the page, 

OS: WIndows 7 , Current mojoProtal Version: 2.3.9.6 using skin : artisteer31-hovermenu 

is that any other way we could know what is the css file the class is calling from? 

4/15/2013 9:10:10 PM
Gravatar
Total Posts 211
Community Expert

mojoPortal Hosting & Design @ i7MEDIA!

Re: CSS not updating

Hey PrabirChoudhury,

Here are a few more steps you might want to take:

  1. Click "administration" in the admin toolbar, then click the "Advanced Tools" button. Next click "Cache Tool", and then click both the buttons "disable CSS caching" and "reset skin version GUID".
  2. Like Audette mentioned, make sure that you are editing the skin in /data/sites/#/skins, not the one in data/skins.

As for knowing what CSS file a class is calling from, download FireBug for Firefox, and when you select an element with it you will see the source. For a local server I suggest you disable CSS combining and minifying.

Hope this helps,
-Isaac

4/15/2013 9:26:05 PM
Gravatar
Total Posts 3

Re: CSS not updating SOLVED

Hi Isaac

Thanks for your response. yes found the problem, it was missing the virtual path references of the style.css file in style.config file

missing css virtual path: 
<file cssvpath="/Data/Sites/1/skins/style.css" imagebasevpath="/Data/Sites/1/skins/images/">none</file> 

but still file is being listed:  <file>style.css</file>

this was a confusion for the beginner like me. but finally found that missing  (or needed to add) part. 

 

cheers

4/16/2013 6:14:57 AM
Gravatar
Total Posts 18439

Re: CSS not updating

Hi,

<file>style.css</file> this syntax is for css files that are in the skin folder it does not need or use virtual path attributes cssvpath or imagebasevpath, the virtual path for the skin folder is already known from the syntax. The use of those attributes is only for when the css files are not inside the skin folder, like if using css from a common shared location

You should not have to hard code any virtual path attributes that point to a skin folder because then it must be updated if the skin is renamed or moved to a different site.

I personally do not recommend disabling CSS combining. If you do that then there is no control over cache and skin guid reset is irrelevant, plus you need to make sure it does work with css combining before deployment to production and people too often forget to re-enable it so they end up with lots of extra http requests in the page for each separate css file. You can disable minification and caching on your dev machine but I would not disable combining CSS. Generally you can figure out which css file a style rule is coming from by its location in the output css and the list of css files in style.config.

Hope that helps,

Joe

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