DrDanon Certificates for WooCommerce

By drdanon

0+ active installationsVersion 1.10.5

Course participants enter their name in My Account and download a PDF or PNG certificate with a number, date and verification QR code.

Description

DrDanon Certificates for WooCommerce lets customers who bought a course download their certificate from My account → Certificates.

The customer enters the name once for each certificate (with a live preview and a confirmation checkbox), so one account – a school, for example – can hold certificates for different people. From then on she can download the certificate as PDF or PNG as often as she likes. The certificate file is generated in the browser, so no files are stored on the server.

Features

  • Certificate per product: JPG or PNG background, available from a chosen date – optionally from a chosen time (e.g. 12:00).
  • Name, certificate number, date and QR code – each with its own position, size, colour, font, bold and alignment.
  • Long names can be split into two lines automatically.
  • Date of issue or course date, in a format you choose (presets, the site format or a custom PHP date format) – globally or per product.
  • Built-in fonts with Latin and Cyrillic characters, uploaded TTF/OTF/WOFF/WOFF2 fonts and fonts from the WordPress Font Library, with a character check.
  • Public verification page ([tcert_verify] shortcode) that answers to a certificate number only – no search by name, no list of people. It shows the full name, the first name with a masked surname, or a fully masked name; with rate limiting and a cache test. It can be turned off.
  • Automatic revocation after a refund or cancellation, manual revocation, manual access grants and removal – by account search or from a CSV file – also for people who never bought the product.
  • Certificates for courses that are not in the shop (old products, courses sold elsewhere) through a private, hidden product.
  • Live preview and “Download sample PDF” button in the product editor.
  • All texts of the customer pages can be edited; button colours, corner radius and width can be set in the settings.
  • Own time zone for unlock times and printed dates (defaults to the site time zone).
  • “Accounts and certificates” list in the admin: which account has which certificate, the name saved for it, its status, how many times and when the customer last generated the file.
  • Personal data export and erasure (WordPress privacy tools), suggested privacy policy text.
  • Compatible with WooCommerce High-Performance Order Storage (HPOS).

No e-mails. The plugin never sends any e-mail – neither to customers nor to the administrator.

No external services. The plugin has no telemetry and does not contact any third-party service. Fonts, QR code generator and the PDF writer are bundled. The browser loads only files from your own site: the certificate background and uploaded fonts from your Media Library – if your site serves media through a CDN, they come from that CDN.

Analytics events – off by default. If you turn on “Analytics events” (WooCommerce → Training certificates → General), the customer page fires the browser event tcert:download when a certificate file is prepared and, only if your site already has a window.dataLayer (e.g. Google Tag Manager), adds a tcert_download entry to it. Both carry the file format, the product ID and the course title – never the name or the certificate number. The plugin loads no tracking script and sends nothing to other servers by itself; whether a tag fires and what happens with the event is decided by your tag manager and consent tool, so turn the option on only when your consent settings and privacy policy cover it. With the option off nothing is passed to analytics tools. Names on the customer page are marked with data-clarity-mask, so session-recording tools that honour it (Microsoft Clarity) hide them.

WooCommerce is a trademark of its owner. This plugin is an independent add-on and is not affiliated with or endorsed by WooCommerce or Automattic.

Privacy

The plugin stores manually granted access, the issued certificates (number, course, the name entered for that certificate, date of issue, status) and, for each certificate, how many times and when the customer last generated the file (a counter and one date, no history) in the WordPress database. The data is used to generate certificates and to confirm their authenticity. It is included in the WordPress personal data export and removed by the personal data eraser and when the user account is deleted. The plugin sends no data to third-party services and sends no e-mails.

