CalderaWP / Caldera-Forms

Drag and drop, responsive WordPress form builder.
https://CalderaForms.com
GNU General Public License v2.0
187 stars 163 forks source link

Caldera Compatibility issues with WooCommerce 3.3.5 #2453

Closed steveconnerton closed 5 years ago

steveconnerton commented 6 years ago

Caldera has compatibility issues with WooCommerce v3.3.5. I was getting the Submission Rejected; invalid Token error, so immediately thought it was my caching, but was able to verify that it wasn't. So I dug deeper and was able to find this:

Warning: Invalid argument supplied for foreach() in /var/www/html/wp-content/plugins/woocommerce/includes/class-wc-api.php on line 284

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-content/plugins/woocommerce/includes/class-wc-api.php:284) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1248

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-content/plugins/woocommerce/includes/class-wc-api.php:284) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1248

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-content/plugins/woocommerce/includes/class-wc-api.php:284) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1248

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-content/plugins/woocommerce/includes/class-wc-api.php:284) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1248

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-content/plugins/woocommerce/includes/class-wc-api.php:284) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1248

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-content/plugins/woocommerce/includes/class-wc-api.php:284) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1248

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-content/plugins/woocommerce/includes/class-wc-api.php:284) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1248

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-content/plugins/woocommerce/includes/class-wc-api.php:284) in /var/www/html/wp-includes/rest-api/class-wp-rest-server.php on line 1248

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-content/plugins/woocommerce/includes/class-wc-api.php:284) in /var/www/html/wp-includes/rest-api.php on line 544

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-content/plugins/woocommerce/includes/class-wc-api.php:284) in /var/www/html/wp-includes/rest-api.php on line 545

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-content/plugins/woocommerce/includes/class-wc-api.php:284) in /var/www/html/wp-includes/rest-api.php on line 546

Warning: Cannot modify header information - headers already sent by (output started at /var/www/html/wp-content/plugins/woocommerce/includes/class-wc-api.php:284) in /var/www/html/wp-includes/rest-api.php on line 547 {"nonce":"88f9edba06"}

Hope this is helpful. I am going to reach out to Woo as well.

Thanks, Steve

Do You Need Immediate Help?

Is This A Feature Request?

What Version Of Caldera Forms, WordPress and PHP Are You Using?

*You can copy the "Short Debug" line from the Caldera Forms support menu's debug tab

Does Your Issue Persist When You Disable All Other Plugins and Switch To The Default Theme?

What Is The Unexpected Behaviour?

What PHP Errors Have You Logged While Reproducing This Bug?

What JavaScript Errors Have You Seen While Reproducing This Bug?

Shelob9 commented 5 years ago

I'm going to close this as this is related to a feature -- token check -- that is no longer in use.