This plugin hasn’t been tested with the latest 3 major releases of WordPress. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.

Child Theme Configurator


Child Theme Configurator is a fast and easy to use utility that allows you to analyze any theme for common problems, create a child theme and customize it beyond the options of the Customizer. Designed for WordPress users who want to be able to customize child theme stylesheets directly, Child Theme Configurator lets you easily identify and override the exact CSS attributes you want to customize. The Analyzer scans the rendered theme and automatically configures your child theme. It correctly enqueues theme and font stylesheets for optimum performance and handles vendor-specific syntax, giving you unlimited control over the Child Theme look and feel while leaving your Parent Theme untouched. Learn more about how to create a child theme.

Take Control of Your Child Themes

Child Theme Configurator parses and indexes your stylesheets so that every CSS media query, selector, property and value are at your fingertips. Second, it shows you how each customization you make will look before you commit it to the child theme. Finally, it saves your work so that you can customize styles in your child themes without the risk of losing your edits.

You can create any number of child themes from your existing Parent Themes. Child Theme Configurator lets you choose from your installed themes (even existing child themes) and save the results in your Themes directory.

When you are ready, just activate the Child Theme and your WordPress site takes on the custom styles automatically.

Why create child themes and customize styles using Child Theme Configurator?

  1. Some things cannot be changed using the Customizer.

  2. Unless you use a child theme, you will lose any changes you made to templates and stylesheets when you update.

  3. Child Theme Configurator automatically determines the correct way to set up a child theme based on the theme you are using.

  4. You can find the exact style selectors your theme uses and change properties quickly.

  5. You can locate, copy and edit theme templates from the admin.

  6. Much more:

    • Update themes without losing customizations
    • Smart Theme Analyzer determines correct settings to use
    • Resolve common child theme issues with almost any parent theme
    • Copy existing widgets, menus and Customizer options to child theme
    • Use web fonts in your child theme
    • Enqueue (link) stylesheets instead of using @import
    • Quickly locate and edit theme CSS.
    • Customize @media queries for responsive design
    • Select hex, RGBA (transparent) and named colors using Spectrum color picker
    • Add fallback styles (multiple values per property)
    • Save hours of development time
    • Multisite compatible
    • Make modifications unavailable to the Customizer
    • Export child themes as Zip Archive
    • Identify and override exact selectors from the parent theme
    • Change specific colors, backgrounds, font styles, etc., without changing other elements
    • Automatically generate cross-browser and vendor-prefixed properties and CSS gradients
    • Preview custom styles before committing to them
    • Uses WP Filesystem API – will not create files you cannot remove

Child Theme Configurator PRO

Apply the CSS customizing power of Child Theme Configurator to any WordPress Plugin installed on your website. Child Theme Configurator PRO scans your plugins and lets you customize their stylesheets. We’ve added more features to make customizing styles quicker and easier with PRO.

Learn more at

Unlimited Widget Content With a Single Plugin

IntelliWidget is a versatile widget manager that does the work of multiple plugins by combining custom page menus, featured posts, sliders and other dynamic content features that can display on a per-page or site-wide basis.

Learn more at

Hook Highlighter

Hook Highlighter provides Administrators insight into the internal program flow of WordPress when activated on any front-facing page of a website.

Display action and filter hooks, program files and backtrace information inline for the current page.

Learn more at

Query/Selector Tab

There are two ways to identify and customize baseline (parent) styles. Child Theme Configurator lets you search styles by CSS selector and by property. If you wish to customize a specific CSS selector (e.g., h1), use the “Query/Selector” tab. If you have a specific CSS value you wish to customize site-wide (e.g., the color of the type), use the “Property/Value” tab.

The Query/Selector tab lets you find specific CSS selectors and edit them. First, find the query that contains the CSS selector you wish to edit by typing in the Query autoselect box. Select by clicking with the mouse or by pressing the “Enter” or “Tab” keys. CSS selectors are in the base query by default.
Next, find the CSS selector by typing in the “Selector” autoselect box. Select by clicking with the mouse or by pressing the “Enter” or “Tab” keys.

This will load all of the properties for that CSS selector with the Original values on the left and the child theme values inputs on the right. Any existing child theme values will be automatically populated. There is also a Sample preview that displays the combination of Parent and Child overrides. Note that the border and background-image get special treatment.

The “Order” field contains the original sequence of the CSS selector in the parent theme stylesheet. You can change the CSS selector order sequence by entering a lower or higher number in the “Order” field. You can also force style overrides (so called “!important” flag) by checking the “!” box next to each input. Please use judiciously.

Click “Save” to update the child theme stylesheet and save your changes to the WordPress admin.

Adding Raw CSS

If you wish to add additional properties to a given CSS selector, first load the selector using the Query/Selector tab. Then find the property you wish to override by typing in the New Property autoselect box. Select by clicking with the mouse or by pressing the “Enter” or “Tab” keys. This will add a new input row to the selector inputs.

