Back to Community
Home / Community / Plugin → Child theme configurator

Troubleshooting Common Child Theme Configurator Issues: Blank Tabs, Missing Styles, and More

34 threads Sep 16, 2025 Plugin → Child theme configurator

Content

Creating a child theme with the Child Theme Configurator plugin is usually a smooth process, but sometimes things don't go as planned. Based on community reports and solutions, here's a guide to diagnosing and fixing some of the most common issues users encounter.

1. Blank or Empty Tabs in the Configurator Interface

The Problem: You open the Child Theme Configurator, but most of the tabs (like Query/Selector) are blank, showing only a scroll bar. Debug output may show messages like 'config does not exist'.

Why it Happens: This is often caused by a PHP configuration or server environment issue that prevents the plugin's AJAX calls from completing successfully. It can also occur after a plugin or WordPress core update if there is a temporary conflict.

How to Fix It:

  1. Enable Debugging: Navigate to the plugin's Files tab and check the box to enable debug output.
  2. Reload: Go to Tools > Child Themes in your WordPress admin menu to reload the interface.
  3. Investigate: The debug output (which contains sensitive server info) can help pinpoint the issue. For security, do not post this output on public forums. The issue often resolves itself after a WordPress or plugin update.

2. Missing Menus, Widgets, or Header/Background Images

The Problem: After activating your new child theme, your custom menus, widget areas, header image, or background settings are missing or broken.

Why it Happens: The 'Copy Menus, Widgets and other Customizer Settings' option transfers most standard WordPress settings. However, some themes store this data in non-standard ways or in options that the plugin cannot automatically copy.

How to Fix It:

  1. Re-apply Settings Manually: The most common fix is to simply re-select your menu under Appearance > Menus and assign it to the correct location. Similarly, go to Appearance > Background and Appearance > Header to reassign your images for the child theme.
  2. Recreate Widget Areas: If specific widget areas are missing, you may need to recreate them manually in the child theme. Go to Appearance > Widgets, find the 'Manage Sidebars' option, and add a new sidebar with the exact same name as the one in the parent theme. Afterwards, run the 'Copy Settings' process in the Child Theme Configurator again.

3. Live Preview Doesn't Match the Activated Theme

The Problem: The Live Preview looks broken (e.g., images don't load, styling is off), but when you brave the activation, the live site looks correct.

Why it Happens: The WordPress Live Preview function can sometimes behave differently than a fully activated theme, especially with certain server configurations or themes that load assets in unique ways.

How to Fix It:

  1. Trust but Verify: This is a known quirk. It is always recommended to use Live Preview to check for major errors, but some minor discrepancies may not reflect the final result.
  2. Activate and Test: If the Live Preview shows your basic structure correctly but is missing some images, try saving and activating the theme. Often, the issues resolve themselves once the theme is active. Always have a recent backup before activating.

4. Responsive Design or Other Styles Break

The Problem: Your site's responsiveness or specific styles work in the parent theme but break in the child theme.

Why it Happens: Many themes load additional stylesheets beyond the main style.css file. If the child theme does not account for these, crucial CSS will be missing.

How to Fix It:

  1. Import Additional Stylesheets: In the Child Theme Configurator, go to the @imports tab. Manually add import rules for any additional stylesheets the parent theme uses (e.g., @import url(../parent-theme/css/responsive.css);).
  2. Auto-Scan: Check the box on the Configure tab to 'Scan parent theme for additional stylesheets' and then re-parse the styles. The plugin will attempt to find and import them for you.

5. "Destination folder already exists" Error

The Problem: You try to create a child theme, but the process fails with this error.

Why it Happens: This means a directory for your child theme already exists in the /wp-content/themes/ folder, likely from a previous, incomplete attempt.

How to Fix It:

  1. Use an FTP client or your web host's file manager to navigate to /wp-content/themes/.
  2. Find the folder named after your child theme (e.g., my-theme-child) and delete it.
  3. Return to the Child Theme Configurator and try the process again.

Remember, the Live Preview feature is your best friend for testing a child theme before making it active on your live site. If you encounter persistent problems, checking the theme's documentation for its specific methods of handling menus, widgets, and styles can provide further insight.

Related Support Threads Support