Support » Theme: Storefront » upgrade to Version: 2.4.1 broke childtheme

  • Resolved NightL

    (@nightl)


    Upgrade to Version: 2.4.1 broke connection with child theme

    I tested turning off all plugins – that was not the issues

    Activated 2.4.1 – that works

    Activate my child theme again and get white screen

    Now installing backup

    Just a heads-up for others

Viewing 7 replies - 1 through 7 (of 7 total)
  • Hi!

    What child theme is it that you are using? Is it a custom child theme or one of the official child themes made by WooCommerce?

    If are getting a white screen, it means that you’re getting a PHP error. Please check your error log, there you’ll be able to find the exact error. Your hosting company should be able to help you with this.

    Thank you!

    Thank you Tiago

    It is a custom child theme which was originally set up with Child Theme Wizard plugin. Was just using functions.php, footer.php, header.php and css

    In the end I uploaded Version: 2.3.5 retrieved from a a back-up – did not do a full backup reinstall – all came back OK

    I have had this site in place for over three years and have done successive updates immediately as they come available – this time it fell over.

    I’ll try to find out what is going on via a testing server this time – will report back.

    same here! What is going on with Storefront?

    i’ve had the same issue WSOD with update to 2.4.1 on the frontend

    Jesse Pearson

    (@jessepearson)

    Automattic Happiness Engineer

    @nightl Typically a white screen is some sort of critical error. WooCommerce should be logging these for you so that you don’t have to FTP in to check the logs. They would be logged under WooCommerce > Status > Logs, and they are logged daily in the drop downs there.

    Looking here should help you determine where the conflict in code is happening. If you cannot determine this via the log, please put the log into something like https://gist.github.com/ or https://pastebin.com/ and provide the link here so that we can take a look.

    @nekokun @daverempel if you could do the same, as well, but create your own threads if you need us to take a look.

    @jessepearson thank you for your reply – prompted me to sort the issue out

    Just ran the update on my testing server

    opened the error log
    PHP Fatal error: Call to undefined function language_attributes() in /home/wwwXXXXXXXXpublic_html/shop/wp-content/themes/Storefront-Child/header.php on line 11

    which was
    <html <?php language_attributes(); ?> <?php storefront_html_tag_schema(); ?>>

    I removed <?php storefront_html_tag_schema(); ?> and all was well

    Having a quick look around I saw other people having the same issue as far back as 2015… looks like I was just lucky up till now as I run updates on everything asap

    but maybe it is time to rebuild my child theme

    it is mentioned here
    https://wordpress.org/support/topic/call-to-undefined-function-storefront_html_tag_schema/

    ________________________________________
    Having removed that bit of rogue code – (for my live site I actually dumped my custom code into a new copy of header.php in my child theme) – my site now happily sits on php7.2 – up till now it would fall over on anything above 5.6

    • This reply was modified 11 months, 1 week ago by NightL.
    • This reply was modified 11 months, 1 week ago by NightL.
    Jesse Pearson

    (@jessepearson)

    Automattic Happiness Engineer

    @nightl Glad my direction helped you sort it out, hopefully that will help others that are running into the same issue.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘upgrade to Version: 2.4.1 broke childtheme’ is closed to new replies.