If you wish to add completely new CSS selectors, or even new @media queries, you can enter free-form CSS in the “Raw CSS” textarea. Be aware that your syntax must be correct (i.e., balanced curly braces, etc.) for the parser to load the new custom styles. You will know it is invalid because a red “X” will appear next to the save button.

If you prefer to use shorthand syntax for properties and values instead of the inputs provided by Child Theme Configurator, you can enter them here as well. The parser will convert your input into normalized CSS code automatically.

Property/Value Tab

The Property/Value tab lets you find specific values for a given property and then edit that value for individual CSS selectors that use that property/value combination. First, find the property you wish to override by typing in the Property autoselect box. Select by clicking with the mouse or by pressing the “Enter” or “Tab” keys.

This will load all of the unique values that exist for that property in the parent theme stylesheet with a Sample preview for that value. If there are values that exist in the child theme stylesheet that do not exist in the parent stylesheet, they will be displayed as well.

For each unique value, click the “Selectors” link to view a list of CSS selectors that use that property/value combination, grouped by query with a Sample preview of the value and inputs for the child theme value. Any existing child theme values will be automatically populated.

Click “Save” to update the child theme stylesheet and save your changes to the WordPress admin.

If you want to edit all of the properties for the CSS selector you can click the “Edit” link and the CSS selector will automatically load in the Query/Selector Tab.

Web Fonts Tab

You can add additional stylesheets and web fonts by typing @import rules into the textarea on the Web Fonts tab. Important: do not import the parent theme stylesheet here. Use the “Parent stylesheet handling” option from the Parent/Child tab.

Files Tab

Parent Templates

You can copy PHP template files from the parent theme by checking the boxes. Click “Copy Selected to Child Theme” and the templates will be added to the child theme’s directory.

CAUTION: If your child theme is active, the child theme’s version of the file will be used instead of the parent immediately after it is copied. The functions.php file is generated separately and cannot be copied here.

Child Theme Files

Templates copied from the parent are listed here. These can be edited using the Theme Editor in the Appearance Menu. Remove child theme images by checking the boxes and clicking “Delete Selected.”

Child Theme Images

Theme images reside under the images directory in your child theme and are meant for stylesheet use only. Use the media gallery for content images. You can upload new images using the image upload form.

Child Theme Screenshot

You can upload a custom screenshot for the child theme here. The theme screenshot should be a 4:3 ratio (eg., 880px x 660px) JPG, PNG or GIF. It will be renamed “screenshot”.

Export Child Theme as Zip Archive

You can download your child theme for use on another WordPress site by clicking “Export”.

Preview and Activate

IMPORTANT: Test child themes before activating!

Some themes (particularly commercial themes) do not correctly load parent template files or automatically load child theme stylesheets or php files.

In the worst cases they will break your website when you activate the child theme.

  1. Navigate to Appearance > Themes in the WordPress Admin. You will now see the new Child Theme as one of the installed Themes.
  2. Click “Live Preview” (theme customizer) below the new Child Theme to see it in action.
  3. When you are ready to take the Child Theme live, click “Activate.”

MULTISITE USERS: You must Network Enable your child theme before you can use Live Preview. Go to “Themes” in the Network Admin.


  • Arbitrary comments are not supported. Providing a high level of flexibility for previewing and modifying custom styles requires a sophisticated parsing system. Maintaining comments that are bound to any particular element in the stylesheet is prohibitively expensive compared to the value it would add. Although we are working to include this as an option in the future, currently all comments are stripped from the child theme stylesheet code.
  • No @keyframes or @font-face rules. Child Theme Configurator only supports @media and @import. If you need other @rules, put them in a separate stylesheet and import them into the Child Theme stylesheet.
  • Only two-color gradients. Child Theme Configurator is powerful, but we have simplified the gradient interface. You can use any gradient you want as long as it has two colors and no intermediate stops.
  • CSS properties are auto-discovered. Child Theme Configurator loads the properties that exist in the Parent stylesheet. You can always add new properties using the “Raw CSS” text area.
  • Legacy gradient syntax is not supported. Child Theme Configurator does not support the MS filter gradient or legacy webkit gradient. These will continue to work if they are used in the parent theme, but will not be written to the child theme stylesheet. If there is a demand, we may add it in a future release, but most users should have upgraded by now.


Go to

Serbo-Croatian translation courtesy of Borisa Djuraskovic

Copyright: (C) 2014-2018 Lilaea Media


  • Parent/Child tab
  • Parent/Child tab with parent theme menu open
  • Query/Selector tab
  • Property/Value tab
  • Web Fonts tab
  • Parent CSS tab
  • Files tab


  1. To install from the Plugins repository:

    • In the WordPress Admin, go to “Plugins > Add New.”
    • Type “child theme” in the “Search” box and click “Search Plugins.”
    • Locate “Child Theme Configurator” in the list and click “Install Now.”
  2. To install manually:

    • Download the Child Theme Configurator from
    • In the WordPress Admin, go to “Plugins > Add New.”
    • Click the “Upload” link at the top of the page.
    • Browse for the zip file, select and click “Install.”
  3. In the WordPress Admin, go to “Plugins > Installed Plugins.” Locate “Child Theme Configurator” in the list and click “Activate.”

  4. Navigate to Tools > Child Themes (multisite users go to Network Admin > Themes > Child Themes).

