upgraded to 2.2.1 and some css not loading

[Gavin_+ 55]

Hi we have a live site here http://www.atab.org.uk/ and as you can see we have customised the home pages for a widget box to sit next to the feature slider we have upgraded to 2.2.1 on our test site http://test.atab.org.uk/ and along with the expected sidebar widget issue you will notice that the modification to the feature area is not loading. we have tried copying in all the css from scratch but it is not loading the modifications. any ideas? thanks

[Danny 1,327]

Hi Gavin, Can you post the CSS that is not working since the 2.2.1 upgrade please ?

[Gavin_+ 55]

Hi Danny from test site: CSS [code]#features { background: URL(/wp-content/uploads/2012/01/snow.png); border-top: 1PX SOLID #E3E3E3; } #feature_slider { position: relative; z-index: 0; overflow: hidden; width: 48%; float: left; padding: 0 1%; } .fset_height,#feature_slider .text-bottom .fmedia .dcol-pad,#feature_slider .text-bottom .feature-pad,#feature_slider .text-none .fmedia .dcol-pad{ height: 390px; overflow:hidden; } .fcontent .ftitle { font-size: 1.5em; font-weight: lighter; vertical-align: middle; } #feature_slider .fcontent { width: 55%; } .fcontent .fheading { margin-bottom: 0.7em; padding: 0 0; } */ #features { background: URL(/wp-content/uploads/2012/01/snow.png); border-top: 1PX SOLID #E3E3E3; } .fcontent .ftitle { font-size: 1.5em; font-weight: lighter; vertical-align: middle; } #feature_slider .fcontent { width: 100%; background: #fff; } .fcontent .fheading { margin-bottom: 0.7em; padding: 0 0; } .fexcerpt{ color: #000; text-shadow: none; } #feature_slider .fcontent a { color: #000; text-shadow: none; } .fset_height { height: 352px; border-bottom: 1px dashed #AAA9A9; -webkit-box-shadow: 0px 0px 5px 3px #E3E3E3; -moz-box-shadow: 0px 0px 5px 3px #e3e3e3; box-shadow: 0px 0px 5px 3px #E3E3E3; } .fheading { display: none; } #feature_slider .fcontent .dcol-pad { padding: 0; } .float-left-new{ float:left; width: 48%; padding: 1%; } .float-right-new{ float: right; width: 48%; padding: 1%; } .thick-top-border { border-top: 6px solid; } .red-new{ border-color: #D01C3B } .orange-new{ border-color: #F46F16 } .purple-new{ border-color: #9F3DE5; } .hover-red:hover{ background: #D01C3B; color: #000; text-shadow: none; padding: 2px; } .hover-orange:hover{ background: #F46F16; color: #000; text-shadow: none; padding: 2px; } .hover-purple:hover{ background: #9F3DE5; color: #000; text-shadow: none; padding: 2px; } #feature_slider .fcontent a:hover { color: #000; } .widget_categoryposts { min-height: 250px; } .clear{ clear:both; } /* Homepage Category News */ #custom-homepage-news { width: 48%; float: left; padding: 0 1%; background: white; border-bottom: 1px dashed #AAA9A9; -webkit-box-shadow: 0px 0px 5px 3px #E3E3E3; -moz-box-shadow: 0px 0px 5px 3px #e3e3e3; box-shadow: 0px 0px 5px 3px #E3E3E3; } #custom-homepage-news ul li.cat-post-item a{ color: #000; padding: 2px; } #custom-homepage-news ul li.cat-post-item a:hover{ background: #D01C3B; padding: 2px; } #custom-homepage-news .textwidget { padding: 0; text-align: center; } #custom-homepage-news .widgettitle{ display: none; } #custom-homepage-news ul li{ width: 46%; float: left; } [/code] PHP [code]if ( function_exists('register_sidebar') ) register_sidebars( 1, array( 'name' => 'widgetized-page-top-news', 'before_widget' => '

', 'after_widget' => '

', 'before_title' => '

', 'after_title' => '

' ) );[/code]

[Danny 1,327]

Hi Gavin, You have two minor errors in the CSS. [code].red-new{ border-color: #D01C3B } .orange-new{ border-color: #F46F16 }[/code] Both are missing ; after Hex color code. Can you fix this and see if this resolves the problem. Also, are you receiving any Parse errors at all ?

[Gavin_+ 55]

Hi Danny no that hasn't changed anything where would i find parse errors? cheers

[catrina 103]

The parse errors should show up on the page where the errors are located (they're basically syntax errors/errors in the code).

[Gavin_+ 55]

There are no parse errors. this all worked perfectly before the upgrade and now doesn't work after the upgrade... so whats next? we have a live site here http://www.atab.org.uk/ and as you can see we have customised the home pages for a widget box to sit next to the feature slider we have upgraded to 2.2.1 on our test site http://test.atab.org.uk/ and along with the expected sidebar widget issue you will notice that the modification to the feature area is not loading. we have tried copying in all the css from scratch but it is not loading the modifications. any ideas?

[Danny 1,327]

Hi Gavin, Some of your custom CSS for features is commented /* CSS Here */ is this correct ? I have added it below for you to see. [code]-----If not added on purpose, then remove------> /* #features { background: URL(http://www.atab.org.uk/wp-content/uploads/2012/01/snow.png); border-top: 1PX SOLID #E3E3E3; } #feature_slider { position: relative; z-index: 0; overflow: hidden !important; width: 48% !important; float: left !important; padding: 0 1%; } .fset_height,#feature_slider .text-bottom .fmedia .dcol-pad,#feature_slider .text-bottom .feature-pad,#feature_slider .text-none .fmedia .dcol-pad{ height: 390px; overflow:hidden; } .fcontent .ftitle { font-size: 1.5em; font-weight: lighter; vertical-align: middle; } #feature_slider .fcontent { width: 55%; } .fcontent .fheading { margin-bottom: 0.7em; padding: 0 0; } */ <]-----If not added on purpose, then remove------[/code] Has this been added on purpose as this would prevent your CSS for loading.

[Gavin_+ 55]

Hi Danny The css on the test site is exactly the same as the css on the live site - yet it is not working on test site anymore after update i dont really know why that code is commented out but that is the same as on the live site where everything is working

[Jenny 33]

You have an error in your feature html: [code]

We help you make your Air Miles go further

[/code] Notice the lack of ending "strong" and "p" tags? That throws off everything else. You also have a duplicate "allowfullscreen" code at: [code][/code] Looks like you also have Universal Sidebar active with nothing in it. Whenever something doesn't behave as it should, always check your html to ensure you don't have errors in your code. :)

[Gavin_+ 55]

Hi thanks for the those ideas but that was not what the problem was. i apologise for wasting time here - the developer who did the work was not completely honest about the changes they had made. i can only imagine they were too busy to really respond and came up with a trite - the css is not loading from pagelines plugin its their problem speak to them - when in fact, what they revealed last night, was that they had changed php inside the feature section area and i pointed out to them that this was subsequently overwritten with the upgrade. this i find quite surprising as i did explain to them the need to create sections and use the customise plugins to prevent this happening. what a pain. this experience really reinforces the principle of having a test site that you make changes on...

[Jenny 33]

Thanks for the update, Gavin. That's never good. :( Hopefully you're able to get everything straightened out. If you consider this topic resolved, please "accept" an answer - thanks!