Aurora Membership Manager

Aurora Membership Manager is a free, self-contained membership management plugin built for associations, clubs, nonprofit organizations and other membership-based groups that want to manage members directly inside WordPress. The Core plugin works without an Aurora account, license key or external service. Member data stays in the site's WordPress database, and Core updates are delivered only through WordPress.org. What Core includes

• Member records with contact details, status, reference numbers and expiry dates.
• Configurable rolling or annual membership validity.
• Renewal overview for active, expiring and expired members.
• Member search and a mobile-friendly staff workspace.
• CSV import and export with spreadsheet-formula protection.
• Secure member portal with opaque, expiring email access links.
• Member profile and privacy-consent management.
• WordPress personal-data exporter and eraser integration.
• Backup, restore, reconciliation, diagnostics and audit tools owned by Core.
• Stable hooks and APIs for separately installed extensions.

Built for organizations that want to keep control Aurora runs inside WordPress rather than moving your membership database to a separate closed platform. Core can be used on its own and does not require WooCommerce, a digital-card provider or a commercial Aurora license. Optional extensions Core remains fully usable without paid extensions. Separate add-on plugins are available when an organization needs additional workflows:

• Membership Manager Pro — communications, campaigns, events, member benefits and advanced operational tools.
• Membership Manager Commerce — WooCommerce membership products, order-to-member workflows and renewals.
• Membership Manager Digital Cards — Passcreator-based digital membership cards and wallet delivery workflows.

Aurora can also support organization-specific extensions for workflows that do not belong in Core or in a standard add-on. These separately installed extensions can combine reusable Aurora capabilities with rules, labels, mappings, templates or integrations tailored to one organization. For example, an organization may need different digital-card templates according to age, membership type or role, or may have its own membership categories and operational workflow. Aurora keeps reusable capabilities generic while organization-specific behavior remains isolated in a separate extension rather than creating a fork of Core. During the 2026 launch period, eligible associations and membership organizations can request no-cost access to the standard separately distributed add-ons until 31 December 2026. Early Adopter 2026 programme details Explore optional extensions and regular pricing or contact Aurora about an organization-specific extension. Standard and organization-specific extensions are separate plugins with their own code, configuration, licensing, external-service disclosures and update channels. They are not included in or unlocked by this WordPress.org package. Documentation and support

• Aurora documentation
• For Core support, use the support forum available from this plugin's WordPress.org page.

1. Install and activate Aurora Membership Manager from WordPress.org.
2. Open Membership Manager > Initial configuration.
3. Enter the organization name and choose the membership validity rule.
4. Add members manually or import a CSV file.
5. Optionally create a member portal page from Membership Manager > Settings > Member portal.

No license key is required for the Core plugin.

1.2.8

• Documents organization-specific extensions as a supported way to add tailored rules and workflows without forking Core.
• Adds one contextual extension-discovery panel to the Extensions screen with links to optional extensions and tailored-extension support.
• Keeps commercial discovery limited to the Extensions screen: no global promotional notices, dashboard advertising, remote promotional assets, tracking or locked Core controls.
• No database schema or public API contract changes.

1.2.7

• Fix checkbox and radio sizing in the member editor.
• Improve WordPress.org discovery tags and screenshot captions.
• Confirm compatibility with WordPress 7.1 after final-release testing.
• Clarifies that a saved renewal fee and currency are manual dashboard assumptions, while installed extensions may supply both values only when the fee is left blank.
• Fix final CSV import button remaining disabled when valid rows are ready.
• Prevent immediate import and backup-restore lock refreshes from being misreported as lost when their expiry value is unchanged within the same second.
• Keep a retained CSV preview visible and renew its retry window when a recoverable final-import error occurs.
• Keep member-bound portal tokens restricted to their original member identities.
• Preserve extension-defined consent keys when Core consent fields are updated.
• Report partial CSV write failures instead of treating them as skipped successful completion.
• Fix the renewal onboarding completion condition.
• Clean up Core schema/lock state completely when data deletion is requested on uninstall.

1.2.6

• Refreshes the WordPress.org presentation, documentation and screenshot captions, and adds one public link to information about optional extensions. No runtime, API or database schema changes.

1.2.5

• Removes promotional/storefront content from the WordPress administration while preserving the operational extension inventory and existing add-on hooks; no API or database schema changes.

1.2.4

• Completes the WordPress.org review hardening by fixing translator annotations for backup/restore notices; no functional API or database schema changes.

1.2.3

• Hardened Plugin Check handling for read-only backup/restore status notices; no functional API or schema changes.

1.2.2

• Hardened request/upload handling for WordPress.org review while preserving Core/add-on contracts.
• Normalized admin notice inputs and documented read-only request parameters for static analysis.

1.2.1

• Aligns the WordPress.org text domain with the approved aurora-membership-manager slug.
• Hardens Basic Setup upload hand-off so extension callbacks receive only explicitly registered and validated upload metadata, never the raw PHP upload superglobal.
• Completes the review audit for request nonces, permissions and early input sanitization while preserving the Core 2.0.0 API contract.
• Keeps Core free of commercial licensing and external update delivery; commercial add-ons remain separate plugins.

1.2.0

• Introduces collision-resistant Aurora_MMC and aurora_mmc prefixes across Core APIs, hooks, options, capabilities, routes and interface identifiers.
• Adds a conservative one-time migration for legacy Core tables, options and role capabilities while preserving existing add-on data.
• Uses identifier placeholders for dynamic database table names on supported WordPress versions.
• Removes inline administration JavaScript and strengthens direct output escaping.
• Preserves legacy public shortcodes as compatibility aliases.
• Publishes Core API contract 2.0.0 for the coordinated add-on releases.