WooCommerce 2.3.1 Blanco Fatal error: Call to undefined method

This topic has 4 replies, 3 voices, and was last updated 9 years, 2 months ago ago by Robert Hall

  • Avatar: inkarna
    inkarna
    Participant
    February 12, 2015 at 00:44

    Just updated to the newest WooCommerce 2.3.1 and have the following fatal error appearing.

    Fatal error: Call to undefined method WooCommerce::get_image_size() in [full path in private content] themes/blanco/woocommerce/content-product.php on line 54

    It is on the homepage of 2smock.com and rather a problem. I will try find a work around but it would appear that the Blanco theme needs to be updated again.

    Thanks for any suggestions or help, don’t want to mess up the code but can edit it a little if it solves the issue while the problem is being fixed.

    UPDATED: have temporarily edited the site to default to the blog so that I don’t loose too many customers in the mean time.

    Please, contact administrator
    for this information.
    3 Answers
    Avatar: russlib
    russlib
    Participant
    February 12, 2015 at 06:29

    Got same problem. Just go to Appearance –> Editor –> content-product.php and replace

    
    $placeholder_width = $woocommerce->get_image_size( ‘shop_catalog_image_width’ );
    $placeholder_height = $woocommerce->get_image_size( ‘shop_catalog_image_height’ );

    with

    // $placeholder_width = $woocommerce->get_image_size( ‘shop_catalog_image_width’ );
    // $placeholder_height = $woocommerce->get_image_size( ‘shop_catalog_image_height’ );

    Works for me.

    Avatar: inkarna
    inkarna
    Participant
    February 12, 2015 at 11:20

    Thank you russlib for that, working well now.

    Avatar: Robert Hall
    Robert Hall
    Support staff
    February 12, 2015 at 11:31

    Hello,

    This bug will be fixed in the next theme update.
    Sorry for inconvenience.

    Regards,
    Robert Hall.

  • Viewing 4 results - 1 through 4 (of 4 total)

The issue related to '‘WooCommerce 2.3.1 Blanco Fatal error: Call to undefined method’' has been successfully resolved, and the topic is now closed for further responses

We're using our own and third-party cookies to improve your experience and our website. Keep on browsing to accept our cookie policy.