Child Theme missing INC and CSS folder or not inheriting

  • So I just purchased Serenity Pro. I installed it and activated the license. I realized that the footer in customization would not let me specify PHP or a shortcode for the current year, so I installed the child theme. The previously set settings, did not copy across which was not that big of a deal. After getting everything set, I realized the site wasn’t working fully and checking the inspector showed a bunch of 404’s for the path to the child theme INC and CSS folder. I manually copied those across but something doesn’t seem right with that. Is something else going on or did I mess something up?

    EDIT: After copying those 2 folders into the child theme, everythings works, but the inspector still shows warning 404’s for the missing .map files.

    • This topic was modified 4 months, 3 weeks ago by mcadle.

    Hello,

    You can ignore the warning for the .map files.

    We will fix this in the next update of Serenity Pro.

    Figured as much. Do we need to move INC and CSS folders to the child theme and if so, are there others that need to go as well?

    Hello,

    No you don’t need to move those folders over.

    BTW, you cannot place PHP code or a shortcode in the Footer customization field because it filters our HTML characters.

    You need to edit the footer.php file itself.

    You can always copy it over to the child theme and edit it there.

    Yes, that is what I ended up doing. I still am getting several JS errors in the console. Sporadic things, like jQuery throwing undefined reference to $ in the admin customizer when I changed the number of widget sections in the features section. Clicking publish and refreshing saves the change. Do you know why we would be getting the 404’s for missing files in the inc/kirki folder then? The full path was to https://mayumitayake.com/wp-content/themes/serenity-pro-child/inc/kirki/assets/vendor/selectWoo/kirki.css, etc

    Thanks and love the theme by the way. We have been using Elegant Themes Divi for a very long time but its becoming very complex to use and manage so I branched out and found yours. Way simpler to use and I think we are getting better results and cleaner UI for client edits. I am probably going to start using this theme as the base for all of our other projects that are coming up. Excellent work.

    Edit: Man, I just realized I created this thread in the wrong forum. If you can move it and feel free to do so – my apologies.

    • This reply was modified 4 months, 3 weeks ago by mcadle. Reason: I am an idiot
    • This reply was modified 4 months, 3 weeks ago by mcadle. Reason: Still an idiot but trying to clarify

    Yes, that is what I ended up doing. I still am getting several JS errors in the console. Sporadic things, like jQuery throwing undefined reference to $ in the admin customizer when I changed the number of widget sections in the features section. Clicking publish and refreshing saves the change. Do you know why we would be getting the 404’s for missing files in the inc/kirki folder then? The full path was to https://mayumitayake.com/wp-content/themes/serenity-pro-child/inc/kirki/assets/vendor/selectWoo/kirki.css, etc

    Thanks and love the theme by the way. We have been using Elegant Themes Divi for a very long time but its becoming very complex to use and manage so I branched out and found yours. Way simpler to use and I think we are getting better results and cleaner UI for client edits. I am probably going to start using this theme as the base for all of our other projects that are coming up. Excellent work.

    Edit: Man, I just realized I created this thread in the wrong forum. If you can move it and feel free to do so – my apologies.

    • This reply was modified 4 months, 3 weeks ago by mcadle.

    Yes, that is what I ended up doing. I still am getting several JS errors in the console. Sporadic things, like jQuery throwing undefined reference to $ in the admin customizer when I changed the number of widget sections in the features section. Clicking publish and refreshing saves the change. Do you know why we would be getting the 404’s for missing files in the inc/kirki folder then? The full path was to wp-content/themes/serenity-pro-child/inc/kirki/assets/vendor/selectWoo/kirki.css, etc

    Thanks and love the theme by the way. We have been using Elegant Themes Divi for a very long time but its becoming very complex to use and manage so I branched out and found yours. Way simpler to use and I think we are getting better results and cleaner UI for client edits. I am probably going to start using this theme as the base for all of our other projects that are coming up. Excellent work.

    Edit: Man, I just realized I created this thread in the wrong forum. If you can move it and feel free to do so – my apologies.

    Here are some more errors that come from the child theme but not when we use the parent theme:

    Uncaught TypeError: Cannot read property ‘focus’ of undefined at <anonymous>:1:58

    This occurs when clicking Add Features Widget from the customizer. If we go to Widgets and then add it there, it works.

    Hello,

    Hope you had a pleasant weekend.

    Glad you like it, what do you think of the partial edit shortcuts in the customizer? Do you find it helps a lot with customization?

    As to the issues you are experincing. Have you installed the jQuery Migrate Helper plugin?

    Enable jQuery Migrate Helper

    We will also invesigate the console errors with a child theme here on our development server so we can include fixes in the next update.

    I have not installed the helper as when I use the parent theme, I do not experience any errors. It is only with the child theme and only in the customizer.

    I like the partial edit shortcuts. I think everything is really well laid out and works very very well. I am only using a child theme in order to inject the current date in the footer, if I was able to use a shortcode in the footer then I would have no need for a child theme at all.

    Hello,

    As long as the console errors only appear in the Customizer then it’s nothing to be concerned about, though we will still investigate and fix on our end.

    Wes will be releasing an update soon as WordPress 5.6 will be released on the 8th.

You must be logged in to reply to this topic.