Issue with my store page

Hi Dylan,
Maintenance mode disabled!

Thanks Dylan. I prefer to continue here, so other people in the future can also try to fix a similar error 🙂

This’s Debug-log:

[05-Feb-2022 16:48:06 UTC] PHP Fatal error:  Uncaught Error: Call to undefined method WP_Error::get_data() in /home/u178952842/domains/frigoca.com/public_html/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/RestApi.php:64
Stack trace:
#0 /home/u178952842/domains/frigoca.com/public_html/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/BlockTypes/AbstractBlock.php(352): Automattic\WooCommerce\Blocks\RestApi->get_routes_from_namespace('wc/store')
#1 /home/u178952842/domains/frigoca.com/public_html/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/BlockTypes/AbstractBlock.php(323): Automattic\WooCommerce\Blocks\BlockTypes\AbstractBlock->enqueue_data(Array)
#2 /home/u178952842/domains/frigoca.com/public_html/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/BlockTypes/AbstractBlock.php(85): Automattic\WooCommerce\Blocks\BlockTypes\AbstractBlock->enqueue_assets(Array)
#3 /home/u178952842/domains/frigoca.com/public_html/wp-includes/class-wp-block.php(255): Automattic\WooCommerce\Blocks\BlockTypes\AbstractB in /home/u178952842/domains/frigoca.com/public_html/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/RestApi.php on line 64
[05-Feb-2022 16:48:22 UTC] PHP Fatal error:  Uncaught Error: Call to undefined method WP_Error::get_data() in /home/u178952842/domains/frigoca.com/public_html/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/RestApi.php:64
Stack trace:
#0 /home/u178952842/domains/frigoca.com/public_html/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/BlockTypes/AbstractBlock.php(352): Automattic\WooCommerce\Blocks\RestApi->get_routes_from_namespace('wc/store')
#1 /home/u178952842/domains/frigoca.com/public_html/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/BlockTypes/AbstractBlock.php(323): Automattic\WooCommerce\Blocks\BlockTypes\AbstractBlock->enqueue_data(Array)
#2 /home/u178952842/domains/frigoca.com/public_html/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/BlockTypes/AbstractBlock.php(85): Automattic\WooCommerce\Blocks\BlockTypes\AbstractBlock->enqueue_assets(Array)
#3 /home/u178952842/domains/frigoca.com/public_html/wp-includes/class-wp-block.php(255): Automattic\WooCommerce\Blocks\BlockTypes\AbstractB in /home/u178952842/domains/frigoca.com/public_html/wp-content/plugins/woocommerce/packages/woocommerce-blocks/src/RestApi.php on line 64

EDIT: (Please let me know if there’s any information that I should hide for security).

• This reply was modified 4 years, 7 months ago by Daniel.

Hello Dylan,

After contacting Woocommerce support and performing a test for plugins and themes conflicts, I discovered that the error appears when activating the “Woostify Pro” plugin. So the error is related Woostify apparently.

“A conflict is an error or malfunction caused by two parts of code giving conflicting signals.”

After reading that quote I remembered that the colors of the “add to cart” button seemed to be receiving code from two different places. I’m not sure if what I say is correct, the truth is that when you hover over the button, the background of the icon appears before the background of the rest of the button. (See the image: https://imgur.com/xmKtMrG).

The latter is less important than the general error that the store page presents when activating the Woostify Pro plugin.

I hope you can continue to help me solve it 🙁

It was a normal set up, practically automatic when installing woocommerce. The store page worked perfectly for a while. I’m pretty sure after the last Woostify Pro plugin update I went into the customizer and maybe I did something that caused the error. Unfortunately I didn’t realize it at the time so I can’t be 100% sure that it was.

I tried to see that everything was “normal” in the customizer and even made some changes to see if it fixed the error but nothing worked.

I remember that at some point I tried to create a new store page using the Elementor builder but it caused a conflict with the store archive, so I deactivated it and left the page created by default with woocommerce.