This tab allows you to define custom code and style rules to the <HEAD> Section of every page on your site.
PLEASE NOTE: Only minimal validation is made on the field values, so be careful not to use invalid code.
Invalid code is usually harmless, but it can make your site display incorrectly. If your site looks broken after make changes here,
please double check that what you entered uses valid HTML or CSS rules.
Custom CSS Rules
Add your own custom CSS Rules to Weaver II's style rules
This section allows you to add new CSS Rules to your theme to enhance or override the styling set using
Weaver's Main Options. For example, Weaver's documentation includes many CSS Snippets that allow you
to find tune the look of your site. You simply add whatever CSS Rules you need into the box below. Include the
complete rule. You do not need to add <style> HTML tags to bracket your rules.
Rules you add here
will be the last CSS Rules included by Weaver, and thus override all other Weaver generated CSS rules.
It is possible that other plugins might generate CSS that comes after these rules.
<HEAD> Section
This input area allows you to enter custom HTML such as <link> and <meta> statements, or JavaScript code to your site.
Code entered into this box is included right before the </HEAD> HTML tag on each page of your site.
Shortcodes are not supported in this option.
We recommend using dedicated WordPress plugins to add things like ad tracking, SEO tags, Facebook code, and the like.
Note: Use the "Custom CSS Rules" option above to add custom CSS Rules to your site.
You can also add code to the <HEAD> section on a per page basis using the per page options from the page editor.
Due to WordPress.org theme standards (since WP 3.9), this option is not supported
by Weaver II Free. You must install the Weaver II Theme Extras plugin, or have Weaver II Pro to add
code to this option.
Weaver II will always load the jQuery Library.
<HEAD> Section (Advanced Alternative - ♦)
Same as normal <HEAD> box above, but works like other ♦ options - it survives changing
the subtheme from the Weaver II Subthemes tab, and is saved only on a full backup Save. This option is
not commonly used, and is intended for more advanced Weaver II users to add <script> and <style>
blocks to the <head> section.
Actions and Filters
This Option for Advanced Users! You can add arbitrary PHP code here. This option is intended to allow
you to add WordPress Actions and Filters to your own site. This PHP code is executed at the very
beginning of the theme's header.php template file before any site HTML is emitted. Do NOT bracket the code with <?php and ?>. See the Help file for more technical details.
Weaver II Pro Feature:Actions and Filters allows
you to add arbitrary PHP code to support WordPress Actions and Filters on your own site. ";
}
} // not multisite
weaverii_hide_advanced('end');
}
function weaverii_adv_html_insert() {
weaverii_hide_advanced('begin');
?>
HTML Insertion
The Advanced Options→HTML Insertion tab allows you to insert custom HTML code in many places on your site.
These fields allow you to add HTML code, special CSS rules, or even JavaScripts. You will need at least
a bit of knowledge of HTML coding to use these fields most effectively.
The values you put here are saved in the WordPress database, and will survive theme upgrades and other changes.
PLEASE NOTE: Only minimal validation is made on the field values, so be careful not to use invalid code.
Invalid code is usually harmless, but it can make your site display incorrectly. If your site looks broken after make changes here,
please double check that what you entered uses valid HTML or CSS rules.
'Site Header Insert Code', 'id'=>'header', 'info'=>
"This HTML code will be inserted into the #branding div header area right above where the standard site
header image goes. You can use it for logos, better site name text - whatever. When used in combination with hiding the site title,
header image, and the menu, you can design a completely custom header. If you hide the title, image, and header, no other code is generated
in the #branding div, so this code can be a complete header replacement. You can also use WP shortcodes to embed plugins, including
rotating image slideshows such as Aspen Themeworks Show Sliders.", 'help' => ''),
array ('name'=>'Footer Code', 'id'=>'footer', 'info' =>
'This code will be inserted into the site footer area, just before the before the copyright and "Powered by" credits, but after any Footer widgets (check option below to move to before widgets). This could include extra information, visit counters, etc.',
'help' => ''),
array ('name'=>'Pre-Wrapper Code', 'id'=>'+prewrapper', 'info' =>
'This code will be inserted just before the #wrapper and #branding divs, before any other site content. (●Pro)',
'help' => ''),
array('name'=>'', 'id'=>'submit', 'info' => '', 'help' => ''),
array ('name'=>'Pre-Header Code', 'id'=>'preheader', 'info' =>
'This code will be inserted just before the header area (between the "#wrapper" and the "#branding" divs), above the menus and site image.',
'help' => ''),
array ('name'=>'Pre-Main Code', 'id'=>'+premain', 'info' =>
'This code will be inserted after the #branding div and before the #main div. (●Pro)',
'help' => ''),
array ('name'=>'Pre-Container Code', 'id'=>'+precontent', 'info' =>
'This code will be inserted inside the #container div that wraps content, including before the top widget areas. It will have the same width as the container area. (●Pro)',
'help' => ''),
array ('name'=>'Post-Post Content Code', 'id'=>'+postpostcontent', 'info' =>
'This code will be inserted after the content area of each post. (●Pro)',
'help' => ''),
array('name'=>'', 'id'=>'submit', 'info' => '', 'help' => ''),
array ('name'=>'Pre-Comments Code', 'id'=>'+precomments', 'info' =>
'This code will be inserted just before the #comments div where comments are displayed. If comments
are open for the page, this area will include the class .precomments-comments, if closed .precomments-nocomments. (●Pro)',
'help' => ''),
array ('name'=>'Post-Comments Code', 'id'=>'+postcomments', 'info' =>
'This code will be inserted right after the #comments div where comments are displayed. If comments
are open for the page, this area will include the class .postcomments-comments, if closed .postcomments-nocomments. (●Pro)',
'help' => ''),
array ('name'=>'Pre-Footer Code', 'id'=>'+prefooter', 'info' =>
'This code will be inserted just before the footer #colophon div. (●Pro)',
'help' => ''),
array('name'=>'', 'id'=>'submit', 'info' => '', 'help' => ''),
array ('name'=>'Post-Footer', 'id'=>'postfooter', 'info' =>
'This code will be inserted just after the footer #colophon div, outside the #wrapper div.',
'help' => ''),
array ('name'=>'Pre-Left Sidebar', 'id'=>'+presidebar_left',
'info' => 'This code will be inserted just before the left sidebar area. (●Pro)',
'help' => ''),
array ('name'=>'Pre-Right Sidebar', 'id'=>'+presidebar_right', 'info' =>
'This code will be inserted just before the right sidebar area. (●Pro)',
'help' => '')
);
if ( ! weaverii_hide_advanced() )
weaverii_sapi_submit('', "
\n");
foreach ($areas as $area => $def) {
weaverii_add_html_field($def['name'],$def['id'],$def['info'],$def['help']);
}
weaverii_hide_advanced('end');
}
function weaverii_add_html_field($title, $name, $info, $help='') {
if ($name=='submit') {
weaverii_sapi_submit('', "
\n";
weaverii_adv_hidden_opt($area_name); // keep it working for Pro settings, even on free version
weaverii_adv_hidden_opt($hide_front);
weaverii_adv_hidden_opt($hide_rest);
if ($info)
echo '';
return;
}
?>
class .$style_id.)");
else
echo (" (Style with #$style_id.)");
?>
'; weaverii_form_row_ctext($val); echo '';
?>
If you check this box, then the code from this area will not be displayed on the front (home) page.
If you check this box, then the code from this area will not be displayed on non-front pages.
If you check this box, then the code from this area will be inserted before the footer widgets instead of after.
Custom Page Templates
Weaver II includes several page templates - which is the WordPress tool for giving different look and functionality
do individual static pages. Many of the properties of any given page, independent of the page template, can be
set using the "Weaver II Options For This Page" box on the regular WordPress Page Editor admin page.
One of the most requested features included in the Per Page box is the ability to set the sidebar layout for
each page. If this is not set, the page will use the global options for the page type. The other popular option
includes the ability to replace any of the sidebar widget areas, as well as the ability to add an additional top
widget area. To use a new widget area you must first tell Weaver II to create a new one. These
Per Page Widget Areas are defined on the Main Options:Widget Areas tab.
Overview of Page Templates
The 2 Col Content template splits content into two columns. You manually set the column
split using the standard WP '<--more-->' convention. (Note - since WordPress only used the '<--more-->' to
show the "Continue reading..." for posts, it can serve this purpose for this template on pages. Columns will split first
horizontally, then vertically (you can have more than one <--more--> tag).
The Blank page template will wrap the content of an associated page with an HTML div with class
.content-blank which you can add CSS rules to style using the standard Weaver II options.
The standard page <article> wrapping is not used. The page title is not displayed. Use Per Page Options
on Page edit menu to control Menu, Site Title, and Header Image visibility.
Page with Posts serves as an alternative way to display posts. After you select the Page with Posts
template, a new set of options will be added to the Per Page menu. There is additional help in the help documentation.
The Raw template allows total custom HTML styling with no predefined div's. It useful for Pop Up pages.
The Sitemap provides a page with a basic sitemap.
The iframe template is designed for full width display of html iframes. You can control sidebars
and titles using standard Per Page options.
The HTML Source template will display the page content as syntax-highlighted HTML or PHP code.
It is useful for showing source code. Any text (e.g., an explanation) defined in per page Custom Field called 'html_source_intro' will
be displayed before the content source code.
'Archive Type Pages', 'type' => '=header0',
'info'=> 'Extra options for Archive-like pages - Categories, Tags, etc.',
'help' => 'help.html#ArchivePages'),
array('name' => 'Hide Categories Archives Title', 'id' => 'wii_hide_p_category', 'type' => '+checkbox',
'info' => 'Hide "Category Archives" title on category pages. (●Pro)'),
array('name' => 'Custom CSS', 'id' => 'wii_p_category_css', 'type' => '+textarea',
'info' => 'Custom CSS to add to Category Archive page. (●Pro)'),
array('name' => 'Hide Tag Archives Title', 'id' => 'wii_hide_p_tag', 'type' => '+checkbox',
'info' => 'Hide "Tag Archives" title on category pages. (●Pro)'),
array('name' => 'Custom CSS', 'id' => 'wii_p_tag_css', 'type' => '+textarea',
'info' => 'Custom CSS to add to Tag Archive page. (●Pro)'),
array('name' => 'Hide Author Archives Title', 'id' => 'wii_hide_p_author', 'type' => '+checkbox',
'info' => 'Hide "Author Archives" title on author pages. (●Pro)'),
array('name' => 'Custom CSS', 'id' => 'wii_p_author_css', 'type' => '+textarea',
'info' => 'Custom CSS to add to Author Archive page. (●Pro)'),
array('name' => 'Hide Date Archives Title', 'id' => 'wii_hide_p_date', 'type' => '+checkbox',
'info' => 'Hide "Date Archives" title on date archive pages. (●Pro)'),
array('name' => 'Custom CSS', 'id' => 'wii_p_date_css', 'type' => '+textarea',
'info' => 'Custom CSS to add to Date Archive page. (●Pro)'),
array('name' => 'Hide Search Results Title', 'id' => 'wii_hide_p_search', 'type' => '+checkbox',
'info' => 'Hide "Search Results" title on search pages. (●Pro)'),
array('name' => 'Custom CSS', 'id' => 'wii_p_search_css', 'type' => '+textarea',
'info' => 'Custom CSS to add to Search Archive page. (●Pro)'),
);
weaverii_form_show_options($opts);
weaverii_hide_advanced('end');
}
// ============================================== SITE OPTIONS ===========================================
function weaverii_adv_site_opts() {
?>
Site Options
These options are available to fine tune various aspects of your site. Technically, these features
are not part of the theme styling, but cover other aspects of site functionality. NOTE:
The FavIcon and Preferred Image for Facebook options will be displayed only for
Weaver II Pro or if you have the "Weaver II Theme Extras" plugin installed.
Home Page
WordPress allows you to specify what page is used for your home page - either the standard WordPress blog,
or a static page (which can be a Weaver "Page with Posts" page). How to set the Front page displays options
is not totally obvious - please see the Weaver Help topic for a more complete explanation.
For the best look, your site should support Avatars - a small image associated with
a contributors e-mail address. '); ?>Gravatar.com
is probably the most popular Avatar support, and is closely associated with WordPress. You should set up a Gravatar for
the main authors of your blog. For contributors without any avatar, you can select an automatically
generated avatar from several options found on the
Settings→Discussion panel.
'#070Mobile Support Mode', 'id' => '_wii_mode_mobile', 'type' => 'select_id',
'info' => 'Select how Weaver II generates mobile views. (Default: Smart, hide sidebars) Important: see the help file!. ♦',
'value' => array(
array('val' => 'weaver-mobile-smart-nostack', 'desc' => 'Smart, hide sidebars'),
array('val' => 'weaver-mobile-smart-stacked', 'desc'=> 'Smart, stacked sidebars' ),
array('val' => 'weaver-mobile-resp-nostack', 'desc' => 'Responsive, hide sidebars'),
array('val' => 'weaver-mobile-responsive', 'desc' => 'Responsive, stacked sidebars')
)),
array('name' => '#070Disable Mobile Support', 'id' => '_wii_mobile_disable', 'type' => '=checkbox',
'info' => 'Disable support for mobile devices. Your site will shrink the sizes of the sidebars and content
areas, but will otherwise not be responsive or stack sidebars. ♦'),
array('name' => 'Alternative Mobile Plugins:','type'=> '=note',
'info' => 'If you need to use an alternative Mobile Theme plugin, you must set one of the
responsive Mobile Support Modes above, in which case your site will continue to display responsively on desktop browsers and unrecognized mobile devices, while using the alternative plugin for recognized mobile devices.
You can also Disable Mobile Support, in which case you will not get fully responsive desktop support.'),
array('name' =>'Mobile Simulator Options','type'=>'subheader',
'info' => 'Settings for the Mobile simulator. Available only when using "Smart" Mobile Modes.'),
array('name' => '#070Simulate Mobile Device', 'id' => '_wii_sim_mobile', 'type' => 'select_id',
'info' => 'Simulate Mobile Device (◘Smart Modes Only): Select type to see what your site will look like on mobile devices. The simulator works only when using a "Smart" mobile support mode. Otherwise, just shrink your browser for the Responsive modes (IE7/IE8 don\'t work to shrink). ♦',
'value' => array(
array('val' => 'none', 'desc' => 'Simulation Off'),
array('val' => 'WeaverMobile', 'desc'=> 'Smart Phone' ),
array('val' => 'WeaverMobileSmallTablet', 'desc' => 'Small Tablet (Fire)'),
array('val' => 'WeaverMobileTablet', 'desc' => 'Large Tablet (iPad)')
)),
array('name' => '#070... even if not admin', 'id' => '_wii_sim_mobile_always', 'type' => '=checkbox',
'info' => 'Normally, the mobile simulation will be displayed only for admins. Checking this allows visitors to view the simulated mobile view. IMPORTANT! Be careful using this option - it is intended for development and demos only and normally should be disabled for productions sites. ♦'),
array('name' =>'Small Screen Devices','type'=>'=subheader',
'info' => 'Settings for smartphones, other small screen devices, and small tablets.'),
array('name' => '#070Show Full Blog Posts', 'id' => 'wii_mobile_full_posts', 'type' => '+checkbox',
'info' => 'Show full post text on blog pages - posts are excerpted by default on mobile devices (◘Smart Modes only). (●Pro)'),
array('name' => '#070Show Footer Widgets', 'id' => 'wii_mobile_show_footerwidgets', 'type' => '+checkbox',
'info' => 'Will show footer widget area on non-stacked Mobile Modes for mobile devices. (Footer widget is always displayed on stacked Mobile Modes.) (●Pro)'),
array('name' => '#070Hide Top/Bottom Widget Areas', 'id' => 'wii_mobile_hide_topbottom_widgets', 'type' => '+checkbox',
'info' => 'Hide Top and Bottom Widget Areas in addition to Sidebars. (●Pro)'),
array('name' => '#070No Auto-Underline Links', 'id' => 'wii_mobile_nounderline', 'type' => '+checkbox',
'info' => 'Underlined links are easier to use on most mobile devices. This will disable auto-underlined links. (●Pro)'),
array('name' => '#070View Toggle', 'id' => 'wii_layout_view_toggle', 'type' => '+select_id',
'info' => 'How to display the Full View/Mobile View toggle button on mobile devices (◘Smart Modes only). (●Pro)',
'value' => array(
array('val' => 'both', 'desc' => 'Both top & bottom'),
array('val' => 'top', 'desc'=> 'Top only' ),
array('val' => 'bottom', 'desc' => 'Bottom only'),
array('val' => 'hide', 'desc' => 'Hide view toggle')
)),
array('name' => '#070Alternate Full View HTML', 'id' => '_wvr_mobile_fullmsg', 'type' => '+textarea',
'info' => 'HTML to replace standard Full View icon (include style if needed). (●Pro) ♦'),
array('name' => '#070Alternate Mobile View HTML', 'id' => '_wvr_mobile_mobilemsg', 'type' => '+textarea',
'info' => 'HTML to replace standard Mobile View icon. (●Pro) ♦'),
array('name' => '#070Mobile Home Page', 'id' => 'wii_mobile_home_int', 'type' => '+text',
'info' => 'Specify page ID for alternate Home page when site viewed from mobile device (◘Smart Modes only). Recommended: check "Hide Page on the default Primary Menu" Per Page option for the page. (●Pro)'),
array('name' => '#070Mobile Site Title', 'id' => '_wii_mobile_site_title', 'type' => '+textarea',
'info' => 'Specify alternate Site Title if needed (◘Smart Modes only) (Use to hide Site Title on mobile). (●Pro) ♦'),
array('name' => '#070Mobile Site Title Color', 'id' => 'wii_mobile_title_color', 'type' => '+color',
'info' => 'Alternate Color for Mobile Site Title (includes Responsive Modes). (●Pro)'),
array('name' => '#070Mobile Header Image', 'id' => '_wii_mobile_header_url', 'type' => '+textmedia',
'info' => 'Specify alternate header image for phone/small tablet mobile view (◘Smart Modes only). (●Pro) ♦'),
array('name' => '#070Mobile Header Image - Tablet', 'id' => '_wii_mobile_tablet_header_url', 'type' => '+textmedia',
'info' => 'Specify alternate header image for tablet mobile view (will usually not be necessary, ◘Smart Modes only). (●Pro) ♦'),
array('name' => '#070Custom CSS', 'id' => '_wii_mobile_css', 'type' => '+textarea',
'info' => 'Custom site wide CSS included only when viewed on Mobile Device. Note that ".weaver-mobile" wrapping class can also be used for this purpose in the <HEAD> Section Custom CSS option (◘Smart Modes only). (●Pro) ♦'),
array('name'=>'More Mobile Options:','type'=>'note',
'info'=>'More mobile options are available for specific areas: Header, Menus, Post Specifics, Shortcodes.'),
array( 'type' => 'submit'),
array('name' =>'Tablets','type'=>'=subheader',
'info' => 'Settings for iPad and other tablets'),
array('name' => '#070Keep Site Margins', 'id' => 'wii_mobile_keep_site_margins', 'type'=>'+checkbox',
'info' => 'Retain standard site margins on tablets (◘Smart Modes only) - will normally reduce outer margins by default. (●Pro)'),
array('name' => '#070No Auto-Underline Links', 'id' => 'wii_mobile_tablet_nounderline', 'type' => '+checkbox',
'info' => 'Underlined links are easier to use on most tablet devices. This will disable auto-underlined links. (◘Smart Modes only - Responsive Modes never auto-underline links on tablets.) (●Pro)'),
array('name' =>'Alternate Mobile Theme','type'=>'=subheader',
'info' => 'Use Alternate Mobile Theme when site viewed by Mobile Device.'),
array('name' => '#070Use Alternate Mobile Theme', 'id' => '_wii_mobile_alt_theme', 'type' => '+checkbox',
'info' => 'Mobile Devices will use the Mobile Theme Settings saved in the "Save Settings to Mobile Settings"
option on the "Save/Restore" tab (◘Smart Modes only). (The Alternate Mobile Theme can not be displayed with the Mobile Simulator.) (●Pro) ♦')
);
?>
Mobile Device Options
These are the main options that control how Weaver II displays your site on Mobile devices. Please note that there are
other options that affect the mobile view located on other tabs (e.g., the Main Options : Header tab). Options that affect
the mobile view are displayed with a Green Label.
Warning: No Mobile Theme Settings have been saved. You must use the "Save Settings to Mobile Settings" from the Save/Restore tab first! ';
}
}
?>
Apple Touch Icon for iOS
When this site is viewed on an Apple iOS device such as an iPhone or iPad (◘Smart Modes only), Apple iOS recognizes a special icon
that can be displayed on the device's home screen. The recommend size for this icon is a .png file 57x57 px for basic display,
or 114x114 px for enhanced display. ♦
';
}
?>
Apple Touch Icon URL:
Full path to Apple Touch Icon
Caching Plugins for Weaver II
Because of the advanced Smart Mobile View capabilities provided by Weaver II, many existing WordPress Caching plugins
will not work correctly with Weaver II when it is displayed in Smart Mobile Device mode.
(Using one of the Responsive mobile display modes will allow Weaver II to work correctly with any cache plugin.)
For using the ◘Smart Modes mobile support, we have found that the Quick Cache and
W3 Total Cache plugins do work with Weaver Smart Mobile mode when
properly configured. Please see the Weaver II help file for instructions on
using compatible cache plugin →.
SEO
Weaver II has been designed to follow the latest SEO (Search Engine Optimization) guidelines.
Each non-home page will use the recommended "Page Title | Site Title" format, and the site is formatted
using the appropriate HTML5 tags for optimal SEO performance.
If you want optimal SEO for your site, we recommend using an SEO plugin such as
WordPress SEO by Yoast.
SEO/Meta Tags (legacy support)
Previous versions of Weaver II supported two <meta> tags: "description" and "keywords". This is no
longer supported. If you want these values in your site, you can use the Advanced Options : <HEAD>
Section option to add them.
You have a value for this meta information saved in your settings - probably from a previous
version of Weaver II. If you had set these to something other than the default, you might want
to copy/paste these into the Advanced Options : <HEAD> Section option. Otherwise,
you should consider using an SEO plugin.