* * @see http://wcpos.com * @package WCPOS\WooCommercePOS */ namespace WCPOS\WooCommercePOS; use WCPOS\WooCommercePOS\Admin\Consent; use WCPOS\WooCommercePOS\Admin\Menu; use WCPOS\WooCommercePOS\Services\Auth as AuthService; use WCPOS\WooCommercePOS\Services\Extensions; use WCPOS\WooCommercePOS\Services\Receipt_Snapshot_Store; use WCPOS\WooCommercePOS\Services\Settings as SettingsService; /** * Init class. */ class Init { /** * Constructor — the plugin's entire `plugins_loaded` hook wiring. * * Reached from {@see Activator::init()}, which runs on `plugins_loaded` at the * default priority 10. Everything that must exist before `init` fires — most * importantly the `determine_current_user` pair — has to be registered here. * * NOT PURE WIRING. Constructing this class also, in statement order: * `require_once`s `wcpos-functions.php` and `wcpos-store-functions.php`; * registers the `wc_pos_user_uuid_locks` global cache group; READS the sync * schema-latch option; WRITES options through * `Config_Fingerprint::maybe_cleanup_legacy_options()` (one-time, latched on * its own version option); and SCHEDULES a daily cron event through * `Sync_Journal_Purge::register_hooks()`. Anything that constructs `Init` — * a test included — inherits all of that. * * ## How to read the ordering table * * A priority number decides ordering on its own, wherever in this method it * happens to be written. Statement order is load-bearing ONLY when two * callbacks share a hook AND a priority: WordPress then runs them in * registration order. Exactly one such pair exists here, and it is marked * ORDER-CRITICAL (STATEMENT ORDER) below — do not move it. * * Priorities that live in the callee (`Meta_Normalizer` at 5, `Revision` at 9, * the proxy stampers at 10) are listed at the value they actually register, * not at the position of the call in this method. Reordering those statements * changes nothing; changing those numbers changes everything. * * "Why" is recovered from `git log -S` / `git blame` where a reason was * recorded. Where none was, the entry says **unknown** rather than guessing. * * ## Ordering table * * | # | Hook | Callback | Pri | Order | Why that priority | * |---|------|----------|-----|-------|-------------------| * | 1 | `activated_plugin`, `upgrader_process_complete`, `admin_enqueue_scripts`, `admin_notices`, `rest_api_init` | `Admin\Consent` (5 callbacks) | 10 | irrelevant | Default. What matters is that `Consent` is built during `plugins_loaded`, so its lifecycle hooks exist before an activation/update request fires them. | * | 2 | `woocommerce_pos_rest_api_controllers` | `Sync\Api::register_controllers` | 10 | irrelevant | Default; sole callback. | * | 3 | `wcpos_integrity_digest_rebuild` | `Sync\Integrity_Digest::run_scheduled_rebuild` | 10 | irrelevant | Default; sole callback. Registered OUTSIDE the schema latch, so an already-scheduled rebuild still has a callback while the latch is down. | * | 4 | `woocommerce_pos_sync_proxy_response`, `..._serialized_product`, `..._serialized_order` | `Sync\Meta_Normalizer::normalize` | **5** | **ORDER-CRITICAL** | Must precede `Revision` at 9 so the stamped revision bytes equal what the write path recomputes from a bare `wc/v3` re-read. See `Sync\Augmentation_Pipeline` class docblock and `Sync\Meta_Normalizer::register_hooks()`. Kept out of the pipeline because it also serves the ORDER lane. | * | 5 | `woocommerce_pos_sync_serialized_order` | `Sync\Pos_Uuid::stamp_serialized_record` | 10 | order-critical (by number) | After `Meta_Normalizer` at 5, in step with the product lane's stampers. | * | 6 | `woocommerce_pos_sync_order_pull_payloads` | `Sync\Integrity_Digest::stamp_proxy_order_digests` | 10 | irrelevant | Default; sole callback on that filter. | * | 7 | `woocommerce_pos_sync_proxy_response` | `Sync\Revision::stamp_proxy_revisions` (via `Augmentation_Pipeline::install()`) | **9** | **ORDER-CRITICAL** | Between `Meta_Normalizer` (5) and the uuid/digest stampers (10). Revision must hash the normalized-but-not-yet-augmented payload. | * | 8 | `woocommerce_pos_sync_proxy_response`, `..._serialized_product` | `Proxy_Uuid_Stamper`, `Integrity_Digest` digest stampers, pipeline projections | 10 | order-critical (by number) | Preserved verbatim from the hand-wiring the pipeline replaced, so third-party code hooking either public filter still runs where it always did. | * | 9 | `woocommerce_before_product_object_save`, `woocommerce_before_product_variation_object_save` | `Sync\Pos_Uuid::stamp_on_save` | 10 | irrelevant | Default. The HOOK is the design (before the data store writes, so the uuid lands in the same save); the number is not. Registered unconditionally — identity is core, not an observer. | * | 9a | `untrashed_post`, `woocommerce_untrash_order` | `Sync\Pos_Uuid::recheck_ownership_after_untrash`, `::recheck_order_ownership_after_untrash` | 10 | irrelevant | Default. Re-proves uuid ownership when a record leaves the trash — the one seam a native restore passes through (#1805, ADR 0038). Unconditional for the same reason as row 9; the journal and digest observers (rows 10, 12) share both hooks at the same priority once the latch is set, and nothing depends on the order. | * | 10 | 32 catalogue/customer/order hooks, plus `shutdown` | `Sync\Sync_Journal` (34 callbacks) | 10 (`shutdown` at `PHP_INT_MAX`) | `shutdown`: order-critical (by number) | Default throughout. `woocommerce_update_order` only MARKS the order dirty; the `hook:update` row lands on `flush_pending_order_updates()` — at `shutdown`, before any other-origin row for that order, or when a different order is saved — so one online checkout writes one update row, not eleven. The shutdown flush runs LAST because WooCommerce saves the customer at 10 and the session at 20; a save those trigger after the flush is written immediately. | * | 10b | `delete_option` plus `pre_update_option_*`, `update_option_*`, `add_option_*`, `delete_option_*` for the two `Pos_Visibility::source_options()` | `Sync\Visibility_Observer` (9 callbacks) | 10 | irrelevant | Default. Appends the journal row for a record entering or leaving the POS servable set — the transition the sequence-log stream relies on, since it drops a hidden record's update rows. `delete_option` is the generic PRE-delete action (the per-option form fires after) and is gated on the option name inside the callback. Registered after `Sync_Journal` only because it writes through it; the constructor also runs the observer's one-time tombstone seed. | * | 11 | `wcpos_sync_journal_purge` | `Sync\Sync_Journal_Purge::run_purge` | 10 | irrelevant | Cron callback; sole listener. This call also SCHEDULES the daily event. | * | 12 | 21 catalogue/customer/order hooks (a subset of row 10's), plus `shutdown` | `Sync\Integrity_Digest` | 10 (`shutdown` at `PHP_INT_MAX`) | unknown | Default. Shares every one of its hooks with `Sync_Journal` at the same priority, so the journal always runs first — no code found that depends on that, but nothing pins it either. Every save — product, variation, customer, order — only MARKS the digest dirty; the upsert lands on `flush_pending_digests()` at `shutdown`, before any `Digest_Index::read_digests()`, or when the queue holds 50 records. | * | 13 | `init` | `Init::init` | 10 | **ORDER-CRITICAL, CROSS-PLUGIN** | Default. **Pro registers its own `init` at 20** (`woocommerce-pos-pro/includes/Init.php:32`) so free's services exist first. Raising free's number silently breaks Pro; nothing on either side tests it. | * | 14 | `rest_api_init` | `Init::init_rest_api` | **20** | **ORDER-CRITICAL, CROSS-PLUGIN** | Free's own reason: unknown — the number dates to the initial commit (8f2b9eac, 2021-03-16). It is load-bearing anyway: **Pro registers `rest_api_init` at 9**, commented "Before the free version" (`woocommerce-pos-pro/includes/Init.php:33`). Untested on both sides. | * | 15 | `query_vars` | `Init::query_vars` | 10 | irrelevant | Default; appends one var. | * | 16 | `pre_update_option_woocommerce_pos_pro_settings_license` | `Init::remove_license_transient` | 10 | irrelevant | Default. The reentrancy guard, not the priority, is what makes it safe (f33b8d655). | * | 17 | ~~`rest_pre_serve_request`~~ | *(removed)* | — | — | Init no longer publishes any part of the REST wire contract. This registration and its handler moved to `Rest_Cors::register_hooks()`, which registers at **20** — after core's `rest_send_cors_headers` at 10 — so WCPOS is the last writer on the lanes it owns. The old `5` had no recorded reason; the new number does. | * | 18 | `send_headers` | `Init::send_headers` | 99 | unknown | Introduced by 62da70551 ("fix WPSEO integration"). The commit records no reason for the number beyond running late. | * | 19 | `send_headers` | `Init::remove_x_frame_options` | **9999** | **ORDER-CRITICAL** | Must run AFTER security plugins have set `X-Frame-Options`, because it works by `header_remove()` (80ee545a5). A smaller number lets the plugin set the header again afterwards. | * | 20 | `determine_current_user` | `Services\Core_Order_Audit_Guard::record_prior_authentication` | **20** | **ORDER-CRITICAL (STATEMENT ORDER)** | See below. | * | 21 | `rest_pre_dispatch` | `Services\Core_Order_Audit_Guard::rest_pre_dispatch` | 10 | irrelevant | Default; reads what row 20 recorded. | * | 22 | `woocommerce_update_coupon` | `Sync\Coupon_Modified_Date::touch` | 10 | irrelevant | Default. `Sync_Journal::record_coupon_updated` shares the hook and priority (row 10) and is registered first, but the journal timestamps rows with the wall clock, not the coupon's `post_modified`, so neither ordering changes an outcome. | * | 23 | `determine_current_user` | `Init::determine_current_user_early` | **20** | **ORDER-CRITICAL (STATEMENT ORDER)** | See below. | * | 24 | `admin_init` | `Services\Lifecycle_Events::flush_pending`, `::maybe_schedule_refresh` | 10 | irrelevant | Default. `admin_init` because both need a fully booted admin request: one sends install/upgrade events recorded before the plugin was loaded enough to send them, the other schedules row 25. Both check consent first and cost nothing on a site that opted out. | * | 25 | `wcpos_analytics_group_refresh` | `Services\Lifecycle_Events::refresh_group_properties` | 10 | irrelevant | Default; sole listener. Unlike row 11, this call does NOT schedule the event — scheduling lives in row 24 so that withdrawing consent unschedules it. | * | 26 | `rest_request_after_callbacks` | `Services\Error_Reporter::filter_rest_request_after_callbacks` | **999** | order-critical (by number) | Runs late so the response status it reports is the one the client receives. | * * ## The one pair where statement order is the whole mechanism * * Rows 20 and 23 share `determine_current_user` AND priority 20, so insertion * order — and nothing else — decides which runs first. 20 puts both after * WordPress core's own handlers, which `default-filters.php` registers before * any plugin loads: `wp_validate_auth_cookie` at 10, then * `wp_validate_logged_in_cookie` and `wp_validate_application_password`, both * at 20 and therefore both ahead of these two. * * The guard must run FIRST. It records into `pre_wcpos_user_id` whichever user * some EARLIER filter had already authenticated; a non-zero value means the * request proved itself with a cookie or application password, so * `Core_Order_Audit_Guard::is_wcpos_jwt_authenticated()` returns false and the * request keeps its normal power over order meta. * * Swap the two statements and the guard records the user WCPOS's own JWT filter * just authenticated. `pre_wcpos_user_id` is then non-zero on every * token-authenticated request, `is_wcpos_jwt_authenticated()` returns false for * all of them, and forged `_pos_*` audit meta on `/wc/v3/orders` is accepted. * It fails OPEN, silently, on a route no smoke test touches. * * Pinned by `tests/includes/Test_Init_Hook_Wiring.php`, which asserts the two * callbacks' ARRAY POSITIONS inside `callbacks[20]` — asserting priorities * would pass on the broken order. */ public function __construct() { // global helper functions. require_once PLUGIN_PATH . 'includes/wcpos-functions.php'; require_once PLUGIN_PATH . 'includes/wcpos-store-functions.php'; wp_cache_add_global_groups( 'wc_pos_user_uuid_locks' ); // Tracking consent pop-up + callout. Registered here (during // plugins_loaded) so its lifecycle hooks (activated_plugin, // upgrader_process_complete) are in place before those actions // fire on a plugin activation or update request. new Consent(); add_filter( 'woocommerce_pos_rest_api_controllers', array( \WCPOS\WooCommercePOS\Sync\Api::class, 'register_controllers' ) ); add_action( \WCPOS\WooCommercePOS\Sync\Integrity_Digest::REBUILD_HOOK, array( \WCPOS\WooCommercePOS\Sync\Integrity_Digest::class, 'run_scheduled_rebuild' ) ); // Gate on the schema latch, not a live Health probe: the latch is only // set AFTER install verified every table (latch-after-verify), so a // per-request SHOW TABLES sweep buys nothing — and a table lost after // latching is already survivable (observer writes fail open and the // REST health gate 503s the sync endpoints). $sync_schema_latched = \WCPOS\WooCommercePOS\Sync\Api::SCHEMA_VERSION === get_option( \WCPOS\WooCommercePOS\Sync\Api::SCHEMA_OPTION, null ); if ( $sync_schema_latched ) { // Normalize structured meta at priority 5, before revision stamps at 9 // and UUID, digest, and variable-price stamps at priority 10. Kept out // of the augmentation pipeline because it also serves the order lane. \WCPOS\WooCommercePOS\Sync\Meta_Normalizer::register_hooks(); add_filter( 'woocommerce_pos_sync_serialized_order', array( \WCPOS\WooCommercePOS\Sync\Pos_Uuid::class, 'stamp_serialized_record' ), 10, 3 ); // ONE seam for both product read lanes: the batch catalog proxy and the // per-object serializer. Every stamper is declared once inside; both // public filter names stay live as projections of it. The order pull // lane's digest stamper is wired there too — it was hand-added here, // under this same latch, which made the pipeline's single-wiring-site // claim untrue. \WCPOS\WooCommercePOS\Sync\Augmentation_Pipeline::install(); } // Identity is core, not an observer benchmark variable: every product is // born with a UUID even before the schema latch is healthy. The before-save // hook writes it in the same save. \WCPOS\WooCommercePOS\Sync\Pos_Uuid::register_hooks(); if ( $sync_schema_latched ) { ( new \WCPOS\WooCommercePOS\Sync\Sync_Journal() )->register_hooks(); $visibility_observer = new \WCPOS\WooCommercePOS\Sync\Visibility_Observer(); $visibility_observer->register_hooks(); $visibility_observer->maybe_seed_hidden_tombstones(); ( new \WCPOS\WooCommercePOS\Sync\Sync_Journal_Purge() )->register_hooks(); ( new \WCPOS\WooCommercePOS\Sync\Integrity_Digest() )->register_hooks(); } ( new \WCPOS\WooCommercePOS\Sync\Config_Fingerprint() )->maybe_cleanup_legacy_options(); // Init hooks. add_action( 'init', array( $this, 'init' ) ); add_action( 'rest_api_init', array( $this, 'init_rest_api' ), 20 ); add_filter( 'query_vars', array( $this, 'query_vars' ) ); // Remove this once Pro settings have been moved to the new settings service. add_filter( 'pre_update_option_woocommerce_pos_pro_settings_license', array( self::class, 'remove_license_transient' ), 10, 2 ); // The REST wire contract — CORS and shared-cache defeat — has a single // owner. Registered unconditionally, from here rather than from the // X-WCPOS-gated API class, because preflights carry no marker and the // relay's consent route is served without constructing API. Rest_Cors::register_hooks(); // Non-REST API discoverability: the HEAD probe against the homepage. add_action( 'send_headers', array( $this, 'send_headers' ), 99, 1 ); add_action( 'send_headers', array( $this, 'remove_x_frame_options' ), 9999, 1 ); /* * Add the global JWT authentication filter and its core-route audit guard. * * Hook order: plugins_loaded -> init (determine_current_user) -> rest_api_init * * This filter runs at priority 20, after WordPress core's cookie auth handlers. * It must be registered here (during plugins_loaded) because determine_current_user * fires during 'init', which is BEFORE rest_api_init where our API class loads. * Because it authenticates WCPOS Bearer tokens on EVERY * REST request (marked or not), the audit-meta guard for core routes * must be registered just as unconditionally — never from the * X-WCPOS-gated API class, whose marker an attacker simply omits. * Registering it first lets its priority-20 provenance filter run after * core's cookie handlers but before WCPOS's JWT filter. */ ( new Services\Core_Order_Audit_Guard() )->register_hooks(); // Coupon post-date touch. Unconditional and lane-agnostic on purpose: a // meta-only coupon edit (amount, discount_type, usage limits) never moves // post_modified, and the client's catalogue replication is date-based // (?modified_after, filtered by WooCommerce on post_modified_gmt), so an // untouched coupon is invisible to every other till. That is true whether // the edit came from the POS, wp-admin, WP-CLI or another plugin — so this // sits outside the schema latch above because it does not use the v2 sync // tables. \WCPOS\WooCommercePOS\Sync\Coupon_Modified_Date::register_hooks(); add_filter( 'determine_current_user', array( $this, 'determine_current_user_early' ), 20 ); // Install lifecycle reporting. Registered last: it adds no filter that // anything else orders against, and appending keeps the ordering table // above in statement order. Deliberately NOT before the pair above — // rows 20 and 23 are decided by insertion order alone. ( new Services\Lifecycle_Events() )->register_hooks(); // Consent-gated Sentry error reporting (issue #1811). Registered last for // the same reason as Lifecycle_Events: nothing orders against it. Its REST // filter runs at 999 so the status it reports is the one the client receives. Services\Error_Reporter::instance()->register_hooks(); } /** * Clear cached data that depends on the Pro license. * * @param mixed $value The new option value. * @param mixed $old_value The previous option value (false when unset). * * @return mixed */ public static function remove_license_transient( $value, $old_value = false ) { // Pro's updater can react to the update_plugins deletion by reading — // and, when the stored instance id is blank, re-saving — the license // option, which re-enters this filter. Without the guard that cycle is // unbounded and OOMs the first license activation on a fresh install. static $clearing = false; if ( $clearing ) { return $value; } $clearing = true; delete_transient( 'woocommerce_pos_pro_license_status' ); // The update caches bind to the license key and activation state. A // write that changes neither — e.g. Pro's read-side instance mint — // must not wipe update_plugins: Pro reacts to that deletion by // clearing its own update-data cache, which empties the payload of an // update check that is in flight when the mint occurs. $old = \is_array( $old_value ) ? $old_value : array(); $new = \is_array( $value ) ? $value : array(); if ( (string) ( $old['key'] ?? '' ) !== (string) ( $new['key'] ?? '' ) || ! empty( $old['activated'] ) !== ! empty( $new['activated'] ) ) { delete_site_transient( 'update_plugins' ); } $clearing = false; return $value; } /** * Early authentication check for JWT tokens. * * This runs BEFORE rest_api_init, so we can authenticate users before WP REST API * permission callbacks run. This is especially important for authorization via * query parameter (?authorization=Bearer...) which some servers require. * * Note: We don't check for X-WCPOS header here because: * 1. The header check uses getallheaders() which may not work in all environments * 2. JWT authentication should work regardless - the token itself is proof of WCPOS usage * 3. Invalid tokens (non-WCPOS) will fail validation anyway * * @param false|int $user_id User ID if one has been determined, false otherwise. * * @return false|int User ID if authenticated, original value otherwise. */ public function determine_current_user_early( $user_id ) { // Skip if user already authenticated. if ( ! empty( $user_id ) ) { return $user_id; } $authenticated_user_id = AuthService::instance()->authenticate_request(); if ( false === $authenticated_user_id || is_wp_error( $authenticated_user_id ) ) { return $user_id; } return $authenticated_user_id; } /** * Load the required resources. */ public function init(): void { $this->init_common(); $this->init_frontend(); $this->init_admin(); $this->init_integrations(); } /** * Loads the POS API and duck punches the WC REST API. */ public function init_rest_api(): void { $is_wcpos_request = woocommerce_pos_request(); if ( $is_wcpos_request ) { if ( ! wcpos_request( 'header' ) && ! wcpos_request( 'query_var' ) ) { // Namespace-detected only: routes still register, but surface // that a proxy/WAF is stripping the X-WCPOS marker. $this->log_unmarked_wcpos_rest_request(); } new API(); } else { // Queue the registration at a later priority of the SAME // rest_api_init pass this method runs on (priority 20), so // register_rest_route() executes during the action as WP requires. // When this method is called outside the action (tests), the // add_action is simply inert. add_action( 'rest_api_init', array( $this, 'register_public_relay_routes' ), 30 ); new WC_API(); } } /** * Register the relay's public consent-callback route for unmarked requests. * * The WCPOS Cloud Print relay proves site consent by fetching * print-jobs/relay-verification WITHOUT the WCPOS request marker, so this * single public route must exist even when the full WCPOS API is not * loaded. Everything else stays behind the marker. */ public function register_public_relay_routes(): void { register_rest_route( SHORT_NAME . '/v1', '/print-jobs/relay-verification', array( 'methods' => 'GET', 'callback' => array( new API\V1\Print_Jobs_Controller(), 'relay_verification' ), 'permission_callback' => '__return_true', ) ); } /** * Log requests for a WCPOS namespace that omitted the request marker. * * Namespace detection registers the routes anyway; this surfaces that a * proxy/WAF is stripping the X-WCPOS marker so misconfigured hosts stay * visible in the logs. Warnings are limited by API version to avoid * allowing repeated unauthenticated requests to flood WooCommerce logs. */ private function log_unmarked_wcpos_rest_request(): void { global $wp; $route = isset( $wp->query_vars['rest_route'] ) ? '/' . ltrim( sanitize_text_field( wp_unslash( (string) $wp->query_vars['rest_route'] ) ), '/' ) : ''; if ( 1 !== preg_match( '#^/wcpos/v([12])(?:/|$)#', $route, $matches ) ) { return; } // The relay's consent callback is expected unmarked traffic (see // register_public_relay_routes()), not a misconfigured client. if ( '/wcpos/v1/print-jobs/relay-verification' === $route ) { return; } $transient = 'wcpos_missing_request_marker_v' . $matches[1]; if ( false !== get_transient( $transient ) ) { return; } set_transient( $transient, 1, 5 * MINUTE_IN_SECONDS ); Logger::warning( $route . ': request marker missing (routes still registered via namespace detection).' ); } /** * Adds 'wcpos' to the query variables allowed before processing. * * Allows (publicly allowed) query vars to be added, removed, or changed prior * to executing the query. Needed to allow custom rewrite rules using your own arguments * to work, or any other custom query variables you want to be publicly available. * * @param string[] $query_vars The array of allowed query variable names. * * @return string[] The array of allowed query variable names. */ public function query_vars( array $query_vars ): array { $query_vars[] = SHORT_NAME; return $query_vars; } /** * Allow HEAD checks for WP API Link URL and server uptime. * * This is the NON-REST lane and is not part of the REST wire contract * ({@see Rest_Cors}): `send_headers` fires from `WP::main()`, which a REST * request never reaches — core's `rest_api_loaded()` runs on * `parse_request` and dies. What it serves is the app's site-discovery * probe against an ordinary page: the app reads the `Link: * <.../wp-json/>; rel="https://api.w.org/"` header cross-origin to find * the REST root, which needs both headers below. Some servers turn HEAD * into GET, hence the `?_method=head` query param rather than the method. * * This is live, not legacy. The client calls it on every Connect: * `packages/core/src/screens/auth/hooks/use-url-discovery.ts` issues * `http.head()` against the site root, and * `packages/hooks/src/use-http-client/use-http-client.tsx` sets * `params._method = 'HEAD'` on every HEAD request (both in the client * monorepo). That same client code deliberately omits the `X-WCPOS` * marker for HEAD, so this handler cannot be marker-gated and must stay * unconditional. 521ccb9a added it; the `?wcpos=1` gate it originally * carried is long gone. * * @return void */ public function send_headers(): void { // some server convert HEAD to GET method, so use this query param instead. if ( isset( $_GET['_method'] ) && 'head' === strtolower( sanitize_text_field( wp_unslash( $_GET['_method'] ) ) ) ) { header( 'Access-Control-Allow-Origin: *' ); header( 'Access-Control-Expose-Headers: Link' ); } } /** * Some security plugins will set X-Frame-Options: SAMEORIGIN/DENY, which will prevent the POS desktop * application from opening pages like the login in an iframe. * * For pages we need, we will remove the X-Frame-Options header. * * @param mixed $wp The WP object. * * @return void */ public function remove_x_frame_options( $wp ): void { if ( woocommerce_pos_request() || isset( $wp->query_vars['wcpos-login'] ) ) { if ( ! headers_sent() && \function_exists( 'header_remove' ) ) { header_remove( 'X-Frame-Options' ); } } } /** * Groups constructed so far in this request (test seam; see constructed_groups()). * * @var array */ private static array $constructed = array(); /** * Common initializations, by request lane. * * Every request gets the services whose hooks WooCommerce consults on a * plain shopper page BEFORE any order exists: translations, the product * visibility filters, the order statuses and the read-side order filters * (My Account renders POS orders), the gateway registration (WooCommerce * builds its gateway list on cart pages) and the reserved-stock filter * (POS drafts must reduce online availability at add-to-cart time). * * Everything else is constructed only on the lanes that use it, and the * order-event services additionally on the first order write of ANY request * ({@see ensure_order_services()}), so the lane classifier is an * optimisation rather than a correctness gate. Measured 2026-09-03: a * storefront page loaded ~80 plugin files and 22 objects for hooks that * never fire there (see .claude/research/2026-09-03-lazy-service-construction-spec.md). */ private function init_common(): void { self::$constructed['always'] = true; // init the Services. SettingsService::instance(); AuthService::instance(); // Needed on every lane, including a plain storefront page. new i18n(); new Gateways(); new Products(); new Orders(); Services\Stock_Validator::instance(); if ( Services\Request_Lane::is_storefront() ) { // Order-event services arrive on the first order write, if any. self::arm_order_services(); return; } self::ensure_order_services(); self::construct_pos_services(); } /** * Services only POS, admin, REST, cron and CLI requests use. */ private static function construct_pos_services(): void { if ( isset( self::$constructed['pos'] ) ) { return; } self::$constructed['pos'] = true; Extensions::instance(); new Services\Decimal_Quantities(); new Services\Customer_Meta_Parity(); } /** * Hook the order-event services to the first order write of the request. * * Every WooCommerce order write — create, update, status transition, * `payment_complete()`, refund — goes through `WC_Abstract_Order::save()`, * which fires `woocommerce_before_order_object_save` before the data store * writes and before `woocommerce_new_order` / `woocommerce_order_status_changed` * / `woocommerce_payment_complete` fire. Priority 0 there means every * observer exists before any order is written — on a webhook, a cron * spawned from a page view, a third-party plugin creating an order on * `template_redirect`, or a lane the classifier got wrong. Nothing in the * order group listens to trash or delete, so those need no arming. */ private static function arm_order_services(): void { add_action( 'woocommerce_before_order_object_save', array( self::class, 'ensure_order_services' ), 0, 0 ); } /** * Construct the order-event services exactly once per request. * * Idempotent and safe to call after `init`; each service handles its own * late registration. Fires `woocommerce_pos_order_services_ready` once so * Pro and extensions can construct their own order-event services at the * same moment on every lane. */ public static function ensure_order_services(): void { if ( isset( self::$constructed['order'] ) ) { return; } self::$constructed['order'] = true; Receipt_Snapshot_Store::instance(); new Emails(); new Templates(); new Services\Print_Job_Service(); new Services\Cloud_Print_Trigger_Service(); new Services\Cloud_Print_Submit_Service(); new Services\Cloud_Print_Relay_Service(); /** * Fires once per request when the POS order-event services exist: * eagerly on POS, admin, REST, cron and CLI requests (from this * plugin's `init` callback at priority 10), and on a storefront * request the moment the first order is about to be written. * * Because the eager firing happens at `init` priority 10, a listener * added later than that (for example from another plugin's `init` * callback at priority 20) must check `did_action()` first and * construct immediately when the action has already fired. * * @since 1.10.8 */ do_action( 'woocommerce_pos_order_services_ready' ); } /** * Which service groups this request has constructed: 'always', 'order', 'pos'. * * @internal Test seam. * * @return string[] */ public static function constructed_groups(): array { return array_keys( self::$constructed ); } /** * Forget which groups were constructed. Tests only. * * @internal */ public static function reset_request_state(): void { self::$constructed = array(); Services\Request_Lane::reset(); } /** * Frontend specific initializations. */ private function init_frontend(): void { if ( is_admin() ) { return; } // The public receipt shortcode and the My Account receipt action are // storefront features; they construct the template services when used. new Storefront_Receipts(); if ( ! Services\Request_Lane::is_storefront() ) { // The POS routes (rewrite rules, checkout context, order-pay and // coupon forms) only matter on requests the classifier saw as POS. new Template_Router(); new Form_Handler(); } } /** * Admin specific initializations. */ private function init_admin(): void { if ( is_admin() ) { // Register AJAX handler before the branch so it's available during AJAX requests. add_action( 'wp_ajax_wcpos_track_upgrade_click_ajax', array( Menu::class, 'handle_upgrade_click_ajax' ) ); add_action( 'admin_post_wcpos_track_upgrade_click', array( Menu::class, 'handle_upgrade_click_redirect' ) ); if ( wp_doing_ajax() ) { new AJAX(); } else { new Admin(); } } } /** * Integrations. */ private function init_integrations(): void { // WooCommerce Bookings - http://www.woothemes.com/products/woocommerce-bookings/ // if ( class_exists( 'WC-Bookings' ) ) { // new Integrations\Bookings(); // }. // Yoast SEO - https://wordpress.org/plugins/wordpress-seo/. if ( class_exists( 'WPSEO_Options' ) ) { new Integrations\WPSEO(); } // wePOS alters the WooCommerce REST API, breaking the expected schema // It's very bad form on their part, but we need to work around it. // Its only hook is admin_init (a conflict notice), so admin lane only. if ( is_admin() ) { new Integrations\WePOS(); } // WooCommerce Tax - https://wordpress.org/plugins/woocommerce-services/ // Its class exists whenever the plugin is active, but its callbacks are // only hooked when automated taxes are on and the store country is // supported, so the integration looks them up on the hooks at // recalculation time instead of gating on the class here. new Integrations\WooCommerce_Tax(); } }