Title: WC_GET_LOOP_PROP Error
Last modified: August 19, 2020

---

# WC_GET_LOOP_PROP Error

 *  Resolved [houcatdad](https://wordpress.org/support/users/houcatdad/)
 * (@houcatdad)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/wc_get_loop_prop-error/)
 * Getting an error after update.
    At WP 5.5 and Just updated woocommerce. Everything
   was fine… ran the update, updated the database, everything was stable.
 * Now site won’t load. Call to Undefined function wc_get_loop_prop()
 * Only way to get the site to load, I changed the name of the woocommerce directory
   so that the plugin failed…. site starts up.
 * any ideas?

Viewing 4 replies - 1 through 4 (of 4 total)

 *  [Phil](https://wordpress.org/support/users/fullysupportedphil/)
 * (@fullysupportedphil)
 * Automattic Happiness Engineer
 * [5 years, 9 months ago](https://wordpress.org/support/topic/wc_get_loop_prop-error/#post-13282054)
 * This happens when third-party theme’s or plugins are making calls to your database
   that trigger WooCommerce functions before they have finished loading.
 * Some third-party theme and plugin developers have already released updates that
   resolves the problem. If yours has not, we’ve included a failback option in the
   next version of WooCommerce (4.4.1) that will prevent third-party code from doing
   that.
 * That version of WooCommerce has been released and should show as an available
   update on your site over the next 24hrs.
 *  Thread Starter [houcatdad](https://wordpress.org/support/users/houcatdad/)
 * (@houcatdad)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/wc_get_loop_prop-error/#post-13282197)
 * Is there a way to determine which plugin is doing it? Or is it usually the theme
 *  [Phil](https://wordpress.org/support/users/fullysupportedphil/)
 * (@fullysupportedphil)
 * Automattic Happiness Engineer
 * [5 years, 9 months ago](https://wordpress.org/support/topic/wc_get_loop_prop-error/#post-13282223)
 * Most reports I’ve seen so far are from the theme, but it can be your plugin.
 * To isolate the source, you can try temporarily switching your site to the default
   Twenty Twenty or Storefront theme. If that doesn’t help, then you can temporarily
   disable your plugins one at a time until the problem is resolved and you’ve identified
   the source.
 * If you’re site won’t currently load you can do this by access your site by FTP
   and then temporarily renaming your the folder for your active theme as well as
   each individual plugin folder. You can simply add “-test” or something simple
   to end of the folder name. This way you can easily return the folder name to 
   it’s original state when your done.
 *  [Daniel Milner](https://wordpress.org/support/users/danielmilner/)
 * (@danielmilner)
 * [5 years, 9 months ago](https://wordpress.org/support/topic/wc_get_loop_prop-error/#post-13282495)
 * If you don’t want to wait for the update, you can download v4.4.1 from their 
   Github page and upload it through the Add New Plugin screen. If you’re on WordPress
   5.5, it will allow you to update the plugin that way.
 * [https://github.com/woocommerce/woocommerce/releases/tag/4.4.1](https://github.com/woocommerce/woocommerce/releases/tag/4.4.1)

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘WC_GET_LOOP_PROP Error’ 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/)

 * 4 replies
 * 3 participants
 * Last reply from: [Daniel Milner](https://wordpress.org/support/users/danielmilner/)
 * Last activity: [5 years, 9 months ago](https://wordpress.org/support/topic/wc_get_loop_prop-error/#post-13282495)
 * Status: resolved