Weaving 3 Ways
avatar

Weaving 3 Ways

Theme Settings Converter

Convert theme settings between Weaver II and Aspen, or either of those to Weaver Xtreme. The settings will be saved in a file on your computer which you can then upload to the other theme.

Features

admin screenshot Weaving 3 Ways

admin screenshot Weaving 3 Ways

Any of these theme settings:
  • current settings,
  • alternate mobile settings,
  • backup settings,
  • theme switcher settings

can be saved to a file or converted to one of the other themes.
All settings that can be converted, are.
The style version number is used in the output file name.
The plugin has Spanish and French translations.
Conversion is fast and easy.
Most of the subthemes for sale here convert without needing any adjustment.

Details

  • Built with: Weaver II 2.0, Aspen 1.0.5
  • Release Date: Oct 2013
  • Last Updated: Nov 2014
  • Dependencies: Aspen 1.0.6+ or Weaver II 2.1+ or Weaver Xtreme 0.90.3+
Try out the demo!

This converts only the options available from the theme admin page. It does not do anything with header images, widgets, settings from the Appearance: Background page, or any Per Page Options or Per Post Options.

The differences in the base style sheets are reconciled with CSS that is put in the CSS+ box for the default link color since that is the first thing that the themes output for the generated CSS.

If you use the Weaver II option for an alternate style sheet, it will come out after the other styles, which would be different than in Weaver II, and there is no way to turn off the base style sheet for the theme in Aspen or Weaver Xtreme.

You will need to check how the CSS renders, and make some tweaks to the converted theme settings.

With Weaver Xtreme, most of the options generate styling with CSS classes, which makes the conversion more and less exact at the same time. A lot of settings are converted to styles which override the class definitions. To use the Weaver Xtreme class definitions, remove the extra styles added by the conversion (in the color option CSS+ boxes). Weaver Xtreme does not have the mobile widget area or the mobile menu location that both Weaver II and Aspen have. Also, the Weaver II Per Page Widgets list is a theme setting, but in Weaver Xtreme it is a site setting, meaning it will not be saved in a wxt file. The Aspen Pro and Weaver II header widget area settings are site settings, but in Weaver Xtreme they are theme settings (except for the custom widget widths). Be sure to review your custom CSS for correct hierarchy of names, especially for names that are no longer used, such as sidebar_wrap, container_wrap, entry-header and entry-hdr, and parts of the menus. Also, if you have mobile rules in CSS+ boxes, check them to be sure they did not get reformatted incorrectly.

Aspects that are not converted

Most of the options that are not converted are due to the inability to affect the workings of the theme. The options influence the theme, but are not code. So most of these are about HTML differences and mobile functionality. The Weaver Xtreme footer widgets work differently than in Aspen or Weaver II. You will need to adjust the number of columns desired for the footer widgets.

Weaver II to Aspen

"standard border" style, search message, Go button, search button URL, hide not found search, sidebar flow color to bottom, per page widgets, mobile move title over header, header image width, header layout, iPad show header image, hide mobile Featured Image, alternate header image, disable header clipping, top menu before wrapper, menu bar separators, menu item width, menu add HTML on left, Infobar HTML, hide tooltips, Featured Image above page title, fitvids javascript, comment reply message, comments on Page with Posts page, no post title link, post meta move top, post meta move bottom, mobile hide post meta, always show featured image for blog, Featured Image above post titles, disable mobile support, mobile simulator, show full posts on mobile, mobile Full toggle, mobile site title, mobile header URL, mobile CSS, mobile keep site margins, no underline on tablets, alternate mobile theme, CSS output only on specific archive pages, no final div
With the exception of Total CSS settings, Weaver II Pro options that are accessed from the Weaver II Pro/Shortcodes page are not converted.

Aspen to Weaver II

extra header logo, header widget area shortcode, mobile header insert, desktop header insert, Per Post Options for Custom Post Types

Weaver II to Weaver Xtreme

