Title: Critical error Last modified: May 5, 2020 --- # Critical error * Resolved [mothermayapple](https://wordpress.org/support/users/mothermayapple/) * (@mothermayapple) * [5 years, 11 months ago](https://wordpress.org/support/topic/critical-error-72/) * There is a critical error just now with your plugin, it crashes my whole website. I am deactivating it until it is resolved. * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fcritical-error-72%2F%3Foutput_format%3Dmd&locale=en_US) to see the link]_ Viewing 10 replies - 1 through 10 (of 10 total) * Plugin Support [slash1andy](https://wordpress.org/support/users/slash1andy/) * (@slash1andy) * Automattic Happiness Engineer * [5 years, 11 months ago](https://wordpress.org/support/topic/critical-error-72/#post-12785411) * Hey there! * What kind of errors are in your fatal error logs? Can you paste them here? That will help us figure out what is the source of the issue. If you are not sure where to locate logs, you can ask your host for the server error logs. * Hopefully that helps! Have a great one! * Thread Starter [mothermayapple](https://wordpress.org/support/users/mothermayapple/) * (@mothermayapple) * [5 years, 11 months ago](https://wordpress.org/support/topic/critical-error-72/#post-12785516) * There are several errors from today, here is an example: * 2020-05-05 08:41:33.061242 [NOTICE] [20444] [/home/mayapple/public_html/.htaccess: 143] Unsupported ErrorDocument URL: default, must start with ‘/’ or ‘http’. * I narrowed it down to the Square for Woocommerce plugin by activating plugins one at a time. Right now I have the plugin deactivate, so my website is working. If I activate the plugin, it crashes both the front- and back-end. * Thanks for your help with this! * Plugin Support [slash1andy](https://wordpress.org/support/users/slash1andy/) * (@slash1andy) * Automattic Happiness Engineer * [5 years, 11 months ago](https://wordpress.org/support/topic/critical-error-72/#post-12785557) * Hey again! * That’s actually not an error, that’s a [NOTICE] * Can you see if WooCommerce caught any fatals here: [https://d.pr/i/AAgUQw](https://d.pr/i/AAgUQw) * That’s in the Status > Logs page, and then the dropdown there will say if it has a fatal error log. If there’s not one there, then your host would be essentially your only source of logs for this. * Thread Starter [mothermayapple](https://wordpress.org/support/users/mothermayapple/) * (@mothermayapple) * [5 years, 11 months ago](https://wordpress.org/support/topic/critical-error-72/#post-12785584) * It occurred to me that it might be a conflict with Bulletproof Security which writes a number of rules to htaccess. To test that theory, I deactivated BPS plugin and deleted htaccess from my root folder. I still get a critical error when I activate the WooCommerce Square plugin, but the errors have changed: * 2020-05-05 08:59:53.029204 [INFO] [20443] [114.119.165.159:37182#APVH_mayapplesoaps. com:443] File not found [/home/mayapple/public_html/product-tag/garden-grown- ingredients] 2020-05-05 08:59:01.080553 [INFO] [20444] [107.180.109.27:55192# APVH_mayapplesoaps.com] File not found [/home/mayapple/public_html/401.shtml] 2020-05-05 08:59:01.080266 [INFO] [20444] [HTAccess] Configuration file [/home/ mayapple/public_html/.htaccess] has been removed. * None of these look like critical errors to me, but maybe you see something here that I do not… ? * Thread Starter [mothermayapple](https://wordpress.org/support/users/mothermayapple/) * (@mothermayapple) * [5 years, 11 months ago](https://wordpress.org/support/topic/critical-error-72/#post-12785592) * Ok, this should be more helpful: * 2020-04-27T07:04:23+00:00 CRITICAL Uncaught Error: Call to a member function getCursor() on string in /home/mayapple/public_html/wp-content/plugins/woocommerce- square/includes/Sync/Interval_Polling.php:261 Stack trace: #0 /home/mayapple/ public_html/wp-content/plugins/woocommerce-square/includes/Sync/Stepped_Job.php( 114): WooCommerce\Square\Sync\Interval_Polling->update_inventory_counts() #1 / home/mayapple/public_html/wp-content/plugins/woocommerce-square/includes/Sync/ Stepped_Job.php(55): WooCommerce\Square\Sync\Stepped_Job->do_next_step() #2 / home/mayapple/public_html/wp-content/plugins/woocommerce-square/includes/Handlers/ Background_Job.php(172): WooCommerce\Square\Sync\Stepped_Job->run() #3 /home/ mayapple/public_html/wp-content/plugins/woocommerce-square/includes/Handlers/ Background_Job.php(123): WooCommerce\Square\Handlers\Background_Job->process_job( Object(WooCommerce\Square\Sync\Interval_Polling)) #4 /home/mayapple/public_html/ wp-content/plugins/woocommerce-square/vendor/skyverge/wc-plugin-framework/woocommerce/ utilities/class-sv-wp-back in /home/mayapple/public_html/wp-content/plugins/woocommerce- square/includes/Sync/Interval_Polling.php on line 261 * [AITpro](https://wordpress.org/support/users/aitpro/) * (@aitpro) * [5 years, 11 months ago](https://wordpress.org/support/topic/critical-error-72/#post-12786855) * Someone who has WPEngine hosting found a solution for this problem > [https://wordpress.org/support/topic/square-to-woo-sync-broken/](https://wordpress.org/support/topic/square-to-woo-sync-broken/), but it looks like your host is A2 hosting. * > Anyone with this issue that uses WP Engine > Put this in your WP Config: > define( ‘WPE_GOVERNOR’, false ); - This reply was modified 5 years, 11 months ago by [AITpro](https://wordpress.org/support/users/aitpro/). * Thread Starter [mothermayapple](https://wordpress.org/support/users/mothermayapple/) * (@mothermayapple) * [5 years, 11 months ago](https://wordpress.org/support/topic/critical-error-72/#post-12786967) * AITpro, I also find that sync gets broken often Square -> WooCommerce. Should I try applying that fix even though I have a different host? * [AITpro](https://wordpress.org/support/users/aitpro/) * (@aitpro) * [5 years, 11 months ago](https://wordpress.org/support/topic/critical-error-72/#post-12787016) * Nope, don’t use the WPEngine fix since it would only work specifically for sites hosted on WPEngine. Unfortunately, google searches are pointing me back to this plugin’s support page. So I will butt out at this point since I don’t know much about this plugin. 😉 After rechecking the WPEngine fix it only works for Long Queries or Killed Queries. So wrong fix even if you did have WPEngine hosting. 😉 - This reply was modified 5 years, 11 months ago by [AITpro](https://wordpress.org/support/users/aitpro/). * Plugin Support [slash1andy](https://wordpress.org/support/users/slash1andy/) * (@slash1andy) * Automattic Happiness Engineer * [5 years, 11 months ago](https://wordpress.org/support/topic/critical-error-72/#post-12799051) * Hey again! * [@mothermayapple](https://wordpress.org/support/users/mothermayapple/) can you please update the Square plugin to the latest version (2.1.4) and see if that helps? * Plugin Support [slash1andy](https://wordpress.org/support/users/slash1andy/) * (@slash1andy) * Automattic Happiness Engineer * [5 years, 11 months ago](https://wordpress.org/support/topic/critical-error-72/#post-12840550) * Hey there! * We haven’t heard back from you in a while, so I’m going to mark this as resolved– if you have any further questions, you can start a new thread. Viewing 10 replies - 1 through 10 (of 10 total) The topic ‘Critical error’ is closed to new replies. * ![](https://ps.w.org/woocommerce-square/assets/icon-256x256.png?rev=3234354) * [WooCommerce Square](https://wordpress.org/plugins/woocommerce-square/) * [Frequently Asked Questions](https://wordpress.org/plugins/woocommerce-square/#faq) * [Support Threads](https://wordpress.org/support/plugin/woocommerce-square/) * [Active Topics](https://wordpress.org/support/plugin/woocommerce-square/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/woocommerce-square/unresolved/) * [Reviews](https://wordpress.org/support/plugin/woocommerce-square/reviews/) * 10 replies * 3 participants * Last reply from: [slash1andy](https://wordpress.org/support/users/slash1andy/) * Last activity: [5 years, 11 months ago](https://wordpress.org/support/topic/critical-error-72/#post-12840550) * Status: resolved