| 开发者 |
edutainmentuk
freemius |
|---|---|
| 更新时间 | 2026年9月13日 20:45 |
| PHP版本: | 7.2 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
https://checkout.freemius.com/js/v1/ on the plugin's Dashboard, Data Management, Upgrade, and Freemius Account screens, where purchasing controls may appear. As with any remote request, this can send your IP address, browser user-agent, and the referring admin page URL. Opening Checkout also sends the selected product, plan, license quantity, and billing cycle. Any contact, billing, and payment details you enter during Checkout are handled by Freemius and its payment providers.
When an administrator connects a Freemius account, activates or manages a license, checks for premium updates, or opts into data sharing, the bundled Freemius SDK may send: your site URL and title; WordPress, PHP, and SDK versions; site language and multisite context; the plugin version and its active, deactivated, or uninstalled state; the administrator's name and email address; Freemius account, site, install, product, plan, and license identifiers, including a submitted license key; and, only if you enable that optional permission, a list of installed plugin and theme names and versions.
Freemius permissions are shown to you inside WordPress, and optional diagnostic sharing can be turned off there. Some communication is required to activate and validate a Pro license.
Certificate data is never sent to Freemius. Learner names, email addresses, course names, issue dates, authentication codes, custom fields, and verification analytics stay in your own WordPress database.
Freemius terms of service: https://freemius.com/terms/
Freemius privacy policy: https://freemius.com/privacy/
If you configure a certificate logo using an external image URL instead of the WordPress Media Library, your site downloads that image while generating a PDF, and the image host may receive your server's IP address and standard request headers. No certificate data is included in that request.
Usage
[edcv_validator] to any page or post.edutain-certificate-validator folder to /wp-content/plugins/.[edcv_validator] on your preferred page.No. CSV upload, individual record management, CSV and XLSX export, unlimited stored records, and the public certificate verification form are all available without Pro. A single CSV upload is limited to 10 MB and 100,000 data rows for safe processing. That is a limit on one import operation, not on how many records you can store.
The required columns are Name, Issue Date (or Completion Date), and Authentication Code. Columns can be in any order, and header matching is not case-sensitive. Email is optional.
Completion Date and the Pro Expiry Date column accept dd/mm/yyyy or yyyy-mm-dd. Invalid calendar dates are skipped and reported back to you.
Yes. Each upload is merged into your existing dataset. Authentication codes that already exist are skipped as duplicates and listed in the import summary.
Yes. Your complete dataset can be downloaded as CSV or XLSX. With Pro active, exports also include expiry information and custom fields.
Certificate records are stored in the {prefix}_edcv_certificates table in your own WordPress database. Pro certificate metadata and verification analytics use separate plugin tables.
Visitors enter an authentication code on the automatically created Validate Certificate page, or on any page containing [edcv_validator]. A URL containing ?certificate_code=THEIR-CODE or ?code=THEIR-CODE fills in the form and starts verification automatically, which makes it easy to verify a certificate from a link or a QR code.
Yes, with Pro. Custom fields let you record whatever the document needs — ID card numbers, membership types, test results, license details — so the same public page works as an ID card verifier, a library card verifier, or a general document verification page. The course name field can be left empty.
Yes. The verification endpoint is nonce-protected and allows 30 attempts per IP address in a fixed 60-second window. Public PDF downloads use a separate limit of 10 attempts per IP in their own 60-second window.
No. Certificate lookup, QR generation, and PDF generation all run on your own WordPress site. Freemius is used only for licensing, account, and checkout services, and email delivery depends on your site's existing mail configuration.
Yes. [edcv_validator] is a standard WordPress shortcode, so it works in the block editor, the classic editor, and any page builder that supports shortcodes, including Elementor, Divi, and Beaver Builder.
Administrators only, by default. Editors, Authors, and other roles cannot see or manage certificate data.
It uses the valid Email value stored in each certificate record. Records without a valid email address are skipped. Bulk sends are queued through WP-Cron in batches of 15.
QR generation requires the PHP GD extension, which most hosts enable by default. If GD is unavailable, the plugin shows an administrator notice and does not generate QR images.
With Pro active, the public result changes to show expired, revoked, or suspended status. Public PDF download is offered only for certificates that are currently valid.
Generated PDF certificates work best with Latin-based text. Unsupported characters in learner names, course titles, issuer names, or signature names may be transliterated or omitted in the PDF. Certificate records and the public verification page use WordPress's normal UTF-8 text handling and are not affected by this limitation.
No. The plugin migrates your legacy CSV dataset into its database table and keeps a backup under a random filename. Version 2.0.0 also migrates the former Pro email metadata value into the core Email column where one is available.
Deactivating leaves everything untouched. Uninstalling also keeps your data by default. The Data Management page includes an opt-in setting to delete core certificate data on uninstall, and Pro settings include a separate opt-in control for deleting Pro metadata, analytics, and settings. Check both before uninstalling.
Rate limits can be adjusted with the edcv_rate_limit_max_attempts and edcv_rate_limit_window filters. Trusted hosting environments can supply a validated, server-normalized client IP through edcv_rate_limit_visitor_identity. Record lifecycle actions and verification card filters are preserved from earlier versions.