The Parent/Child Tab: 10 Easy Steps to Create a Child Theme

  1. Select an action:

    • CREATE a new Child Theme – Install a new customizable child theme using an installed theme as a parent.
    • CONFIGURE an existing Child Theme – Set up a previously installed child theme for use with the Configurator or to modify current settings.
    • DUPLICATE an existing Child Theme – Make a complete copy of an existing Child Theme in a new directory, including any menus, widgets and other Customizer settings. The option to copy the Parent Theme settings (step 8, below) is disabled with this action.
    • RESET an existing Child Theme (this will destroy any work you have done in the Configurator) – Revert the Child theme stylesheet and functions files to their state before the initial configuration or last reset.
  2. Select a Parent Theme if creating a new Child Theme; select a Child Theme if configuring, duplicating or resetting.

  3. Analyze Child Theme – Click “Analyze” to determine stylesheet dependencies and other potential issues.

  4. If creating a new Child Theme, name the new theme directory; otherwise verify it the directory is correct. – This is NOT the name of the Child Theme. You can customize the name, description, etc. in step 7, below.

  5. Select where to save new styles:

    • Primary Stylesheet (style.css) – Save new custom styles directly to the Child Theme primary stylesheet, replacing the existing values. The primary stylesheet will load in the order set by the theme.
    • Separate Stylesheet – Save new custom styles to a separate stylesheet and use any existing child theme styles as a baseline. Select this option if you want to preserve the original child theme styles instead of overwriting them. This option also allows you to customize stylesheets that load after the primary stylesheet.
  6. Select Parent Theme stylesheet handling:

    • Use the WordPress style queue. – Let the Configurator determine the appropriate actions and dependencies and update the functions file automatically.
    • Use @import in the child theme stylesheet. – Only use this option if the parent stylesheet cannot be loaded using the WordPress style queue. Using @import is not recommended.
    • Do not add any parent stylesheet handling. – Select this option if this theme already handles the parent theme stylesheet or if the parent theme’s style.css file is not used for its appearance.
  7. Customize the Child Theme Name, Description, Author, Version, etc.: (Click to toggle form)

  8. Copy Parent Theme Menus, Widgets and other Customizer Settings to Child Theme: – NOTE: This will overwrite any child theme options you may have already set.

  9. Click the button to run the Configurator.

  10. IMPORTANT: Always test child themes with Live Preview (theme customizer) before activating!


How do I move changes I have already made to my theme into a Child Theme?

Follow these steps:

When I run the analyzer I get “Constants Already Defined” notice in PHP Debug Output

This is a misconfiguration created by the Bluehost auto-installer.” class=”scroll-to”>How to fix.

Is there a tutorial?

There are videos under the “Help” tab at the top right of the page. You can also view them at

If the parent theme changes (e.g., upgrade), do I have to update the child theme?

No. This is the point of using child themes. Changes to the parent theme are automatically inherited by the child theme.

A child theme is not a “copy” of the parent theme. It is a special feature of WordPress that let’s you override specific styles and functions leaving the rest of the theme intact. Quality themes should identify any deprecated functions or styles in the upgrade notes so that child theme users can make adjustments accordingly.

If I uninstall Child Theme Configurator are child themes affected?

No. Child Theme Configurator is designed to work independently of themes and plugins. Just remember that if you re-install, you must rebuild the configuration data using the Parent/Child tab.

How do I add comments?

Arbitrary comments are not supported. Providing a high level of flexibility for previewing and modifying custom styles requires sophisticated parsing and data structures. Maintaining comments that are bound to any particular element in the stylesheet is prohibitively expensive compared to the value it would add. Although we are working to include this as an option in the future, currently all comments are stripped from the child theme stylesheet code.

Does it work with Multisite?

Yes. Go to “Network Admin > Themes > Child Themes.” Child themes must be “Network enabled” to preview and activate for Network sites.

Does it work with plugins?

Child Theme Configurator PRO brings the CSS editing power of Child Theme Configurator to any WordPress Plugin installed on your website by scanning your plugins and creating custom CSS in your Child Themes. Learn more at

Why doesn’t this work with my [insert vendor here] theme?

Some themes (particularly commercial themes) do not correctly load parent template files or automatically load child theme stylesheets or php files.

This is unfortunate, because in the best case they effectively prohibit the webmaster from adding any customizations (other than those made through the admin theme options) that will survive past an upgrade. In the worst case they will break your website when you activate the child theme.

Contact the vendor directly to ask for this core functionality. It is our opinion that ALL themes (especially commercial ones) must pass the Theme Unit Tests outlined by and ALWAYS TEST CHILD THEMES BEFORE ACTIVATING (See “Preview and Activate”).

