1. PROMO Subscribe our All Access Pass @ 75% OFF & access all our 16+ premium Divi extensions: Divi Block Pro, Carousel Toolkit, etc.LEARN MORE
Dismiss Notice
NEW Divi.Help Pro Carousel AI Toolkit - Magically turn your Divi design into carousel, simply by using our online toolkit. No plugins needed. Now it works with Divi 5 as well!Try our carousel AI toolkit
BEST Divi Block - A revolutionary drag & drop tool to easily mix & match 960+ premade blocks (Light & Dark) to kick start your Divi site design. Special module designs are included as well. Also newly added AI generator & color. Now it works with Divi 5 as well!
Learn More About Divi BlockFree Version ~ 340+ Free Blocks

Solved Child theme throwing warnings on one site (not others)

Discussion in 'Free Divi Community Forum' started by tinlizzy53, Sep 12, 2026 at 1:03 PM.

  1. tinlizzy53

    tinlizzy53 New Member

    When I activate my child theme on site https://famvin.org/en/ I get a debug log filled with the following warning:
    12-Sep-2026 16:57:43 UTC] PHP Notice: WP_Theme_JSON_Resolver::get_user_data(): Error when decoding a theme.json schema for user data. Syntax error in /usr/www/users/XXX/famvin-org/wp-includes/functions.php on line 6260
    This theme is active on 6 other sites in the same multisite network and never generates this error.

    I googled and Google AI tells me that there is a corrupt theme.json file causing the error. But, the child theme has no theme.json. If I run with Divi 5.12.1 (no child) on this site, there are no errors. But, I need a particular action that is coded in my functions file, so I need the child theme.

    Thoughts? I have tested every *.json file I can find in my site. ET says it is not Divi itself, and I tend to believe them. I am thinking that there is something corrupt[ed] in an option or in the particular site, but I can not seem to find it.
     
    1. PRO MEMBER PERKS Custom Color Scheme + Premade Layouts - A perfect combination to boost productivity:Try Now
  2. tinlizzy53

    tinlizzy53 New Member

    I finally resolved the issue: I copied the theme to a new directory and renamed it (new directory name, new name in style.css). Switched to the "new" child theme and all is well. My only guess is that there is something corrupt in the database associated with the "old" child theme or something cached that is corrupt. There was never any theme.json anywhere in the child theme.