Advanced Database Cleaner – Optimize & Clean Database to Speed Up Site Performance vs FlxWoo

Advanced Database Cleaner is a complete WordPress optimization plugin that helps you clean up database clutter and optimize database performance by removing unused data such as old revisions, auto drafts, spam comments, expired transients, unused post meta, duplicated post meta, unused user meta, etc. It is designed to help you improve website speed by reducing database bloat and ensuring a lean, efficient WordPress installation. It also provides detailed previews, powerful filters, and automation tools to safely control what gets cleaned. With the ✨Premium version✨, you can unlock even more advanced features, such as detecting and cleaning orphaned options, orphaned tables, orphaned post meta, orphaned user meta, orphaned transients, and orphaned cron jobs. It also gives you clear insights into how your database evolves over time through built-in analytics, lets you monitor plugin and theme activity to better understand when new data is created or when leftovers appear, and much more. Why use Advanced Database Cleaner❓ 👉 Get a clear overview: see how many tables, options, transients, cron jobs, metadata… records you have, and identify which are unused or orphaned. 👉 Save time: configure what to clean, how far back to keep data, and how often to run automations. The plugin will then handle recurring cleanups for you. 👉 Save space and improve performance: removing unnecessary data reduces database size, makes backups faster, and can improve query performance, especially on busy or older sites. ✅ Main Features Delete old revisions of posts and pages Delete old auto-drafts Delete trashed posts Delete pending comments Delete spam comments Delete trashed comments Delete pingbacks Delete trackbacks Delete unused post meta Delete unused comment meta Delete unused user meta Delete unused term meta Delete unused relationships Delete expired transients Delete duplicated post meta Delete duplicated user meta Delete duplicated comment meta Delete duplicated term meta Delete oEmbed caches Display the database size that will be freed before cleaning for each item type, and the total size to be freed Display and preview items to clean before performing a database cleanup to ensure safety Sorting capability in cleanup preview tables (by name, date, size, site id, etc.) View options value content in original or formatted mode for serialized or JSON structures (and other items types as well). Keep last X days of data: clean only data older than the number of days you specify ✅ Automation Schedule database cleanup to run automatically Create scheduled cleanup tasks and specify which items each task should clean Schedule database optimization and/or repair to run automatically Execute scheduled tasks based on several frequencies: once, hourly, twice a day, daily, weekly, or monthly Specify the “keep last X days” rule for each item type in a scheduled task Pause/Resume scheduled tasks whenever needed Create as many scheduled cleanup tasks as needed and specify what each task should clean ✅ Tables Display the list of database tables with information such as number of rows, table size, engine, etc. Sort tables by any column such as table name or table size Display table contents along with their column structure, indexes, status, and more Detect and filter tables with invalid prefixes (tables that do not belong to the current WordPress installation), this can be enabled or disabled from the settings page Optimize database tables (the plugin notifies you when tables require optimization) Repair corrupted or damaged database tables (the plugin notifies you when tables are corrupted) Convert tables to InnoDB for better performance Empty rows of database tables Clean and delete database tables ✅ Options Display the options list with information such as option name, option value, option size, and autoload status Sort options by any column such as option name or option size View option value content in original or formatted mode for serialized or JSON structures. Notify you if autoloaded options are large and help reduce autoload size for better performance Detect large options that may slow down your website Set option autoload to yes/no Clean and delete options ✅ Cron Jobs Display the list of active cron jobs (scheduled tasks) with information such as arguments, action, next run, schedule, etc. Sort cron jobs by any column such as action name or next run time Detect cron jobs with no valid actions Clean and delete scheduled tasks ✅ Post Meta Display the post meta list with information such as meta key, value, size, associated post ID, etc. Sort post meta by any column such as meta key, meta size, or post ID View post meta value content in original or formatted mode for serialized or JSON structures. Detect unused post meta (meta not associated with any existing posts) Detect duplicated post meta (same meta key/value for the same post ID) Clean and delete post meta ✅ Post types Display post types with information such as name, post count, visibility (public or non-public), etc. Sort post types by columns such as name, post count, visibility, etc. View posts corresponding to each post type, along with their details Detect unused or orphaned post types Clean orphaned post types ✅ User Meta Display the user meta list with information such as meta key, value, size, associated user ID, etc. Sort user meta by any column such as meta key, meta size, or user ID View user meta value content in original or formatted mode for serialized or JSON structures. Detect unused user meta (meta not associated with any existing users) Detect duplicated user meta (same meta key/value for the same user ID) Clean and delete user meta ✅ Transients Display the list of transients with information such as name, value, size, and expiration time Sort transients by any column such as transient name, size, or expiration time View transient value content in original or formatted mode for serialized or JSON structures. Clean expired transients Detect large transients that may slow down your website Clean and delete transients Set transient autoload to yes/no ✅ WooCommerce Clean orphaned product variations Clean orphaned customer analytics Clean expired customer sessions ✅ Other Tools Display current database size Logging system for easy troubleshooting Access the WordPress debug log directly from the plugin interface Multisite support (network-wide database cleanup and optimization from the main site) Modern, responsive interface powered by React for a smooth experience without page reloads Show/hide plugin tabs for better usability ⚡ Premium Features ⚡ Official website Unlock the full power of database cleanup and optimization with Advanced Database Cleaner Premium – packed with smart features that take accuracy, speed, and cleanup control to the next level. ✅ Remote SmartScan Local scan + Remote SmartScan technology to accurately detect the true owners of tables, options, post meta, user meta, transients, and cron jobs Cloud-enhanced ownership detection using a large and continuously improving remote database Improved accuracy for identifying orphaned items left by deleted plugins and themes Ability to edit ownership of any item and correct misidentified owners Ability to send ownership corrections to improve the global detection database Enhanced “Belongs to” ownership column everywhere using cloud data + local data Display multiple possible owners for each item when applicable Display owner status (active, inactive, not installed) to simplify cleanup decisions Check your remote scan credits to monitor usage ✅ Action Scheduler Cleanup Clean Action Scheduler Completed actions Clean Action Scheduler Failed actions Clean Action Scheduler Canceled actions Clean Action Scheduler Completed logs Clean Action Scheduler Failed logs Clean Action Scheduler Canceled logs Clean Action Scheduler Orphan logs ✅ General Cleanup Enhancements Keep last X items feature in General Cleanup Keep last X items per parent (e.g., per post) Keep last X items globally (e.g., keep the last 10 pingbacks) Combine Keep Last X Days with Keep Last X Items for advanced cleanup safety ✅ Advanced Filters Advanced filters in all modules (Tables, Options, Post Meta, User Meta, Transients, Cron Jobs) Filter by size, value content, autoload, expiration, metadata type, and more Filter by plugin owner, theme owner, WordPress core, orphan, or unknown Filter by multisite site ID with full per-site visibility Filter by action frequency and interval in cron jobs Filter by duplicated, unused, large, not-yet-scanned, or expired items ✅ Advanced Automation Unlimited automation tasks (Free version is limited to 5 tasks) Create any number of scheduled cleanup tasks with different configurations Create scheduled optimization and repair tasks Use Keep Last X Items and Keep Last X Days inside scheduled tasks Run automation tasks hourly, twice daily, daily, weekly, monthly, or at any supported frequency Pause/resume/delete automation tasks without losing settings Per-task automation event logging showing executed actions, number of items cleaned, execution timestamps, and detailed logs ✅ Database Analytics Daily tracking of total database size and number of tables Daily and monthly charts showing database growth trends Raw data tab with all recorded measurements Table-level analytics showing size growth, rows growth, and daily changes Ability to detect abnormal table growth caused by logs, caches, or runaway actions Multi-table selection and search for analyzing multiple tables at once ✅ Addons Activity Automatically track plugin activations, deactivations, and uninstalls Automatically track theme switches and uninstalls Display activity in a color-coded timeline for better readability All timestamps shown in your local timezone Multisite support (activity recorded on the main site) ✅ Full Multisite Support Clean any site or all sites Filter items by site ID in every module (Tables, Options, Post Meta, User Meta, Transients, Cron Jobs) Display which site each item belongs to Run automation tasks across the entire network 🛒 WOptimize – The Cleaner & Optimizer for WooCommerce If you run a WooCommerce store and want to go further, try our dedicated plugin WOptimize – the ultimate solution to clean and speed up your WooCommerce store. Learn more: https://sigmaplugin.com/downloads/woptimize

