Discover how to fix `JSON` and `PHP` errors caused by using `get_the_ID()` in a shortcode when working with Gutenberg for `WooCommerce` orders. --- This video is based on the question https://stackoverflow.com/q/72600835/ asked by the user 'Feel Content' ( https://stackoverflow.com/u/15040472/ ) and on the answer https://stackoverflow.com/a/73390024/ provided by the user 'Feel Content' ( https://stackoverflow.com/u/15040472/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions. Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Using get_the_ID() in a Shortcode Causes JSON and PHP Errors in Guttenberg Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/licensing The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/by-sa/4.0/ ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/by-sa/4.0/ ) license. If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com. --- Resolving get_the_ID() Errors in Shortcodes While Using Gutenberg in WordPress Have you ever been frustrated when your WordPress shortcode works perfectly on the front end but fails in the Gutenberg editor, throwing JSON and PHP errors? If you're building a content template with WooCommerce order information, you might encounter issues specifically when using get_the_ID(). In this guide, we will explore this common problem and walk you through the solution step by step. The Problem While working with the Toolslet plugin suite to dynamically display WooCommerce order information, a shortcode was created that functions flawlessly outside of Gutenberg. However, when the shortcode is used within the Gutenberg block editor, users experienced two main issues: JSON Error: "Updating failed. The response is not a valid JSON response." PHP Error: "Call to a member function get_data on bool." These errors are especially frustrating since they indicate that the method being called is not able to retrieve the expected order information. Understanding the Source of the Errors The root of the problem lies within the line of code designed to retrieve order data: [[See Video to Reveal this Text or Code Snippet]] In this context, the error emerges because get_data() returns a boolean value (false), implying that the order object $order could not be fetched correctly. It turns out that get_the_ID() is not fetching the actual WooCommerce order ID as intended but rather the ID of the content template being edited. This confusion arises due to how the WordPress backend interacts with the shortcode. The Solution After some investigation, we found a solution that effectively addresses the issue. Toolslet provides a straightforward option to prevent specific snippets from running in the WordPress backend. By using this option, you can ensure that the shortcode retrieves the correct order ID on the front end while avoiding errors in the backend editor. Step-by-step Guide To resolve this issue, follow these steps: Modify the Shortcode: Update your shortcode to include a condition that checks whether it is being run in the WordPress backend. This is crucial to avoid triggering the errors you’ve experienced. [[See Video to Reveal this Text or Code Snippet]] Implement the Changes: After adjusting your shortcode, you can now use it in your Gutenberg posts and templates without facing the previous errors! Test the Shortcode: Always ensure you test your changes by creating a few test orders and using the shortcode in different scenarios (both on the front end and back end). Conclusion By using the tools available to you in Toolslet and implementing a simple conditional check for admin environments, you can effectively avoid the pitfalls of using get_the_ID() in shortcodes for your WooCommerce orders. This approach ensures a smoother experience whether you are customizing the backend or building user-facing features. If you have found this guide helpful, or if you have any further questions about WooCommerce or WordPress development in general, feel free to reach out or leave a comment below. We would love to hear your thoughts!