Internet Explorer 8

IE8 Pseudo Command Fix

Internet Explorer 8 (and earlier) does not recognize some very powerful pseudo commands, such as ‘first-of-type’, ‘last-of-type’, ‘only-of-type’, ‘nth-of-type’, and ‘nth-last-of-type’ which the follow jQuery snippet fixes. IE8 does support ‘nth-child(last)’ and ‘nth-child(first)’ and other nth-child commands – also ‘last-child’ and ‘first-child.’ However, those are all dependent on the element recognizing children to parent relationships (i.e. ordered and unordered lists) and will not recognize elements simply by them being inside one of another (i.e. a div tag containing a series of other div tags… that’s when you use ‘type’ instead of ‘child.’

If you are creating an addon or have one that uses one of those commands then simply paste the following code to the Page Info > Header > JavaScript of the page (in RapidWeaver).

All credit to Keith Clark on this one – great simple fix.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
/*
 * jQuery Extra Selectors - (c) Keith Clark freely distributable under the terms of the MIT license.
 * twitter.com/keithclarkcouk
 * www.keithclark.co.uk
 */
 
(function($) {
     function getNthIndex(cur, dir) {
          var t = cur, idx = 0;
          while (cur = cur[dir] ) {
               if (t.tagName == cur.tagName) {
                    idx++;
               }
          }
          return idx;
     }
     function isNthOf(elm, pattern, dir) {
          var position = getNthIndex(elm, dir), loop;
          if (pattern == "odd" || pattern == "even") {
               loop = 2;
               position -= !(pattern == "odd");
          } else {
               var nth = pattern.indexOf("n");
               if (nth > -1) {
                    loop = parseInt(pattern, 10) || parseInt(pattern.substring(0, nth) + "1", 10);
                    position -= (parseInt(pattern.substring(nth + 1), 10) || 0) - 1;
               } else {
                    loop = position + 1;
                    position -= parseInt(pattern, 10) - 1;
               }
          }
          return (loop<0 ? position<=0 : position >= 0) && position % loop == 0
     }
     var pseudos = {
          "first-of-type": function(elm) {
               return getNthIndex(elm, "previousSibling") == 0;
          },
          "last-of-type": function(elm) { 
               return getNthIndex(elm, "nextSibling") == 0;
          },
          "only-of-type": function(elm) { 
               return pseudos["first-of-type"](elm) && pseudos["last-of-type"](elm);
          },
          "nth-of-type": function(elm, i, match) {
               return isNthOf(elm, match[3], "previousSibling");
          },
          "nth-last-of-type": function(elm, i, match) {
               return isNthOf(elm, match[3], "nextSibling");
          }                
     }
     $.extend($.expr[':'], pseudos);
}(jQuery));

(function($) {
function getNthIndex(cur, dir) {
var t = cur, idx = 0;
while (cur = cur[dir] ) {
if (t.tagName == cur.tagName) {
idx++;
}
}
return idx;
}
function isNthOf(elm, pattern, dir) {
var position = getNthIndex(elm, dir), loop;
if (pattern == "odd" || pattern == "even") {
loop = 2;
position -= !(pattern == "odd");
} else {
var nth = pattern.indexOf("n");
if (nth > -1) {
loop = parseInt(pattern, 10) || parseInt(pattern.substring(0, nth) + "1", 10);
position -= (parseInt(pattern.substring(nth + 1), 10) || 0) - 1;
} else {
loop = position + 1;
position -= parseInt(pattern, 10) - 1;
}
}
return (loop<0 ? position<=0 : position >= 0) && position % loop == 0
}
var pseudos = {
"first-of-type": function(elm) {
return getNthIndex(elm, "previousSibling") == 0;
},
"last-of-type": function(elm) {
return getNthIndex(elm, "nextSibling") == 0;
},
"only-of-type": function(elm) {
return pseudos["first-of-type"](elm) && pseudos["last-of-type"](elm);
},
"nth-of-type": function(elm, i, match) {
return isNthOf(elm, match[3], "previousSibling");
},
"nth-last-of-type": function(elm, i, match) {
return isNthOf(elm, match[3], "nextSibling");
}
}
$.extend($.expr[':'], pseudos);
}(jQuery));

Consolidate CSS

What is it?

The Consolidate CSS option can be found in the RapidWeaver > Preferences section as a Publishing > Advanced option.

Consolidate CSS

By default RapidWeaver will not consolidate your CSS files.

If selected, all your CSS files will be combined into one CSS file. This works well with RapidWeaver’s built-in themes, but can cause major conflicts with 3rd party developers’ themes and more specifically with those that have a high amount of customization options.

What Use It?

The only reason, that I’m aware of, why anyone would like to use this option is entirely due to Internet Explorer’s (IE) nonsensical structure. IE is the only mainstream browser on the market that limits the amount of stylesheets that can be called within a single webpage. If you go over that limit, 31 stylesheets, all additional stylesheets (32 and up) will be completely ignored.

Well of course Microsoft has realized this problem and made sure to stop such nonsense in the latest versions of IE (8, 9, 10) right? NOPE! They haven’t – nothing has changed in this area. If you’re running IE6 or IE10 you are still limited to this archaic rule. Will they ever fix this? My guess is no, because they don’t care at all about their customers or developers as you might have noticed, whether you follow any of their products (i.e. Windows, Office, XBox, etc).

My Recommendation

If you’re using a browsers with built-in code inspecting tools, my favorite being Chrome, you can right click and select “Inspect Element,” which will bring up a section in your browser where you can view the code. If you go to “Resources” you can see all the stylesheets that are being called in.

I recommend that if this amount is not over 31 then you really have no reason to consolidate CSS.

A majority of our themes often contain a stylesheet count somewhere in the lower 20’s. Why so many? RapidWeaver structure requires theme style options to work largely by alternating between different stylesheets – in other words, it’s just the way RapidWeaver is built.

What if I have a ton of Stacks on a page? No worries there – Stacks already consolidates the CSS, so if you have one stack or several there is still only a single stylesheet being called in.

cleanTabs rapidweaver stack

cleanTabs 2.0.0 Major Update

cleanTabs is one of our top selling stacks and we have received tons of requests over time, which has led to a huge update adding some awesome new features and some compatibility fixes.

  • Fully compatible back to Internet Explorer 8
  • Theme 1 compatible back to IE 7
  • Fully Responsive with controls to adjust to varying themes
  • 3 New Minimalist themes
  • Fix compatibility in some themes caused by CSS 3 backface-visible conflict
  • Improved backend interface
  • Reorganized customization options area
  • Customization option added – change the initial tab that is open
  • Width customization option default changed to 98% (fixes right-side border from cutting in some stack columns)
  • Firefox :focus outline fix (caused minor display issues)
  • Fixed issue where tab clicks would effect multiple instances of cleanTabs on a single page

Internet Explorer 10 Released

If the headline of this post didn’t interest you much then hats off to you – you’ve probably realized that Microsoft’s onslaught of advertisements, as impressive as they were, had little to no truth in them and the Internet Explorer (IE) is perhaps the worst internet browser on the market. Perhaps you don’t use IE for another purpose though… there’s probably a slew of reasons not to use it.

If you are a developer IE 10 does move in the right direction now finally supporting much needed CSS3 effects that pretty much every other browser already supports. On top of that you’ll still need to code accordion to IE 9 because IE doesn’t automatically upgrade its users (in any versions of the browser) and IE 10 requires Windows 7.

The browser does run a tested 20% faster, though if you are running Windows XP and upgrade to 7 to get IE 10 then your Windows software will now be running about 20% slower (or worse), which means your browser may not be running faster at all and now your whole computer runs slower.

If you are not a developer and you already have Windows 7 then the upgrade is a “no brainer” and you should definitely go download it. Though I’m guessing you will not notice too much change. Maybe it will launch a tiny bit quicker and you will now be able to see some of the cool CSS 3 effects such as gradients and transitions (subtle animation effects). However, you still will not have access to inspect code elements like you can in most other browsers now, which is a huge downside in my opinion.

My recommendation – if you haven’t already just forget IE all together and go get Google Chrome.

If you just can resist though, go ahead and upgrade to IE 10.

Resources – SitePoint

cleanAccordion Rapidweaver Stack logo

cleanAccordion 1.4.9 Update

This update includes the following changes to the cleanAccordion RapidWeaver Stack:

  • Added more support for IE9
  • Removed unnecessary files
  • 1px Margin added to right hand side of the container element – fixes a 1 px issue that occurred in some sizes during responsiveness

To get the latest version please use the Order Lookup Form. If you still have difficulties please contact our support email.

cleanAccordion Rapidweaver Stack logo

cleanAccordion 1.2.0 Update

Changelog

NOTE: If you downloaded before 9/15/2012 that you will lose description text when you update. Please save this information before updating. Description data replaced with Slice command so you can drag and drop other stacks inside (i.e. HTML, Text, Columns, etc.).

9/19/2012

  • Moved Accordion Count option (New selection labels “first accordion”) – this sets the accordion class if there are more than one container on the page (global styling applied).
  • Added Support for older browsers added.
  • Internet Explorer Fixes – makes more presentable for older IE browsers (6+) though the functionality still has issues. IE9 keeps gradients, though border radius is only option for theme 2 in IE9 (part of IE’s gradient structure).
  • Sets padding & margins to zero for some theme issues effecting DT & DD calls.

9/16/2012

  • Multi-containers first added (explained more above in 9/19 update).
  • Auto-open option available for first Accordion tab.

9/14/2012

  • Removed font-size call inside description container
  • Bottom border added in description container for Theme 2
  • Clearfix added to the cleanAccordion container (caused conflicts in some themes)
  • Description container no longer allows for text entry, but instead is a container for additional stacks. So you can drag and drop whatever the heck you want in it without limitations.
Cabernet 2.0 RapidWeaver Theme Screenshot

Cabernet 2.0 Release

Cabernet 2.0 is fully responsive and not in a little way!

The theme beautifully animates into position for any screen size, tablet or mobile device.

An extremely minimalistic and photogenic oriented theme that takes your creativity and magnifies it to the next level.

Some of the key features include:

  • Full Page Slider
  • Responsive
  • 8 Elegant Fonts
  • Animated Sidebar
  • Gallery Controls
  • 62 Social Media Icons
  • 4 Background Accents
  • Pretty Photo Viewer
  • Compatible back to IE7
Conversa RapidWeaver Theme Screenshot

Conversa Theme Update V1.5.0

conversa screen shot

New Features:

  • 8 New Textures
  • New Colour Options
  • New Option to change the Height of the Banner (100px-650px)
  • New Option to add texture to the Main Content
  • New layout Options for the Banner & Main Content Areas
  • New design & layout for mobile devices
  • New Option for the Slider captions to change from a solid color to transparent white or black

Bug Fixes:

  • Now compatible with the “Consolidate CSS” option in the preferences menu
  • IE8 and earlier compatibility enhancements
  • Shadows & Coloring fixes
  • Other minor bug fixes

Check it out