Weaver II Theme Documentation -- Version 1.0

See the Release Notes for a summary of changes from the previous Weaver

Weaver II represents a significant upgrade from the previous version of Weaver. It has been almost completely rewritten, and includes many new features. It now generates HTML 5 code to keep your site up to date with the latest Web standards. The handling of sidebars has been totally changed, resulting in complete flexibility of when and where you use sidebars.

If you are upgrading from the previous version of Weaver, Weaver II can perform an automatic conversion of most of your previous settings. But because some of the basic page organization of Weaver has changed, certain elements of your old site might require some manual conversion. This will most likely be true for sidebar arrangement and content, as these have been totally restructured. In the end, however, these manual fixes are likely to take only a few minutes.

Table of Contents

tag (or an extra
). HTML uses
...
blocks to determine different parts of a web page. If your content has a missing
tag, then the bad HTML will confuse your browser, resulting in the incorrect display of the sidebar.


Weaver II allows you to have as many widget areas you need. These new widget areas can be displayed on a per page basis. For example, using the Per Page options when you edit a page, you could have a different Top Widget Area, as well as different Primary, Upper, and Lower sidebars for every single page of your site if you wanted. You tell Weaver II to create these areas by providing a list of Widget Area names in this option area. The names should be letters, underscores, or numbers, and not include any spaces or other special characters. You can name them as you will - mytop,mytop2,myprimary and so on. These names are then used in the Per Page option area on the Page Editor screen to specify new or replacement widget areas. They also can be used by the Weaver II Pro widget area shortcode.

Special Sidebar Handling for Some Plugins
Weaver II uses an approach to generating sidebars that may conflict with some plugins. For example, there are some e-commerce plugins that generate an equivalent of their own page template that does not know about all the Weaver II sidebar layout options. Typically, these plugins will generate a

for the content area, and then invoke a theme specific file called "sidebar.php". Normally, Weaver II does not use that file, but provides a special version just for these plugins.

Here's how it works. Weaver II will check for a extra widget area called plugin_replacement (you would create it on the Main Options:Widget Areas tab). If it finds that widget area defined, it will generate a