Support » Theme: Twenty Ten » Updating Theme after using Child Theme Configurator plugin

  • Resolved miguelrzdesign17

    (@miguelrzdesign17)


    Hello,

    I need to update the active theme Twenty Ten – Version 2.5 on a live site that was built without a child theme. I don’t want to overwrite any custom code.

    I am trying to update the theme by creating a child theme first using the Child Theme Configurator plugin and activating the child theme before updating the parent theme.

    Before creating the child theme, the plugin gave me a warning, which I will include below. I went ahead and created the child theme to see what it did, since this didn’t occur in my local development copy of this site (Running Apache, MySQL version 5.6.38 and PHP 7.2), and the child theme on the live site gave me the error I am including below.

    THE WARNING:

    The theme “Twenty Ten Child” generated unexpected PHP debug output:
    Warning: Use of undefined constant minor – assumed ‘minor’ (this will throw an Error in a future version of PHP) in /…/wp-config.php on line …
    ! This theme loads the parent theme’s style.css file outside the wp_styles queue.
    This is common with older themes but requires the use of @import, which is no longer recommended. You can try to resolve this using the “Repair header template” option (see step 6, “Additional handling options”, below).

    THE ERROR:

    Notice: Use of undefined constant minor – assumed ‘minor’ in /…/wp-config.php on line …
    Use of undefined constant minor – assumed ‘minor’ in wp-config.php
    Please Note:
    The analyzer reveals errors that may otherwise go undetected. Unless this is a fatal error, WordPress may appear to work correctly; however, PHP will continue to log the error until it is resolved. Please contact the author of any theme or plugin mentioned above and cut/paste the error from the text area. Do not use a screen capture as it may cut off part of the error text. Additional information about the error may also be available in the CTC documentation.
    http://www.childthemeconfigurator.com/child-theme-faqs/

    THE CODE ON wp-config.php MENTIONED IN THE ERROR:

    require_once(ABSPATH . ‘wp-settings.php’);

    ADDITIONAL INFO:

    1. No Javascript errors on browser console
    2. Running W3 Total Cache Version 0.9.7
    3. VPS server – cPanel – FatCow hosting
    4. PHP 7.2
    5. WordPress version 4.9.9

    Please let me know what may be causing this error and how I may be able to fix it when you get the chance. I have contacted the plugin author (waiting on response) but I was hoping I could get input from the theme team if you will. I would really appreciate it.

    Thank you,
    Miguel

Viewing 1 replies (of 1 total)
  • The Child Theme Configurator plugin support folks have helped me resolve this issue. Thank you nonetheless. Here are the changes that needed to be made to my wp-config.php file:

    1. Move constant definition higher up in the procedure. All constant definitions must occur before the call to wp-settings.php or “constant already defined” warnings will occur.
    2. Add quotes around the value of WP_AUTO_UPDATE_CORE. This fixed the “bare word” warning.

    Code at the end of wp-config.php file [BEFORE CORRECTION]:

    /** Sets up WordPress vars and included files. */
    require_once(ABSPATH . ‘wp-settings.php’);

    /** Disables Automatic WordPress Core Updates. Allows Minor Updates. */
    define( ‘WP_AUTO_UPDATE_CORE’, minor );

    Code at the end of wp-config.php file [AFTER CORRECTION]:

    /** Disables Automatic WordPress Core Updates. Allows Minor Updates. */
    define( ‘WP_AUTO_UPDATE_CORE’, ‘minor’ );

    /** Sets up WordPress vars and included files. */
    require_once(ABSPATH . ‘wp-settings.php’);

Viewing 1 replies (of 1 total)
  • The topic ‘Updating Theme after using Child Theme Configurator plugin’ is closed to new replies.