Title: Fatal Error After Update Last modified: November 3, 2016 --- # Fatal Error After Update * [jcifuen1](https://wordpress.org/support/users/jcifuen1/) * (@jcifuen1) * [9 years, 6 months ago](https://wordpress.org/support/topic/fatal-error-after-update-60/) * Hi, * I’m fairly new to running a WordPress website, but I recently updated to the latest version of WooCommerce and got this error on my site. * Fatal error: Call to undefined function have_rows() in /home/content/a2pnexwpnas03_data03/ 65/3463565/html/wp-content/themes/econature/page-home.php on line 59 * Is there anyway to go back to a previous version of WooCommerce? * Thanks. Viewing 5 replies - 1 through 5 (of 5 total) * [D Smith a11n](https://wordpress.org/support/users/dsmithweb/) * (@dsmithweb) * Automattic Happiness Engineer * [9 years, 6 months ago](https://wordpress.org/support/topic/fatal-error-after-update-60/#post-8393425) * Hi there! * To first answer your question, you can get older versions of WooCommerce at [https://github.com/woocommerce/woocommerce/releases](https://github.com/woocommerce/woocommerce/releases) * …but at the risk of overstepping, that error has to do with your theme, and makes me wonder if the issue is really WooCommerce-related. Did you also update your theme recently? Is it possible you had custom code in your functions.php that got overwritten? * It’s your website, so of course you are free to do whatever you’d like, include running any version of open-source software you choose, but I would caution that using out-of-date e-commerce software (like older versions of WooCommerce) can present security risks. * [Peter Lawrenson](https://wordpress.org/support/users/lorro/) * (@lorro) * [9 years, 6 months ago](https://wordpress.org/support/topic/fatal-error-after-update-60/#post-8393838) * Agree, installing an older version is not the way to go. Try deactivating all plugins except WooCommerce. If the problem remains, it must be a theme problem and, for commercial themes, you should seek support from your theme vendor’s support service. * Thread Starter [jcifuen1](https://wordpress.org/support/users/jcifuen1/) * (@jcifuen1) * [9 years, 6 months ago](https://wordpress.org/support/topic/fatal-error-after-update-60/#post-8396047) * The theme was done by a developer my boss had hired so it is that. I had even contacted GoDaddy and that’s what they had said as well. I’m not very good at code at all so I’m not sure how to implement the older version of WooCommerce from github. I just want to go back to the older version in the meantime until I can figure something out because the error occurred after I updated the plugins. Are there specific steps to implementing the older version or is it easier if I just try to contact the developer that created the theme? * Thanks again for the advice so far guys. It really is appreciated. I just spent all day freaking out over the issue yesterday. * [Peter Lawrenson](https://wordpress.org/support/users/lorro/) * (@lorro) * [9 years, 6 months ago](https://wordpress.org/support/topic/fatal-error-after-update-60/#post-8396203) * Sometimes when WooCommerce is updated, the database schema is also updated. So reverting to old code may not be enough and you may have to revert to a backup copy of your database. * I don’t think have_rows() is a WooCommerce function. It comes from ACF (Advanced Custom Fields) who create plugins and software. It could be that the WooCommerce update is a coincidence. If the update was the cause, this forum would be inundated with posts about have_rows(). So; – try deactivating WooCommerce, do you still get the error? – have you got any ACF plugins which came with your theme econature? Ensure they are still activated to ensure have_rows() is defined. – Ask your theme vendor’s support service, after all the error is coming from a theme file. This forum’s members don’t have access to commercial themes. [https://themeforest.net/item/eco-nature-environment-ecology-wordpress-theme/8497776/support](https://themeforest.net/item/eco-nature-environment-ecology-wordpress-theme/8497776/support) * Your developer should be well placed to resolve this, or if he is unavailable you could post a job: [http://jobs.wordpress.net/](http://jobs.wordpress.net/) * Thread Starter [jcifuen1](https://wordpress.org/support/users/jcifuen1/) * (@jcifuen1) * [9 years, 6 months ago](https://wordpress.org/support/topic/fatal-error-after-update-60/#post-8396421) * I had tried deactivating the woocommerce plugin and was still getting the error. And there are ACF plugins with the theme but I didn’t know how to check to see if they were defined or not (I really am terrible with code – currently looking into some courses). * I restored a previous version and contacted the developer about the theme and what to do from now on since I don’t want to run into the problem again. I will keep that Econature link bookmarked for the future. * I know this isn’t the smartest route, but I will bring up the security concerns with the developer if he ever gets back to me. Just currently have work that needs to get done on the site at the moment and I have a deadline to meet. * Thank you guys. I truly appreciate all the input. Viewing 5 replies - 1 through 5 (of 5 total) The topic ‘Fatal Error After Update’ is closed to new replies. * ![](https://ps.w.org/woocommerce/assets/icon.svg?rev=3234504) * [WooCommerce](https://wordpress.org/plugins/woocommerce/) * [Frequently Asked Questions](https://wordpress.org/plugins/woocommerce/#faq) * [Support Threads](https://wordpress.org/support/plugin/woocommerce/) * [Active Topics](https://wordpress.org/support/plugin/woocommerce/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/woocommerce/unresolved/) * [Reviews](https://wordpress.org/support/plugin/woocommerce/reviews/) ## Tags * [fatal error](https://wordpress.org/support/topic-tag/fatal-error/) * 5 replies * 3 participants * Last reply from: [jcifuen1](https://wordpress.org/support/users/jcifuen1/) * Last activity: [9 years, 6 months ago](https://wordpress.org/support/topic/fatal-error-after-update-60/#post-8396421) * Status: not resolved