woocommerce/plugins
Vedanshu Jain efc9dc4c62
Check WC_Legacy_API instead of WC_API as that seems to be cached by lightspeed servers (#48593)
* Check WC_Legacy_API instead of WC_API as that seems to be cached by lightspeed servers.

* Improve the detection of the legacy API:

1. Modify the autoloader so that it never loads the WC_API class.

This is needed bacause the legacy REST API plugin itself does a
"class_exists('WC_API')". The plugin itself will continue to load
its own copy of the class without issues.

2. Detect the WC_Legacy_REST_API_Plugin class in the legacy API stub.

This is a performant and bulletproof way to detect if the plugin
is isntalled.

* Rearrange code a bit

---------

Co-authored-by: Nestor Soriano <konamiman@konamiman.com>
2024-06-19 14:29:03 +05:30
..
woo-ai Update to pnpm 9.1 (#47385) 2024-05-13 10:57:39 -03:00
woocommerce Check WC_Legacy_API instead of WC_API as that seems to be cached by lightspeed servers (#48593) 2024-06-19 14:29:03 +05:30
woocommerce-admin CYS - Optimize intro `professional-theme.svg` image (#48566) 2024-06-18 17:32:56 +02:00
woocommerce-beta-tester Remove the new old experience (#47814) 2024-05-24 18:00:22 +00:00
woocommerce-blocks [Experimental] Product Filters Redesign > Parent block: Enable block customizations (#47594) 2024-06-14 13:56:31 -03:00