HLX Donate

By hacklayer

0+ active installationsVersion 2.1.0

Customisable donation forms with three designs, WooCommerce checkout, contribution records and email acknowledgements.

Description

HLX Donate helps a website explain its initiative and accept one-time contributions through its own WooCommerce checkout and configured payment gateway.

Add [hlx_donate] to a page. Choose Ivory Editorial, Midnight Spotlight or Clay Community in HLX Donate > Fund Page. Change the organiser name, fund name, headline, purpose, contact button, amounts and policy to suit your initiative. The theme provides the website header and footer. There are no external fonts, developer tracking, public donor lists or invented fundraising totals.

Features

  • Three responsive layouts, sharing one payment and policy-consent flow.
  • Amount presets, a custom amount and a configurable minimum in the WooCommerce currency.
  • A required published fund policy and an explicit switch to open collection.
  • Standard WooCommerce checkout and gateway integration; the plugin never collects card details.
  • Administrator-only contribution history, net totals after itemised refunds, and linked orders.
  • Optional HTML thank-you emails and PDF acknowledgements generated in memory.
  • WordPress personal-data export and anonymisation for the plugin’s contribution records and mail logs.
  • Scoped frontend styles and assets loaded when a form is rendered.

WooCommerce and a working payment gateway are required to collect money. Email delivery depends on the website’s mail configuration. An acknowledgement is not evidence of tax exemption or a refund guarantee.

Installation

  1. Back up the database and installed plugin, then test upgrades on a staging site.
  2. Install or update HLX Donate in place. Do not delete version 1.2.2 first: its original uninstaller deletes the donation tables.
  3. Activate WooCommerce and configure the store currency, checkout and payment gateway.
  4. Add [hlx_donate] in a Shortcode block on a page.
  5. Open HLX Donate > Fund Page. Choose a design and review the organiser, purpose, contact email and amounts.
  6. Write the actual funding, cancellation and refund terms, then enable contributions.
  7. Configure acknowledgements, test mail delivery, and complete gateway sandbox payment/refund tests before collecting money.

FAQ

Which shortcodes are available?

[hlx_donate] uses the saved design. Per-page options include:

  • [hlx_donate design=”ivory”]
  • [hlx_donate design=”midnight”]
  • [hlx_donate design=”clay”]
  • [hlx_donate amounts=”10,25,50,100″ default=”25″]

Amounts must respect the minimum configured by the administrator. The existing [hlx_donate_fund] and [hlx_donate_event] aliases still work. Legacy theme/layout attributes do not select the retired layouts.

What must the fund policy explain?

Identify the organiser, purpose, use of contributions, handling of insufficient funds or changed plans, refund availability and process, and remaining funds. A blank policy keeps collection paused. Contributors must accept the current policy; changing it invalidates consent in an older cart. The accepted policy is saved on the WooCommerce order item.

Are monthly payments supported?

No. Version 1.2.2’s monthly option sent a reminder; it did not create an automatic payment subscription. That option and its scheduled reminder are retired in version 2. The current form accepts one-time contributions only.

Will updating change an existing form?

Yes. This is a major redesign. The original shortcode uses the new layouts. Old colour/theme controls, FAQ, allocation and social editors, donor notes and reminder controls are retired. Saved historical settings and financial records are preserved; relevant customised text, amount and contact settings are imported. Existing general contributions are not silently reassigned to a new fund. A previously unconfigured fund starts paused and must be reviewed before opening.

An existing 2.0.x installation retains its saved content; a retired design selection falls back to Ivory. Fresh installs use the website name and neutral sample text, which the organiser should replace.

Which amounts and currencies are supported?

The currency comes from WooCommerce. Contributions support up to two decimal places, a minimum of at least 1 and a maximum of 1,000,000. Fresh installs start with a minimum of 1; upgrades retain the previous minimum of 99 until changed. Review WooCommerce currency precision and your gateway’s currency/amount limits before collection.

How are refunds counted?

Paid WooCommerce contribution items are recorded once using a unique order-item reference. Pending or unpaid orders are not counted. Itemised partial refunds reduce the net recorded contribution; fully refunded/reversed orders are excluded. The dashboard separates currencies and historical/unlinked rows.

Amount-only partial refunds without an item allocation, gateway fees, external/off-platform payments and disputes that do not update WooCommerce are not automatically reconciled. Review these separately in your financial records.

Does the plugin show the contact email?

Only the editable contact button label is shown. The configured address is used in its mailto link and remains readable in page source. Leaving it blank uses the site’s administrator email. Use an appropriate public contact address.

What data is stored or sent?

Contributor names/emails, amounts, currency, order references, status, timestamps and mail-attempt logs are stored in the site’s database. Policy acceptance and its snapshot are saved on WooCommerce order items. The name and email are used for checkout/acknowledgements. Payment and email providers receive data according to your site’s configuration; the plugin does not send contributor data to its developer.

Suggested privacy-policy text is available in WordPress. Personal-data export includes the plugin’s own ledger and mail logs. Erasure anonymises contributor names/emails and removes old donor notes while keeping financial amounts and order references. WooCommerce orders and third-party records must be handled using their respective privacy tools. Set an appropriate retention policy and protect administrator accounts and backups.

Why can some acknowledgements have no PDF attachment?

The bundled PDF generator uses standard fonts. If the personalised text cannot be represented safely, the complete Unicode HTML acknowledgement is retained instead of attaching a corrupted PDF. Mail logs record acceptance by the mailer, not confirmed inbox delivery.

What happens on deactivation or deletion?

Deactivation retains settings/history. This version also retains them on deletion by default. Explicit cleanup of the plugin’s options and two custom tables requires defining HLX_DONATE_DELETE_DATA as true in wp-config.php before uninstall. Back up first. WooCommerce orders, products and legacy files are not deleted by this cleanup.

Can I cache the donation page?

Exclude checkout, cart and admin-ajax requests from caching. Avoid long-lived page caches containing expired WordPress nonces. Purge page and asset caches after updates.

Screenshots

Changelog

2.1.0

  • Introduced three public layouts: Ivory Editorial, Midnight Spotlight and Clay Community.
  • Made organiser identity, fund copy, contact label and minimum contribution configurable.
  • Retained shortcode aliases, paid-record deduplication, itemised-refund handling, consent snapshots and historical financial records.
  • Prepared SQL identifiers and values using WordPress placeholders; WordPress 6.2 or newer is now required.
  • Added WordPress privacy-policy text, personal-data export and anonymisation.
  • Kept acknowledgements and their PDF files in memory; no credentials, website backups or contributor data are bundled.
  • Retired the previous reminder job and unused form options without deleting stored history.

1.2.2

  • Previous public release.