Versions, dependencies, licenses, and risk
Check the upstream, minimum versions, known conflicts, premium requirements, abandoned packages, and dangerous update combinations before installation.
Compatibility Lab
Compatibility is a versioned test result—not a logo wall.
WPbyAI separates broad preflight from browser testing and C-level verification. Every public compatibility result names the plugin, version, WordPress/PHP/database/theme/editor stack, tested flow, date, warnings, and untested areas.
Listed does not mean tested. Preflighted does not mean C-verified. Every public status must preserve that distinction.
Install and edit in a browser environment
Verify that the plugin can be installed and the target editor or customer flow can be exercised in the stated test environment.
Run the critical flow in the locked stack
Test the agreed customer path against a stated WordPress/PHP/database/theme/plugin combination and record PASS, warnings, blocked steps, and exclusions.
What happens next
A visible path, with a stop at every meaningful decision.
- 01
Submit the stack
List WordPress, PHP, theme, editor, plugin names and versions, host constraints, premium licenses, and the critical flow.
- 02
Preflight the combination
Check upstream requirements, version ranges, conflicts, abandoned dependencies, security signals, and external-account needs.
- 03
Run the agreed test
Install only in an isolated environment and exercise the exact admin and public flows that matter to the project.
- 04
Publish a scoped result
Record environment, date, status, evidence, warnings, untested areas, retest triggers, and the next safe action.
Included in this route
- Status language from DISCOVERED through VERIFIED_PROFILE
- Exact versions and stated environment for each result
- Known limitations, licenses, external accounts, and retest triggers
- A distinction between upstream claims and WPbyAI testing
- A path from one-off project evidence to a reusable compatibility profile
Not assumed or promised
- A guarantee for every version, configuration, host, theme, and neighboring plugin
- Automatic licensing or redistribution of premium code
- Testing unknown packages directly against production
- Calling every WordPress.org directory plugin an official WordPress-developed plugin
Limited private pilot
Tell us the stack and the flow that must not break.
Plugin names alone are not enough. Include versions, editor, host or PHP constraints, and the customer action that needs evidence.