| 开发者 | ecapla |
|---|---|
| 更新时间 | 2026年8月17日 20:47 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[certloom] in the Classic Editor, a Shortcode block, templates, or other page builders.?certloom_number=YOUR-NUMBER for QR-code destinations. These requests receive noindex and private-cache headers, although the number may still appear in browser history, infrastructure logs, or site analytics.manage_certverify capability and optional Certificate Manager role.certloom folder to /wp-content/plugins/.Yes. The native block, shortcode, administration, REST verification, CSV tools, direct links, roles, and status handling work independently.
Expiry is calculated from the expiry date during normal administration and CSV workflows. Extending the date renews the certificate unless it is Suspended or Withdrawn. Restored historical Expired records remain protected until reviewed.
No. Unmapped values are preserved. Blank mapped cells on existing records are also preserved unless clearing is explicitly enabled. Status cannot be cleared.
CSV is intended for spreadsheet interchange. Complete backup is a versioned streaming JSON format for lossless restoration, including settings, field definitions, retired values, workflow sources, and timestamps.
Yes. The form can submit a normal GET request and render the result on the server. JavaScript provides the faster in-page experience.
No. Records stay in the site's WordPress database and verification is performed by that site.
Not by default. Enable permanent data removal in Certloom > Access & Settings before deleting the plugin only when that is intended.
After publication, use the Support tab on the WordPress.org plugin page. Include the WordPress, PHP, and Certloom versions, clear reproduction steps, and relevant error text. Never post private certificate data, backup files, credentials, or personal information in a public topic.
certloom.changelog.txt included with the plugin.