FlxWoo is a WooCommerce infrastructure plugin. It adds a REST API layer, server-side checkout rendering, and Stripe Checkout integration on top of standard WooCommerce — without replacing WooCommerce’s core order, payment, or inventory systems. It is designed for agencies and developers who need full control over checkout presentation while continuing to rely on WooCommerce for order management, tax calculation, coupon handling, and payment record-keeping. What FlxWoo Is A REST API layer for WooCommerce checkout state (namespace: flxwoo/v1) A server-side rendering layer for checkout and product page templates A Stripe Checkout integration with server-side session management and webhook handling A fallback-safe product page rendering layer: falls back to native WordPress/WooCommerce templates when the Render service is unavailable or the product type is not supported An admin dashboard for operational monitoring: Overview, Settings, and System Status pages An infrastructure layer that extends WooCommerce without replacing it What FlxWoo Is Not Not a WooCommerce fork or replacement Not a page builder or visual checkout designer Not a payment processor — payment remains in WooCommerce and Stripe Not a headless CMS Not a replacement for WooCommerce’s admin, order management, or product system Who FlxWoo Is For Agencies building custom checkout experiences on WooCommerce Developers who need REST access to WooCommerce checkout state Projects requiring server-side rendered checkout templates Teams integrating Stripe Checkout while keeping WooCommerce as the order system Architecture FlxWoo registers a REST namespace (flxwoo/v1). Checkout state endpoints (cart, order, coupon, customer) return JSON. Render endpoints (/render/checkout, /render/thank-you) return server-side rendered HTML. Product pages are intercepted at the template layer and rendered through the external Render service, with automatic fallback to native WordPress/WooCommerce templates if the service is unavailable or the product type is not supported. WooCommerce remains authoritative for all order, cart, tax, and payment data. FlxWoo reads and writes through WooCommerce’s standard APIs without modifying its data structures or core behavior. Features REST API under the flxwoo/v1 namespace Cart and checkout state endpoints returning JSON Stripe Checkout integration — server-side session creation and webhook handling Duplicate order prevention at the checkout session level Concurrent submission guard Session-independent Stripe return flow (order identity carried via URL, not session state) Server-side HTML rendering for checkout and thank-you templates Product page rendering via external Render service, with automatic fallback to native WordPress/WooCommerce templates Product type gate: only simple products (including virtual) are routed to the Render service; variable, external, and unrecognized types use native templates Structured logging for checkout and payment events Operational event store tracking webhook failures, Stripe connectivity issues, and auth denials Health endpoint at GET /wp-json/flxwoo/v1/health for uptime monitoring Admin Overview page with operational health summary and last-payment/last-webhook signals System Status page with diagnostics across environment, Stripe, cache, webhooks, checkout failures, and database Automated data retention: scheduled cleanup for idempotency records, Stripe events, checkout sessions, and operational events with defined retention windows Preserve-by-default uninstall policy: data is retained unless explicitly opted out in Settings Cache and CDN Configuration FlxWoo endpoints are session-sensitive and stateful. They must not be served from a cache layer under any circumstances. Why This Matters FlxWoo checkout endpoints read and write live session, cart, and payment state on every request. If a caching layer returns a stale or shared response, the result is incorrect behavior — not a gracefully degraded experience. Common symptoms include stale cart totals, duplicate checkout attempts, broken Stripe sessions, and session data surfacing to the wrong customer. Any FlxWoo endpoint returning a cache HIT response header is a production defect. What Must Bypass Cache Three route groups must bypass cache at every layer — page cache, CDN, reverse proxy, and any optimization plugin that operates on HTTP responses: /wp-json/flxwoo/* — all FlxWoo REST API endpoints (cart, checkout, payment, webhook, health) /checkout* — the WordPress checkout page and all trailing-slash or query-string variants /thank-you* — the order confirmation page and all variants FlxWoo emits Cache-Control: no-store headers via PHP on both the REST API and the HTML pages. However, CDN-level rules such as Cloudflare’s “Cache Everything” can override PHP headers at the edge before they reach the browser. PHP-level headers alone are not sufficient — explicit CDN bypass rules targeting these paths are required. Common Systems That Require Configuration WP Rocket — Add /wp-json/flxwoo/, /checkout, and /thank-you to “Never Cache URL(s)” in the Cache settings tab. WP Rocket uses substring prefix matching, so these entries cover /checkout* and /thank-you* including trailing-slash and query-string variants. LiteSpeed Cache — Add /wp-json/flxwoo/, /checkout, and /thank-you to the “Do Not Cache URIs” list under Cache > Excludes. LiteSpeed URI exclusions also use prefix matching, covering /checkout* and /thank-you*. Cloudflare — Use Cache Rules to bypass cache for paths matching /checkout*, /thank-you*, and /wp-json/flxwoo/*. If using Automatic Platform Optimization (APO), verify that checkout and thank-you URLs are in the APO exclusion list. Cloudflare’s “Cache Everything” page rule must not apply to these paths. Nginx / FastCGI — Add fastcgi_cache_bypass map entries for /wp-json/flxwoo/, /checkout*, and /thank-you* at the server or location block level. Varnish — Add pass conditions in vcl_recv for /wp-json/flxwoo/*, /checkout*, and /thank-you*. Aggressive optimization plugins — Verify that no plugin is buffering, combining, or caching REST API responses or HTML responses for FlxWoo routes or page wrappers. What Is Safe to Cache Static assets (CSS, JS, images), non-dynamic pages, and REST endpoints that explicitly return Cache-Control: public. FlxWoo’s own endpoints never set public cache headers. Full Configuration Reference Detailed per-system instructions, verification commands, and symptom diagnostics are in docs/cache-configuration.md. Requirements WordPress 6.0 or later PHP 8.0 or later WooCommerce (active; declared as a required plugin) Stripe account with Checkout enabled (for payment features) MySQL 5.7+ or MariaDB 10.3+ Operational Notes Health endpoint: GET /wp-json/flxwoo/v1/health always returns HTTP 200 when the plugin is active. Suitable for uptime monitoring and deployment verification. Logging: Structured logging for checkout and payment events. Useful for incident response and debugging in production environments. Database setup: Required tables are created automatically on activation. Schema migrations run silently on upgrade — no manual steps required. Data on uninstall: Data is preserved by default when the plugin is deleted. To remove all FlxWoo data, enable Delete all data on uninstall in FlxWoo Settings > Data before deleting the plugin. Idempotency: Checkout idempotency is database-backed, making the system safe for concurrent requests and browser retries. Stripe return flow: Order identity is carried via URL parameters after Stripe redirect, not session state. This makes the return path resilient to session loss between payment and confirmation. Security All REST endpoints enforce WordPress capability checks before processing requests. Input is validated and sanitized at the API boundary and within the service layer. All PHP files include an ABSPATH guard to prevent direct execution. Database queries use prepared statements throughout. PHP CodeSniffer with WordPress Coding Standards and security sniffs is enforced as a release gate. Limitations Requires WooCommerce to be active. FlxWoo will not initialize without it. Stripe integration requires an active Stripe account with Checkout enabled. Server-side rendering requires a live PHP execution environment. Fully static deployments are not supported. All FlxWoo REST endpoints must not be behind a full-page or CDN cache layer. Product page rendering via the Render service is currently limited to simple products (including virtual). Variable, external, and other product types fall back to native WordPress/WooCommerce templates.