內容簡介
Creatools Maintenance Check 外掛幫助使用者在進行 WordPress 更新前，組織和檢查相關資訊，確保維護過程的安全性與兼容性，並提供詳細的更新建議。
【主要功能】
• 檢查 WordPress 核心、佈景主題和外掛的更新資訊
• 獲取已安裝版本與可更新版本的詳細資料
• 提供已知漏洞的摘要與維護報告
外掛標籤
開發者團隊
原文外掛簡介
Creatools Maintenance Check organizes research before you press an update button. It reads existing WordPress core, theme and plugin update information and explains what to check before deciding on maintenance.
Review installed versions and native update candidates separately.
Check declared WordPress and PHP requirements, Tested up to and available dependency information.
Optionally retrieve WordPress.org directory metadata and WPVulnerability known vulnerability records.
Read priority, hold, review and update-candidate reasons separately from information completeness.
Review human-readable vulnerability summaries and copy a maintenance report.
Use automatic environment information or a manual PHP assessment value.
Use the administration screens in English or Japanese.
This plugin does not perform updates, enable automatic updates, back up or restore your site. Results do not guarantee safety, compatibility or a successful update. The final maintenance decision remains yours.
Coverage includes inactive plugins and unused themes. MU plugins and drop-ins are outside the research scope. Premium and private products may have limited information; directory identity and update source are separate. A directory-name candidate alone is not treated as a verified identity. Multisite research is disabled with an explanatory message; native WordPress updates remain available.
Native metadata can inform requirement checks, but WordPress Core’s last_checked is not proof of successful retrieval or freshness. Missing information, service failures and expired data are not treated as evidence of no problems. Database information is informational. PHP 7.4 compatibility helps research on older environments and is not a recommendation to run unsupported PHP.
External services
Both services are OFF by default. Requests start only after you enable the relevant service and explicitly start research. Valid caches can avoid requests. Disabling a service stops subsequent requests; retained findings can still be shown with their original dates. The services do not receive your manual PHP value or database information.
WordPress.org
Purpose: directory identity verification, declared requirements, Tested up to, publication status, release dates and changelog references for plugins and themes.
Endpoints: https://api.wordpress.org/plugins/info/1.2/ and https://api.wordpress.org/themes/info/1.2/
Sent: product slug (including eligible identity-verification candidates), information action, en_US locale, requested API fields, and the fixed Creatools-Maintenance-Check User-Agent with plugin version. Product headers and installed/target versions are compared locally.
API documentation: https://codex.wordpress.org/WordPress.org_API
Project license: https://wordpress.org/about/license/
Privacy policy: https://wordpress.org/about/privacy/
These are the provider’s published API, project license and privacy references; the project license is not a separate API service-use agreement.
WPVulnerability
Purpose: known vulnerabilities for installed and target versions, with source references and available severity/exploitation information.
Endpoints: https://www.wpvulnerability.net/core/{version}/, https://www.wpvulnerability.net/plugin/{slug}/ and https://www.wpvulnerability.net/theme/{slug}/
Sent: WordPress core version in a core request, or verified directory slug in a plugin/theme request, and the fixed Creatools-Maintenance-Check User-Agent with plugin version. Plugin/theme version-range matching takes place locally. No API key is required by this integration.
API documentation: https://docs.wpvulnerability.com/
License / provider conditions: https://www.wpvulnerability.com/license/
Privacy policy: https://www.wpvulnerability.com/privacy/
Fair use / sponsorship: https://www.wpvulnerability.com/sponsorship/
For both providers, the connection IP is visible. No site content, site URL, user data, passwords, credentials or database contents are included in these research requests. Retrieved strings are treated as data, not executable code. There are no remote scripts, CDN assets or telemetry in this plugin.
