Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #664222

    Applying the Enfold 3.6.1 theme update crashed the entire website with a fatal error. Apparently your previous theme had an “avia_header_class”, but it was no longer used in the new theme. The solution was to manually copy and paste the new header.php code to the child header.php file. Why didn’t the update automatically update the child header.php file? We don’t want to crash the entire website every time we do an auto theme update.

    #664320

    Hey m,

    I’m not sure I understand what you mean by that but child themes are never updated unless you do it manually, that is the whole point of using a child theme. Please try to explain a bit further if I have misunderstood you.

    Regards,
    Rikard

    #664744

    Thank you for bearing with me. So, a theme update does not change the Child theme files. So when Enfold changed the header.php file, we must now update our Child header.php file in order to work with the updated Enfold theme? Is that correct? If yes, then a crash could happen again in the future? So, a Best Practices procedure would be to download the updated header.php file and compare to our Child header.php file before installing?

    #665264

    Hi,

    No problem, we are happy to help you out. I’m not sure what changes you have made in your child theme’s header file, but a child theme is supposed to override the parents header file. For instance, if you don’t have a file called header.php in your child theme folder, the header file from the parent will be used, and if you do have a file called header.php in the child theme folder, that will be used instead.

    I’m not sure exactly what you have in your child theme but if you try to explain what happened a bit further and post the code you have used we might be able to give you a better explanation.

    Regards,
    Rikard

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.