Will this slow down my site?

Child Theme Configurator is designed to add the minimum amount of additional overhead possible and can actually improve performance. For example:

  • Child Theme Configurator creates or updates files that are already being read by the system. On the front-end, there are no database calls so WordPress can run independent of the plugin. In fact, you can remove Child Theme Configurator when you are finished setting up your child themes.
  • Custom styles are applied to a stylesheet file that can be cached by the browser and/or cached and minimized by a performance caching plugin. Because the editor creates mostly “overrides” to existing styles, the file is typically smaller than other stylesheets.
  • The code that drives the editor interface only loads when the tool is being used from the WordPress Admin, including Javascript and CSS. This means that it will not get in the way of other admin pages.
  • The biggest performance hit occurs when you generate the Child Theme files from the Parent/Child tab, but this is a one-time event and only occurs from the WordPress Admin.

HELP! I changed a file and now I am unable to access my website or login to wp-admin to fix it!

To back out of a broken child theme you have to manually rename the offending theme directory name (via FTP, SSH or your web host control panel file manager) so that WordPress can’t find it. WordPress will then throw an error and revert back to the default theme (currently twenty-fifteen).

The child theme is in your themes folder, usually


To prevent this in the future, always test child themes with Live Preview (theme customizer) before activating.

Why are my menus displaying incorrectly when I activate new child themes?


Why is my custom header missing when I activate new child themes?


Why does my custom background go back to the default when I activate new child themes?


Why do my theme options disappear when I activate new child themes?

These options are specific to each theme and are saved separately in the database. When you create new child themes, their options are blank.

Many of these options can be copied over to the child theme by checking “Copy Parent Theme Menus, Widgets and other Options” when you generate the child theme files on the Parent/Child tab.

If you want to set different options you can either apply them after you activate the child theme using the theme customizer, or by using the “Live Preview” under Appearance > Themes.

Every theme handles options in its own way. Most often, they will create a set of options and store them in the WordPress database. Some options are specific to the active theme (or child theme), and some are specific to the parent theme only (meaning the child theme CANNOT customize them). You will have to find out from the theme author which are which.

Where is Child Theme Configurator in the Admin?

For most users Child Theme Configurator can be found under “Tools > Child Themes.”

WordPress Multisite (Network) users go to “Network Admin > Themes > Child Themes.”

NOTE: Only users with “install_themes” capability will have access to Child Theme Configurator.

Click the “Help” tab at the top right for a quick reference.

How do I add Web Fonts?

The easiest method is to paste the @import code provided by Google, Font Squirrel or any other Web Font site into the Web Fonts tab. The fonts will then be available to use as a value of the font-family property. Be sure you understand the license for any embedded fonts.

You can also create a secondary stylesheet that contains @font-face rules and import it using the Web Fonts tab.

Why doesn’t the Parent Theme have any styles when I “View Parent CSS”?

Check the appropriate additional stylesheets under “Parse additional stylesheets” on the Parent/Child tab and load the Child Theme again. CTC tries to identify these files by fetching a page from the parent theme, but you may need to set them manually.

Where are the styles? The configurator doesn’t show anything!

All of the styles are loaded dynamically. You must start typing in the text boxes to select styles to edit.
“Base” is the query group that contains styles that are not associated with any particular “At-rule.”

Start by clicking the “Query/Selector” tab and typing “base” in the first box. You can then start typing in the second box to retrieve the style selectors to edit.

Why do the preview tabs return “Stylesheet could not be displayed”?

You have to load a child theme from the Parent/Child tab for the preview to display. This can also happen when your WP_CONTENT_URL is different than $bloginfo(‘site_url’). Ajax cannot make cross-domain requests by default. Check that your Settings > General > “WordPress Address (URL)” value is correct. (Often caused by missing “www” in the domain.)

Can I edit the Child Theme stylesheet manually offline or by using the Editor or do I have to use the Configurator?

You can make any manual customizations you wish to the stylesheet. Just make sure you import the revised stylesheet using the Parent/Child panel or the Configurator will overwrite your customizations the next time you use it. Just follow the steps as usual but select the “Use Existing Child Theme” radio button as the “Child Theme” option. The Configurator will automatically update its internal data from the new stylesheet.

Where are the child theme .php files?

Child Theme Configurator automatically adds a blank functions.php file to the child theme’s directory. You can copy parent theme template files using the Files tab. If you want to create new templates and directories you will have to create/upload them manually via FTP or SSH. Remember that a child theme will automatically inherit the parent theme’s templates unless they also exist in the child theme’s directory. Only copy templates that you intend to customize.

How do I customize a specific color/font style/background?

You can override a specific CSS value globally using the Property/Value tab. See Property/Value, above.

How do I add custom styles that aren’t in the Parent Theme?

You can add queries and selectors using the “Raw CSS” textarea on the Query/Selector tab. See Query/Selector, above.