Third-party resources

  • QR Code Generator for JavaScript by Kazuhiko Arase, version 2.0.4 (unmodified dist/qrcode.js from the npm package qrcode-generator, source: https://github.com/kazuhikoarase/qrcode-generator) – MIT license – assets/js/vendor/qrcode.js, licence text in assets/js/vendor/qrcode-LICENSE.txt. “QR Code” is a registered trademark of DENSO WAVE INCORPORATED.
  • Fonts Caveat, Cormorant Garamond, Lora, Marck Script, Montserrat and Playfair Display – SIL Open Font License 1.1 – assets/fonts/ (see assets/fonts/OFL.txt).

Installation

  1. Install and activate WooCommerce.
  2. Upload the plugin in Plugins → Add New → Upload Plugin, or install it from the WordPress.org plugin directory, and activate it.
  3. Go to WooCommerce → Training certificates and check the settings. Click “Create the verification page” (General tab) to add the verification page.
  4. Edit a product, open the Certificate tab, enable “Issue a certificate”, choose a background and place the elements. Use “Download sample PDF” to check the result.
  5. If My account → Certificates shows a 404 error, go to Settings → Permalinks and click “Save Changes”.

FAQ

Can customers change their name later?

No – the name is saved once for each certificate. Every new certificate asks for a name again, so the same account can use a different name (a changed surname, another teacher of a school) on the next certificate while the older certificates keep theirs. An administrator can correct the name on a certificate or unlock single certificates in Users → Edit user → Certificate; the customer then enters the name for those certificates once more.

Can someone look up a person on the verification page?

No. The public page accepts a certificate number only. Typing a name returns a request to enter the number; there is no search by name, no name confirmation and no list of people. Lists of accounts and certificates exist only in the admin panel, for users who can manage the shop.

Who gets a certificate?

Logged-in customers who bought the product (paid order) and customers to whom access was granted manually or by CSV import. After a full refund, a refund of the course line (its whole quantity) or a cancellation the certificate is revoked automatically. A refund of an amount only (no quantity) does not revoke it. The list of issued certificates shows the saved status, which can be updated with a short delay (background check); the verification page and My Account always check the current state.

What does “Files generated” in the admin list mean?

It counts how often the customer prepared the PDF or PNG file on the “My account” page and when that last happened. It is a usage statistic reported by the customer’s browser, not a proof: it does not confirm that the file was saved, the owner of a certificate could raise her own number, and counting stops at one million. The counter is visible only to shop managers in WooCommerce → Certificate access → Accounts and certificates; customers do not see it.

Do I have to do anything with existing certificates after updating?

No. Certificates issued by earlier versions keep their numbers, names, dates and statuses, and QR codes on downloaded files keep working. Only certificates that have no name yet ask for one. The first visit of a shop manager to the admin panel after the update adds two counter columns to the plugin table; until then everything else works as before.

Does the limit of verification attempts work behind Cloudflare or another proxy?

By default the limit uses the address of the connection as the server sees it and trusts no request header, so it cannot be bypassed by sending a made-up address. If a proxy in front of the site does not pass visitor addresses on, its visitors share one limit – less precise, but not weaker. Many servers already restore visitor addresses; then nothing needs to be set.

For the standard Cloudflare proxy there is an option, off by default: WooCommerce → Training certificates → General → Cloudflare. The settings page tells you whether the server currently sees a Cloudflare address. When the option is on, the Cloudflare headers (CF-Connecting-IP, CF-Connecting-IPv6) are used only for connections that come from Cloudflare’s published address ranges, which are bundled with the plugin (keep the plugin updated). The option is not meant for sites with Cloudflare Workers in front of them, tunnels or additional proxies – the address range shows that a request comes from the Cloudflare network, not that it belongs to your own zone. For any other reverse proxy or load balancer return the right address from the tcert_client_ip filter, and never copy an address from a request header there unless that header can only be set by your own proxy.

Is the PDF signed?

No. The PDF contains an image of the certificate. Authenticity is confirmed by the certificate number and QR code on the verification page.

Can certificates unlock at a specific time?

Yes. In the product, set “Available from” and check “Unlock at a specific time” (for example 12:00). The time uses the plugin time zone from WooCommerce → Training certificates → General, which by default is the site time zone. Without a time the certificate unlocks at 00:00.

Which date formats can I use?

Presets such as 31 October 2026, 31.10.2026, 10/31/2026 or 2026-10-31, the site format from Settings → General, or a custom PHP date format such as l, j F Y. Month and day names follow the site language. Each product can override the global format.

Cache and CDN

The verification page and My account → Certificates must not be cached. In your cache plugin (LiteSpeed, WP Rocket, W3 Total Cache…) add both addresses to “Never cache”. With Cloudflare create a Cache Rule with the action “Bypass cache” for the path of your verification page (for example /certificate-verification) and for the My account endpoint (/certificates or, for sites that used older versions, /certyfikaty). Then use “Check that the verification page is not cached” in WooCommerce → Training certificates.

A rate limiting rule for the verification page on your CDN (for example 30 requests per minute per IP) is recommended as a second line of defence.

Does it work with Multisite?

No. The plugin supports single-site installations only.

Is the plugin available in my language?

The plugin is fully translatable. Translations are managed on translate.wordpress.org and installed by WordPress automatically.

Can I change the My account address?

New installations use /my-account/certificates/. Sites updated from versions before 1.7.0 keep /my-account/certyfikaty/, so links customers already have keep working.

Changelog

1.10.5

  • Fixed: the button that applies the ticked people and the CSV file on the “Certificate access” screen was always greyed out, so access could not be granted or removed there.

1.10.4

  • Changed: counting verification attempts per visitor behind Cloudflare is now an option that is off by default (WooCommerce → Training certificates → General → Cloudflare). By default no request header is trusted, exactly as before 1.10.3. With the option on, CF-Connecting-IPv6 is read first (Cloudflare “Pseudo IPv4”), and the headers are still used only for connections from Cloudflare’s address ranges.
  • Improved: the list of people with manually granted access says when it stopped at its ceiling of 5000 checked accounts, and reads accounts in a fixed order.
  • Improved: the counter columns are checked on the “Accounts and certificates” screen itself, and a counter that is not available is shown as “—” instead of 0.

1.10.3

  • Added: counting verification attempts per visitor behind the standard Cloudflare proxy; the CF-Connecting-IP header is used only for connections from Cloudflare’s published address ranges (see 1.10.4: an option, off by default). Other trusted proxies can use the tcert_client_ip filter.

1.10.2

  • Fixed: the list of people with manually granted access reads candidates page by page and checks them exactly (up to 5000 accounts), so entries that only look similar in the database no longer push real people off the list.
  • Improved: the counter of generated files is switched on only when both of its columns exist, and switched off again if the table is later found without them; the “Accounts and certificates” list shows a notice.
  • Docs: the readme describes the counter as a statistic (not a proof) with its upper limit. Tested with WooCommerce 11.3.

1.10.1

  • Fixed: in “Certificate access” a late search answer for the previously selected course (or for a text that was cleared meanwhile) could be shown under the newly selected course.
  • Changed: analytics events (tcert:download, dataLayer entry) are now an option that is off by default (WooCommerce → Training certificates → General → Analytics events). The suggested privacy policy text mentions them only when the option is on.
  • Changed: the counter is kept in the certificates table as a number and the date of the last time, updated in one step – no limit of 500 per account, nothing lost when two files are prepared at once, and the personal data export contains everything that is stored. Revoked certificates and certificates waiting for a new name are not counted. In in-app browsers the file is counted when it is handed over.
  • Changed: the counter is shown only in the “Accounts and certificates” list (as “Files generated”), no longer in the user profile.
  • Improved: saving a new name on an unlocked certificate reports success only after the certificate is locked again; the carry-over of accounts unlocked in older versions is confirmed before it is marked as done; the list of manual grants no longer misses people when the pre-filter matches other values; a failure while creating a certificate-only product is logged (WooCommerce → Status → Logs) instead of ending in an error page.

1.10.0

  • Changed: every certificate has its own name. The customer enters the name once for each certificate (a form next to each certificate in My account); a number is issued when the name is saved. Certificates issued before keep their names.
  • Changed: unlocking is done per certificate (user profile → Certificate) – one or several certificates can be unlocked, the others stay locked. The account-level name field, the account-wide unlock and the “Certificate” column in the users list were removed. Accounts unlocked as a whole in older versions get all their certificates unlocked once.
  • Changed (privacy): the verification page answers to a certificate number only. The name confirmation form was removed; typing a name returns a request to enter the number.
  • Added: third display mode on the verification page – first name and masked surname (“Maria K•••”).
  • Added: “Accounts and certificates” tab in WooCommerce → Certificate access – account, course, name, number, status, number of downloads and time of the last download, with a course filter and search; for a selected course also the people with manually granted access who have not entered a name yet.
  • Added: counter of generated files (how many times and when the customer last prepared the PDF or PNG).
  • Added: optional tcert:download browser event and tcert_download dataLayer entry (see 1.10.1: off by default) with the format, product ID and course title; names on the customer page are marked with data-clarity-mask.

1.9.0

  • Added: WooCommerce → Certificate access (formerly “Import access (CSV)”) – search accounts by e-mail, login or name, tick them and grant access to a certificate, also for people who never bought the product.
  • Added: removing manually granted access – for ticked accounts or from a CSV file. A certificate that was already issued is then blocked automatically, unless the person bought the course.
  • Added: list of people with manually granted access to a course, with the number and status of their certificate.
  • Added: “Certificate for a course that is not in the shop” – creates a private, hidden product without a price that only carries the certificate (old products, courses sold elsewhere).
  • Changed: when a customer enters a new name after unlocking, certificates already issued keep the name they were issued with; only an administrator can change it (user profile). The “also change the name on all issued certificates” box in the profile is no longer ticked by default.
  • Unchanged: people who already have access are skipped, so applying the same list or file twice changes nothing, and a later purchase of the same course does not create a second certificate.

1.8.5

  • Improved: certificates use the original background file. WordPress replaces uploads wider than 2560 px with a smaller copy and that copy was used before, so the downloaded certificate was less sharp than the uploaded graphic (originals up to 5000 px on the longer side are used).
  • Improved: small backgrounds are rendered at print size (A4 at 300 dpi), so the name, number, date and QR code stay sharp.
  • Improved: the image inside the PDF is saved at the highest JPEG quality with full colour resolution (larger file, about 3 MB for A4).
  • Added: the QR code in the PDF is clickable and opens the verification page.
  • Added: the name, number and date in the PDF can be selected, copied and searched (invisible text layer, no extra files).
  • Changed: the name check on the verification page ignores upper and lower case (“anna kowalska” confirms “Anna Kowalska”).
  • Fixed: PHP warning when the product data panel is rendered without a current product.

1.8.4

  • Fixed: critical error on activation on sites where another plugin (SEO, page builder, cache) runs shortcodes while a page is saved.
  • Changed: the verification page is no longer created on activation – create it with the button in Settings (an existing published page with the [tcert_verify] shortcode is reused, no duplicates; drafts are never published automatically).
  • Fixed: “Failed to fetch” when the background or font URL points to another address (www / http vs https, CDN or cache plugin) – the other address is tried as well, also when a file downloads but is not a valid image or font.
  • Fixed: refunding the whole quantity of one course line (order still paid) now revokes that course’s certificate.
  • Changed: the QR code has the standard 4-module quiet zone.
  • Added: the date the name was saved is included in the personal data export.
  • Added: full MIT licence text of the bundled QR code library.

1.8.2

  • Fixed: QR codes encode non-ASCII addresses (international domains, page slugs) as UTF-8.
  • Changed: no silenced PHP errors in the font check; translation template header updated.

1.8.1

  • Changed: plugin name “DrDanon Certificates for WooCommerce”, slug and text domain drdanon-certificates-for-woocommerce.
  • Removed: the free-form custom CSS setting. Use Appearance → Customize → Additional CSS instead; the colour, corner radius and width settings stay.
  • Changed: all request data is sanitized when it is read; nonces are sanitized before verification.
  • Changed: admin notices are shown only on the Plugins screen, the plugin’s own screens and product screens.
  • Changed: translations are provided through translate.wordpress.org (no bundled .po/.mo files).

1.8.0

  • New: certificates can be unlocked at a specific time (“Unlock at a specific time” in the product).
  • New: time zone setting in WooCommerce → Training certificates → General (default: the site time zone). It is used for unlock times and for the dates on certificates and on the verification page.

1.7.2

  • Changed: text domain and plugin folder are now drdanon-certificates-for-woocommerce (the WordPress.org slug).
  • Fixed: the QR code in the product preview and the sample PDF leads to the verification page.
  • Fixed: the certificate number stays in the field when the name check form on the verification page has expired.
  • Fixed: the “(uploaded)” font label and the download file names are translatable.

1.7.0

  • New: date format – more presets, the site format and custom formats, globally and per product (with a live preview).
  • New: long names can be split into two lines automatically.
  • New: English source texts, translation ready.
  • New: default texts follow the site language until you change them.
  • New: suggested privacy policy text.
  • Changed: plugin name “DrDanon Certificates for WooCommerce”, readme in the WordPress.org format.
  • Changed: database queries use $wpdb->prepare() with identifier placeholders; uninstall uses the WordPress filesystem API.
  • Changed: verification name check is protected with a nonce.
  • Changed: font uploads use wp_handle_upload().
  • Removed: Markdown change logs and test notes from the package.

1.6.2

  • Fixed: certificate status in the user profile is reconciled before display.
  • Fixed: clearer error for an empty name confirmation on the verification page.
  • Improved: per-request cache of certificate products.

1.6.1

  • Improved: access checks during verification, save locks, font validation and privacy tools. Multisite is blocked.

1.6.0

  • New: certificate number without the address, separate switch for the verification page, editable texts and styles, date on the certificate, custom fonts, PDF page sized like the graphic.