Skip to content

Third-Party Integrations

Orbit provides sensible performance defaults, security rate-limiting, and cleanup routines for popular third-party WordPress plugins.

WooCommerce Integrations

When WooCommerce is active, Orbit enforces privacy and performance safeguards:

Disabled Telemetry & Pattern Loading

Orbit forces option_woocommerce_allow_tracking to return false. This disables background WooCommerce usage tracking and stops WooCommerce from downloading external pattern templates from Pattern Directory endpoints.

Store API Rate Limiting

Orbit applies rate limiting to WooCommerce Store API checkout endpoints to protect against automated carding and checkout abuse:

  • Max Requests: 20 requests
  • Time Window: 60 seconds
  • Proxy Support: Enabled (properly respects reverse proxy headers such as Cloudflare or Nginx)

External WooCommerce Pattern Removal

Orbit filters out WooCommerce block patterns from both the PHP pattern registry and REST API responses (/wp/v2/block-patterns/patterns).

If you wish to keep default WooCommerce block patterns enabled:

php
add_filter( 'orbit_enable_disable_external_patterns', '__return_false' );

Action Scheduler Optimisations

Orbit tunes WooCommerce and Action Scheduler background job cleanup behaviour to prevent the wp_actionscheduler_actions database table from growing excessively large:

  • Retention Period: Retains completed/failed actions for 2 weeks (WEEK_IN_SECONDS * 2).
  • Cleaned Statuses: Automatically purges complete, canceled, and failed jobs.
  • Batch Cleanup Size: Purges in batches of 1000 records per run.

Action Scheduler Filter Hooks

php
// Change retention period to 7 days
add_filter( 'orbit_action_scheduler_retention_period', fn() => WEEK_IN_SECONDS );

// Customise cleanup statuses
add_filter( 'orbit_action_scheduler_default_cleaner_statuses', function( array $statuses ) {
    return [ 'complete', 'canceled' ]; // Exclude failed jobs
} );

// Change cleanup batch size
add_filter( 'orbit_action_scheduler_cleanup_batch_size', fn() => 500 );

Altcha CAPTCHA Cache-Busting

When using the Altcha spam-protection plugin, challenge URLs can sometimes be cached by reverse proxies (Varnish, Nginx) or CDN edge networks (Cloudflare), causing valid challenge tokens to expire or fail.

Orbit automatically appends a dynamic, uncacheable query string parameter (?r=1234) to Altcha challenge endpoints (altcha_challenge_url), ensuring that every visitor receives a unique cryptographic challenge.