How do I remove a style from the Parent Theme?

You shouldn’t really “remove” a style from the Parent. You can, however, set the property to “inherit,” “none,” or zero (depending on the property). This will negate the Original value. Some experimentation may be necessary.

How do I remove a style from the Child Theme?

Delete the value from the input for the property you wish to remove. Child Theme Configurator only adds overrides for properties that contain values.

How do I set the !important flag?

We always recommend relying on good cascading design over global overrides. To that end, you have ability to change the load order of child theme custom styles by entering a value in the “Order” field. And yes, you can now set properties as important by checking the “!” box next to each input. Please use judiciously.

How do I create cross-browser gradients?

Child Theme Configurator uses a standardized syntax for gradients and only supports two-color gradients without intermediate stops. The inputs consist of origin (e.g., top, left, 135deg, etc.), start color and end color. The browser-specific syntax is generated automatically when you save these values. See Caveats, below, for more information.

How do I make my Theme responsive?

The short answer is to use a responsive Parent Theme. Some common characteristics of responsive design are:

  • Avoiding fixed width and height values. Using max- and min-height values and percentages are ways to make your designs respond to the viewer’s browser size.
  • Combining floats and clears with inline and relative positions allow the elements to adjust gracefully to their container’s width.
  • Showing and hiding content with Javascript.

For more information view “Make a Theme Responsive”:


April 26, 2024
This plugin is outdated since Divi version 4.25.0 . If you use it after that it will make use of code that is too old. The effect of that is that there is no way to add/edit any elements at all. In functions.php of the child theme, you have to add this code: <?php function my_theme_enqueue_styles() { wp_enqueue_style( ‘parent-style’, get_template_directory_uri() . ‘/style.css’ ); } add_action( ‘wp_enqueue_scripts’, ‘my_theme_enqueue_styles’ ); In style.css of the child theme, you have to remove this: @import url(“../Divi/style.css”); This information came from the support team when they helped me solve my issues. You can find more info about this at: elegantthemes dot com slash blog slash divi-resources slash divi-child-theme(RIDICULOUS that they don’t allow to post links to explanations here. How else can I help?)
Maart 7, 2024
Works as it should, faced no issue and problem, using it for months! thanks 🙂
Oktober 19, 2023
Ooh yar! This plugin makes the best of the utterly weird and crazy Wordpress “child” thing with themes. Life is now so much easier.
Julie 30, 2023
I just wanted to change the title of my child theme.This extension completely messed my child theme and I had to restore my site to an earlier backup to get it back to normal.
Read all 275 reviews

Contributors & Developers

“Child Theme Configurator” is oopbron sagteware. Die volgende mense het bygedra tot die ontwikkeling van hierdie uitbreiding:


“Child Theme Configurator” has been translated into 9 locales. Thank you to the translators for their contributions.