search message, Go button, search button URL, hide not found search, fixed theme width, specialized container wrapper properties, sidebar wrapper properties, left sidebar properties, sidebar widget area L/R margins, mobile move title over header, header HTML over header, header image width, iPad show header image, Featured Image in header based on size, hide mobile Featured Image, alternate header image, header widget area height, header widget area on front page only, disable header clipping, wide header, mobile slide menu properties, top menu before wrapper or header, menu spacing, menu bar separator properties, menu item width, Infobar location, breadcrumb blog label, Infobar HTML, fitvids javascript, comment reply message, comments on Page with Posts page, no post title link, post meta move top and bottom, hide final div, wide footer, disable mobile support, mobile simulator, show full posts on mobile, mobile Full toggle, mobile site title, mobile header URL, mobile CSS, mobile keep site margins, no underline on mobile, alternate mobile theme, header HTML insertion on front page only (and non- front), footer HTML insertion on front page only (and non-front), pre left sidebar insert, CSS output only on specific archive pages, no final div
With the exception of Total CSS settings, Weaver II Pro options that are accessed from the Weaver II Pro/Shortcodes page are not converted.

Aspen to Weaver Xtreme

fixed theme width, specialized container wrapper properties, sidebar wrapper properties, left sidebar properties, sidebar widget area L/R margins, header HTML over header, header widget area height, header widget area on front page only, header widget area shortcode, wide header, mobile slide menu properties, top menu before header, Infobar location, breadcrumb blog label, hide final div, wide footer, no underline on mobile, header HTML insertion on front page only (and non-front), footer HTML insertion on front page only (and non-front), pre left sidebar insert

Frequently Asked Questions

What is the difference between All Options and Theme Options?

In Aspen, Weaver II, and Weaver Xtreme there are some settings that are site-specific. When saving your settings to a file, you have the choice of saving All of the options (called a backup), or just the Theme options. The site-specific options are marked with a black diamond in the theme admin page.
Be aware that Per Page Widgets are not site-specific in Weaver II, but are in Weaver Xtreme. That means a w2t file will have them, but they would not be in the converted wxt file. Header widget area settings are site-specific in Aspen Pro and Weaver II (they will only be in the abu and w2b files), but are theme settings in Weaver Xtreme (saved in wxt file). The custom post info lines for Aspen Pro and Weaver II Pro are site-specific (only saved in abu and w2b files), but are theme settings in Weaver Xtreme (saved in wxt files).

Are the Pro options converted?

Many of the Pro options have an equivalent option in the new theme's Pro version. Those options are converted. Other Pro options have no equivalent, so they are not carried forward to the converted file.
With the exception of Total CSS settings, Weaver II Pro options that are accessed from the Weaver II Pro/Shortcodes page are not converted.

Why does my design behave differently on mobile devices? Where are my mobile options?

There are quite a few options in Aspen, Weaver II, and Weaver Xtreme that affect whether the theme outputs some HTML or CSS in different situations. These options are converted as much as possible from the limitations of the subtheme settings file. The theme you use will dictate what is done with the settings in the file. Pro versions can add PHP code in the Actions & Filters area, but the themes do not have filters in the right places to make it work.

When I try to change my design in the new theme, it doesn't change. Why?

The conversion adds CSS to make the design match how it looked in the old theme.
To make changes once converted, you may need to remove some of that CSS. For Weaver II and Aspen, look in the Standard Link Color CSS+ box. For Weaver Xtreme, look in the BG color CSS+ box for that "area" or in the Standard Link Color CSS+ box.
The Weaver II Pro Total CSS is converted to the Custom CSS box.

I have some old Pro options mixed with my current Weaver II options. Why?

If you have switched back and forth between Weaver II and Weaver II Pro, it is possible that you have a mismatch in the options because Weaver II basic does not save Weaver II Pro options. This most affects Total CSS and Fonts options. Clear out the Pro options before conversion, or save settings to a file and then convert the file.

Change Log

= 0.85 =

Release Date: Nov 10, 2014

  • improved security
  • amended to integrate with functions for a demo version

= 0.8 =

Release Date: Nov 7, 2014

  • completed the Weaver Xtreme conversion code (many, many, many changes)
  • changed the name of the plugin
  • added buttons to save to file with no conversion
  • added language support, and Spanish and French translations
  • fixed some option names that use dashes

= 0.7 =

Release Date: Aug 31, 2014

  • fixed the HTML Insertion Areas BG color names
  • added a rough conversion to Weaver Xtreme

= 0.6 =

Release Date: July 16, 2014

  • fixed some Pro settings that were being removed
  • changed the nonce names

= 0.5 =

Release Date: Oct 10, 2013

  • added a call to apply_filters in atw_convert_get_options_to_convert()
  • added a default value for wii_subtheme so converted Aspen settings won't revert to Antique Ivory

= 0.4 =

Release Date: Aug 23, 2013

  • first distribution for testing