Options Theme Version 1.1.7

V1.1.7 Of the Options theme introduces a couple of new features and fixes a few errors in V1.1.6.

Errors Fixes:
Shadows:
Previously, using shadows with the page header or footer attached to the content container resulted in some grey lines (from the shadow) showing through.
This has now been fixed.
Snippets: Search bar snippet script had a typo which caused it to go slightly wrong (extraContainer1 instead of myExtraContent1).

Updates for 1.1.7

Opacity:
Transparent background/header graphics lightened slightly. This allows the image/colour underneath to show through better.
Snippets: Snippets added to allow both a chosen colour (solid or colour gradient) and a single background image to be shown at the same time. There are now 34 versions of the translation snippet (1 version for each language supported by the snippet). A new OSX search box snippet has been added.
Logo Alignment/Location: This has been updated to allow the logo to be placed much more precisely. There are now 42 variations for to choose from (14 from top, 14 from left, 14 from right)

Content and Sidebar Content Capitalisation (Deluxe Versions Only): The Conten Container and sidebar content and now be altered to show 5 different Capitalisations (Normal, First Letter Of Each Word Capitalised, All Lower case, First letter of each word is in Large Capital all others are Small Capitals, All Letters Upper Case). This has not been included in The lite versions.

Scripts: jQuery 1.6.4 has been added to the installable scripts.

From now on purchasers will be given access to beta test versions to test out new/improved features. Once the new features are working properly they will be added to future releases.

Options Theme Version 1.1.6

V1.1.6 Of the Options theme introduces a couple of new features and fixes a few errors in V1.1.5.

Errors Fixes:
The 35px Horizontal menu below the header had a small error where the buttons were too small.
This error has been fixed for V1.1.6.
The horizontal menus are in the process of being completely re-designed and will be released in a future update.

Updates for 1.1.6
Background Images:
Adding background colour gradients caused an error in MSIE. MSIE prevented background images from being displayed properly whilst there was a colour gradient actve. As a result the background colour gradient was removed for MSIE. However, a set of 4 images has now been added to simulate the colour gradient (top, right, bttom, left) and bypass the MSIE error.

Font Family: A Georgia fornt family has now been added and made the default fonty family (it displays better on compputer screens). This brings the total font families up to 20.

Heading Shadows: Shadows have now been added to headings in content and sidebar areas (h1, h2, h3, h4, h5, h6) to make them look better.

Menu Capitalisation (Deluxe Versions Only): Menu button text can now be altered to show 5 different Capitalisations (Normal, First Letter Of Each Word Capitalised, All Lower case, First letter of each word is in Large Capital all others are Small Capitals, All Letters Upper Case). This has not been included in The lite versions.

Scripts: Active Bar 2 jquery script and snippet added to the theme.

Options Theme Version 1.1.5

V1.1.5 Of the Options theme introduces a couple of new features and fixes a few errors in V1.1.4.

V1.1.4 Errors Corrected

Title/Slogan Capitalisation: If the Title or Slogan Effects were set at the "No Effects" (default value) then the Title or Slogan Capitalisation would not work. If any other effects (shadow or glow) were chosen then the capitalisation would work. This has now been fixed.

Colour Fault in MSIE:
Colours for V1.1.4 were reverting to default colours in some areas when viewed in MSIE. This occured when some MSIE colourtag values had not been converted to top and botttom colours when colour gradients were introduced. This has now been fixed.

FAQMaker Sidebar Questions List: The default list was appearing in the middle of the sidebar instead of near the left hand side. This has now been fixed.

Updates/New Styles:
  • Sidebar Line Height: 11 heights up to 2.0em (32px)
  • Content Line Height: 11 heights up to 2.0em (32px)

Adam Merrifield and Seydoggy

A big thank you to Adam Merrifield from Seydoggy for his help with some jquery scripting errors and extra container problems that cropped up in the development of V1.1.4.

Without his help this update would have taken a lot longer to release.

Weaver FM Version 1.1.0

There appears to be a small error that only affects themes with menus or links that are at the top of the screen.
If the bottom edge of the WeaverFM "Login Tab" (which is 42 pixels from the top) ends below the menu/link then it stops working.

Of the themes that come with Rapidweaver only Aqualicious, Caribou, Possible and Simple Business are affected (to a lesser or greater extent).

Unfortunately this fault also affects our Options Themes' Horizontal menu above the header. It may also affect the website link in the logo to a lesser extent if the Horizontal menu above the header is not used.

Solution
To fix this the menu (or link) must be moved below the bottom edge of the "Login Tab" (below 42px from the top).

With the Options theme it is fairly easy to fix. All you have to do is increase the top margin at least 40px, or choose a different menu location.

If you find that you cannot do this with your chosen theme you may have to choose another one.

Validation Errors

If this theme is validated at http://jigsaw.w3.org/css-validator (with the validation level set at 3) it will show several errors and. Whilst we try to reduce these as much as possible some cannot be avoided if our theme is to remain flexible and useful (believe it or not).

Our problem is that two of the Legal CSS3 browser specific commands (-webkit for safari browsers and -moz for firefox browsers) we use for curves and shadows cause a "Property doesn't exist" error when validating the theme at http://jigsaw.w3.org/css-validator. The catch is that if we didn't use these commands then we would have to draw all the curves and save them as images and then load them into the page. This would dramatically increase the complexity, development time and cost of a theme whilst reducing flexibility and usefelness (such as reducing the colours used in menus and corners).

In the end every theme designer has to work out for themselves how many errors/warnings they will put up with in order to produce a theme that is both flexible and useful.

With our theme the errors have been limited to the following style locations:
  • Shadow (5px, 10px, 15px, 20px)
  • Curves (5px, 10px, 15px)
  • Header/Location (Where the Header and/or Footer are attached)
  • Menu/Types (only ones with rounded buttons)
  • File Sharing/Boxes (The curved boxes)
If you do not want any of these "validation errors" appearing in your theme then do not use these particular styles. If you do not care and like the look of these styles then feel free to use them.

Below are the Legal CSS3 commands used that cause the Property doesn't exist validation error.
Equally Rounded Corners
-webkit-border-radius (Webkit/Safari)
-moz-border-radius (Firefox)

Individually Rounded Corners

Webkit/Safari
-webkit-border-top-left-radius
-webkit-border-top-right-radius
-webkit-border-bottom-left-radius
-webkit-border-bottom-right-radius

Firefox
-moz-border-radius-topleft
-moz-border-radius-topright
-moz-border-radius-bottomleft
-moz-border-radius-bottomright

Box Shadow
-webkit-box-shadow (Webkit/Safari)
-moz-box-shadow (Firefox)

Faulty Pages Update

Hi all,

We have just noticed a couple of pages that needed fixing:
  • Payloom 2 and,
  • Slider.
These faults were not the result of the theme. We forgot to reduce the content width (by 200px) in the setup of these 2 plugins when we moved the sidebar to the right hand side of the page. Our Bad, Sorry.

Thermite