Translate “Child Theme Configurator” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.



  • Fixed bug in DE translation module


  • Fixed deprecation notice for utf8_encode


  • Fixed deprecation notices in Packer.php and CSS.php


  • Version updates only.


  • Fixed ui-active-state selector where select menu was not being highlighted


  • Fixed some stylesheet issues


  • Updated for WP 5.6


  • WP 5.5 update removed commonL10n – causing scripts to break – replaced with CTC getxt value.


  • Removed curly brace syntax from substring argument in Packer class.


  • Fixed case where registered styles not showing in queue during analysis.


  • Fixes to stylesheet. Updates to help tabs.


  • Logic to prevent malformed style properties
  • Minor cosmetic changes


  • Preview class now evaluates stylesheet hooks as they fire instead of calling them again to prevent function exists errors.
  • Tested for PHP version 7.1
  • Modified input parser to allow multi-stop background gradients.


  • Analyzer now saves all signals on successful child theme regardless of analysis results.
  • This fixes a bug in some themes where the enqueue hooks were being rewitten incorrectly after adding web fonts.
  • Fixed a serious regression bug created by version 2.4.2.
  • Added call to customizer.php to initialize theme mods prior to analyzing child theme
  • Deferred copy_theme_mods until after child theme analysis. This allows hooks in Preview to initialize custom theme mods
  • Added mpriority (max priority) to CSS object to accommodate multiple irregular stylesheet hooks
  • Restored original (pre 2.4.1) version filter hook style_loader_src to child theme stylesheets to prevent caching
  • Strip closing php tag from functions.php to prevent premature response header
  • Fixed localization issues (thanks @alexclassroom for identifying these)
  • Modified style_loader_src hook to only add timestamp under certain conditions to prevent loading delay for most requests. (thanks @anthony750)
  • Automatically add action parent RTL stylesheet when child theme does not have one.
  • Handle case where parent theme changes queue action incorrectly points to non-existent child theme stylesheet.
  • Correctly copies customizer css to child theme.
  • Fixed PHP 7.3 compatability issue (thanks @forest-skills for identifying this)


  • strip scripts during template scan to prevent false positives
  • check file size during template scan to prevent timeout
  • changed syntax of statement that was being flagged by WP Defender
  • Fixed bug in screenshot copy.
  • Fixed incorrect reference to errors array in UI.
  • Added ability to rename @media query
  • Added height/Width for theme images on Files Tab
  • Added test for RTL in Analyzer
  • Added test cases for WP Rocket and AutOptimize plugins in Analyzer
  • Added redirect for error condition after configurator POST
  • Clarified descriptions for certain Analyzer signal conditions
  • Set priority of child theme css hook to force load after parent
  • Remove pruned selectors from menu


  • Modified preview to include all registered stylesheets in queue
  • Disable Autoptimize in preview
  • Added support for General Sibling Selector (~)
  • Fixed CSS class loading FALSE for dictionaries on fresh install
  • Fixed using wrong nonce for plugin mode preview (Pro)
  • Fixed error thrown when packing negative integers (Pro)
  • Disable Pagespeed in preview
  • Fixed Preview and Analyzer for some child theme configurations by removing nonce requirement
  • Fixed header not being repaired on first pass with “Repair Header” selected
  • Fixed styles being pruned before new “Raw CSS” styles are added
  • Fix bug in parent dependencies
  • Fix bug where stylesheet dependency arrays are not being initialized
  • Add action hook to extend copy theme settings feature
  • Display non active tabs, enable upgrade/register before config data is created
  • Show raw results after Analysis to help debugging
  • Fix javascript not escaping quotes in input fields
  • Restored original ajax preview and added fallback method for cross-domain preview
  • Fix in javascript affecting Pro users
  • Cross domain Parse error
  • Showing “reconfigure” message on new install
  • Manual upgrade Pro from plugin
  • Add pre_option stylesheet and template filters to Preview class
  • Use child theme name on duplicate
  • Ability to force/unforce dependency
  • Identify and handle imported stylesheets, convert to links
  • Fixes related to testing if CTC Pro is installed


  • change packer class to use standard < 5.4 array syntax
  • Loading dictionaries on demand
  • Reversed key/value dictionary structure for huge memory improvement
  • Added packer class to flatten multidim arrays for huge memory improvement
  • Reduced key name lengths throughout
  • Improved data validation on inputs
  • Require minimum Pro version ( Pro users only )
  • Move html output to separate view includes
  • Move theme mod routines to own functions


  • Fix: preview not parsing parent styles correctly when minimized.
  • Fix: cast argument to array in sort functions.
  • Updated Child Theme Configurator language template.
  • Updated child theme preview class to use is_theme_active and other methods to eliminate conflicts with Jetpack and any other plugin that references the customize manager.
  • Updated child theme preview class to send origin headers and run customize_preview_init action along with some other actions.
  • Added logic conditions in preview class to help prevent Analyzer from failing in some cases
  • Enabled theme zip file export for any selected theme independent of theme currently loaded in Configurator
  • Fixed bugs present with servers not running Apache with SuExec
  • Fixed issue with Windows servers that do not return C: with filesystem paths
  • Automatically set priority of enqueue hook based on value from parent theme
  • Made file scan routine more efficient
  • Support for background-image as base64 data
  • Tweaked analyzer signals
  • Updated language template and de_DE files
  • Fix: case where child stylesheet link was not being added resulting in “This child theme does not load a Configurator stylesheet” notice
  • Fix: fatal error in debug mode
  • Minor bug fixes
  • New Theme Analyzer automatically checks for issues and determines correct settings
  • Step by step setup of Parent/Child settings
  • Simplified parent stylesheet handling options
  • Option to write new child theme styles to a separate stylesheet
  • Uses WordPress style dependencies to ensure correct child theme stylesheet load order
  • Automatically repairs themes that use outdated stylesheet handling methods
  • Parses parent theme files and only displays templates that can be be overridden by child themes
  • Numerous minor bug fixes


  • Fix: regression bug in 1.7.9 causing new property menu to fail
  • Fix: use nonce when retrieving front-end html to parse default additional stylesheets
  • Refactored classes to make Child Theme Configurator more lightweight on front end
  • Fix: disable autoload on configuration data options
  • Fix: normalize media query and add to menu when added via raw css
  • Fix: Margin and Padding shorthand generated incorrectly.
  • Addressed case where parent or child theme is in subdirectory.
  • Minimized admin CSS.
  • Sanitize child theme slug
  • Remove cascade load order comments from generated CSS
  • Set admin background to prevent theme override
  • Refactored background normalization function to better follow CSS specification.
  • Check child theme exists function case-insensitive.
  • Changed chldthmcfg.init() call to fire on load instead of .ready() to prevent JS conflicts
  • Uses spectrum color picker to support transparency and named colors.
  • Refactored entire system to support fallback values for any property.
  • Fix path when duplicating child theme on first run
  • New Feature: “delete child values” button – easily revert custom styles in child theme stylesheet
  • Will not write child theme stylesheet if error detected in functions.php
  • Fixed minified JS
  • Restored multisite admin menu link under Tools by popular demand
  • Automatically Network enables new child theme on creation
  • Fix for FTP notice – now uses PHP_OS constant to detect win vs nix
  • Added duplicate child theme feature
  • added dismiss option to warnings by popular demand.
  • Changed @import tab to “Web Fonts.” @import statements are automatically converted to enqueued external links.
  • Added “Enqueue both parent and child stylesheets” option to enable child theme overrides without using @import.
  • Added checks for hard-coded link tags in header template to help resolve incorrect stylesheet load order.
  • Fix: “Enqueue child stylesheet” now passes correct value.
  • Fix: hide called before iris init
  • Fix: @import not being written on rebuild/configure
  • Fix: min height on property/value panel
  • Only prune child theme selectors on rename
  • Removed conflicting wistia javascript link
  • New Feature: Enqueue child theme stylesheet option for themes that do not load it.
  • New Feature: Child Theme and Author website, description and tag fields.
  • Fix: Redesigned UI Javascript using jQuery objects for better browser memory management.
  • Fix: Child Theme Stylesheet version is timestamped to force browser reload after changes.


  • Fix: Empty functions file created causing inserted markers to be output to browser.
  • Fix: check for closed PHP tag in functions file prior to inserting markers
  • Fix: undefined constant LILAEAMEDIA_URL
  • Fix: logic to determine whether to display config notice
  • Fix: incorrect path generation and validation on Windows servers
  • Added error handling and notification to prevent jQuery conflicts and out of memory conditions
  • Fix: removed max-height on property/value overlay
  • Added debug option
  • New Feature: Copy selector button for Raw CSS textarea on Query/Selector tab.
  • Fix: Menus rendering incorrectly for RTL locales
  • Fix: Border-top etc. not being written correctly to stylesheet
  • Fix: Refactored ajax semaphore logic and flow
  • New Feature: Better child theme handling for multisite. Moved interface to Themes menu and check for network enabled.
  • Fix: Restrict child theme configurator access to install_themes capability
  • Fix: Preview links to Themes admin if not network enabled to prevent ‘Cheatin, uh?’ error.
  • Fix: only users with “install_themes” capability have access to Child Theme Configurator. This resolves permission issues with both multisite and single site installs. MULTISITE USERS: The Admin HAS MOVED to Network Admin > Themes > Child Themes for better handling for multisite (network) installs.
  • Fix: Regular expression introduced in version 1.6.2 parses selectors incorrectly.
  • Fix: replaced wp_normalize_path with class method to support legacy WP versions
  • Fix: support for multiple layered background images
  • Fix: background:none being parsed into gradient origin parameter
  • Fix: support for data URIs
  • Fix: support for *= and ^= notation in selectors
  • Fix: add check if theme uses hard-wired stylesheet link and alert to use @import instead of link option
  • Fix: conflicts with using jQuery UI from CDN – using local version of 1.11.2 Widget/Menu/Selectmenu instead
  • Fix: using wp-color-picker handle instead of iris as dependency to make sure wpColorPicker() methods are loaded
  • Fix: copy parent theme widgets logic is different when child theme is active
  • New Feature: option to load parent stylesheet using wp_enqueue_style (link), @import or none.
  • Thanks to cmwwebfx and Shapeshifter3 for pushing me on this
  • New Feature: automatically-generated slug and name
  • New Feature: restore from backup and reset options
  • New Feature: backup files to “Child Theme Files” on Files Tab so they can be deleted
  • New Feature: Added new theme chooser select menu with screenshot, theme info and link to live preview.
  • Fix: Admin scripts now only load when CTC page is being viewed.
  • Fix: parent CSS preview to correctly display all parsed parent stylesheets in sequence
  • Fix: Refactored throughout for maintainability


  • New Feature: Load imported stylesheets into the CTC admin so web fonts can be previewed.
  • Set preview swatch to z-index -1 to prevent it from covering up the controls
  • Spread config data across multiple option records to prevent out of memory errors with large stylesheets.
  • Do not automatically select Bootstrap CSS files as additional stylesheets to (greatly) reduce overhead.
  • Add jQuery UI styles that are no longer being loaded by default in the WP admin (autoselect menus).
  • Fixed a bug in the way zero values are handled that was breaking css output in certain situations
  • Added regex filter for non-printable (e.g., null) characters in input strings
  • Fixed a bug introduced in v1.5.2(.1) that copied all of the parent styles to the child theme stylesheet. This should only be an issue for ‘background-image’ styles that reference images in the parent theme and do not have child theme overrides.
  • Rolled back changes to the javascript controller that introduced a number of type errors.
  • Tweaked preview ajax call to handle ssl.
  • Automatically set additional stylesheets to parse based on parent theme links in head.
  • Render parent CSS including additional stylesheets
  • Added copy option to Parent/Child tab to assign menu locations, sidebars/widgets, custom header, background, and other options to new Child Themes.
  • Refactored CTC to use the WP_Filesystem API.
  • Non suExec configurations will now require user credentials to add, remove or update Child Theme files.
  • Added the ability for you to make the files writable while editing and then make them read-only when you are done.
  • You can also set your credentials in wp-config.php:


  • Removed backreference in main CSS parser regex due to high memory usage.
  • Fixed uninitialized variable in files UI.
  • Feature: export child themes as zip archive
  • Added transform to list of vendor properties
  • Bug fixed: parser not loading multiple instances of same @media rulesets
  • Refactored uploader to use wp core functions for compatibility and security
  • Increased CHLD_THM_CFG_MAX_RECURSE_LOOPS to 1000 to accommodate complex parent frameworks
  • Fix: javascript bug
  • Fix: regression bug – sanitizing broke raw input selectors
  • Fix: escape quotes in text inputs. This has bugged me for a while now.
  • Fix: Escape backslash for octal content values. Thanks Laurent for reporting this.
  • Fix: Normalize colors to lowercase and short form when possible to prevent duplicate entries in the data
  • Refactored the way CTC caches updates and returns them to the UI controller to reduce memory consumption.
  • Prevent out of memory fatals when generating new child themes.
  • Changed “Scan Parent for Additional Stylesheets” to individual checkbox options for each file with a toggle to show/hide in the Parent/Child tab.
  • Added automatic update of form when Parent Theme is changed.
  • Pre-populate Parent/Child form when parent slug is passed to CTC options.
  • updated parser to match selectors containing parentheses and empty media rulesets
  • Tweaked the Files tab options and added check for DISALLOW_FILE_EDIT
  • Removed automatic @import rules for additional stylesheets that are loaded.
  • Fixed bug caused by new jQuery .css function handling of empty css values (preview swatch).
  • New Feature: Theme Files tab:
  • Copy parent templates to child themes to be edited using the Theme Editor.
  • Remove child theme templates.
  • Upload child theme images.
  • Remove child theme images.
  • Upload child theme screenshot.


  • Fixes a bug with the way the @import data is stored that threw errors on php 5.3 and corrupted v1.3.2 @import data.
  • New Feature: option to scan parent theme for additional stylesheets. This allows CTC to be used with themes such as “Responsive” by CyberChimps.
  • New Feature: automatically copies parent theme screenshot to child.
  • Fixed unquoted regex pattern in file path security check function. Thanks to buzcuz for reporting this.
  • Updated help tab content. Added additional sanitization of source and target file paths.
  • Changed CSS preview to retrieve directly from WordPress Admin instead of remote http GET to prevent caching issues.
  • Added loading icon for CSS preview.
  • Fixed JS type error on backup toggle.
  • Improved extensibility throughout.


  • Replace PHP short tags with standard codes.
  • New Features: You can now rename selectors in place from the Query/Selector panel. Made stylesheet backup optional. Bugs fixed: Incorrect parsing of background position when ‘0’, fixed type error when background image url value is removed.
  • Bugs fixed: “star hack” properties no longer throwing js error. Important flag now works on borders and gradients.
  • New features: Link to Query/Selector tab from specific Property/Value selector, new property focus on adding new property. Bugs fixed: clear Query/Selector inputs when loaded selector is empty, use latest min.js script.


  • Added check for writability before attempting to create child theme files to avoid fatal error on servers not running suEXEC. Fixed a bug in the ctc_update_cache function that was throwing a fatal JS error when new media queries were saved via the Raw CSS input. Configurator now adds functions.php file to child theme when it does not exist.
  • Added reorder sequence and important flag functionality. Fixed bug where multiple inputs with same selector/property combo were assigned the same id. Fixed bug in the shorthand encoding routine.
  • Added tutorial video to help tabs.
  • Added call to reset_updates() before update_option() to prevent serialization errors.
  • Query/Selector panel now defaults to ‘base’
  • Fixed bug causing background-image with full urls (http://) to be parsed as gradients
  • Fixed bug causing property menu to throw error when selector has no properties
  • Fixed sort bug in shorthand parser that was returning properties in wrong order
  • Fixed bug that assumed lowercase only for theme slugs. (Thanks to timk)
  • Fixed update redirect to execute on first run
  • Small bug fix to javascript (casting number to string)
  • Fixed major bug where inputs containing ‘0’ were being ignored
  • Removed “no leading digits” requirement for theme slug
  • Change query sort function to keep parent order of queries without device width rules
  • Fixed gettext calls to use static namespace parameter
  • Auto populate child theme inputs when existing theme is selected
  • Correctly remove border when values are blanked
  • Fixed duplicate “new property” bug on Query/Selector panel
  • added timestamp to backup file
  • Added encode_shorthand function to recombine margin/padding values when all 4 sides are present
  • Corrected parsing for certain backgrounds and gradients (e.g., supports hsla color syntax)
  • Handle empty selectors
  • Ajax load for menus and updates
  • Clean up Parent/Child form UI and validation
  • Streamlined UI overall


  • Initial release.