WordPress
PlannedPlanned — not available yet. No WordPress connector exists today. This page describes the intended design, and details may change before anything ships.
See every WordPress site you are responsible for, version by version.
The WordPress connector is intended to give one inventory across many WordPress installations: which core version each site runs, which plugins and themes are installed and at what version, and which PHP version the site reports. It is meant for teams that look after more sites than they can log in to one by one.
Planned capabilities
- Core, plugin and theme inventory with installed versions
- PHP and database server versions as reported by each site
- Active and inactive plugins listed separately
- Last-seen time per site, so a site that stopped reporting is visible
How it will work
The planned model is a small companion plugin that the site administrator installs and then authorizes against a TSmartConnect workspace. The plugin reports inventory outward on a schedule. TSmartConnect does not log in to the site, and the plugin is not intended to change site configuration.
Security and permissions
No WordPress administrator password is ever requested or stored. Authorization is a per-site token that the administrator can revoke from the plugin or the workspace, and removing the plugin ends reporting. The reported data is inventory metadata, not content, users or orders.
Use cases
Agency site portfolio
An agency that maintains forty client sites sees which ones still run a plugin version it has decided to retire, without opening forty dashboards.
PHP upgrade planning
Before a host retires a PHP version, the sites still reporting it are listed in one place.
Evidence for a security review
Plugin and theme versions become structured evidence that a separate assessment service can evaluate.
Questions
- Is the WordPress connector available today?
- No. It is planned and no plugin has been released. Nothing on this page is running yet.
- Will it need my WordPress admin password?
- No. The intended design uses a revocable per-site token issued when the plugin is authorized. Passwords are never requested.
- Will it update plugins automatically?
- That is not part of the planned scope. The connector is designed to report what is installed, not to change it.
- Does it cover WooCommerce?
- WooCommerce is listed as its own planned connector. Store data would be a separate, explicitly authorized scope.
Interested in WordPress?
Connector order follows what customers actually run. Tell us what you would connect and how many sites, accounts or repositories are involved.