Built with not-for-profit governance workflows in mind<\/li>\n<\/ul>\n\nNotes for Developers<\/h3>\n\n
This plugin is built with a modern architecture using PSR-4 autoloading, namespacing under MIME<\/code>, and follows WordPress best practices for escaping, sanitizing, and hooking. Documentation at https:\/\/plugins.webworkz.nz<\/p>\n\n\n\n- Upload the plugin folder to
\/wp-content\/plugins\/meta-membership\/<\/code><\/li>\n- Activate the plugin through the 'Plugins' menu in WordPress<\/li>\n
- Create a page and add the
[mime_dashboard]<\/code> shortcode \u2014 Meta Membership will detect it automatically<\/li>\n- Go to Meta Membership Settings<\/strong> to configure defaults (General, Payments, Notifications, Member Meta Fields)<\/li>\n
- Create one or more Membership Types under Membership > Membership Types<\/strong><\/li>\n
- Add the
[mime_registration type=\"mt-slug\"]<\/code> shortcode to any page to enable a public registration form \u2014 replace mt-slug with your membership type slug (available via copy-to-clipboard in the Membership Types table)<\/li>\n- Enable payment gateways in the Payments tab<\/li>\n<\/ol>\n\n
Note: Stripe payments require Minimal Stripe Wrapper<\/a> to be installed and configured separately.<\/p>\n\n\n\nIs this plugin suitable for commercial use?<\/h3><\/dt>\nYes, absolutely. While it's designed with clubs and not-for-profits in mind, it's flexible enough for commercial sites as well.<\/p><\/dd>\n
How is this different from other membership plugins?<\/h3><\/dt>\nMost membership plugins determine membership status from payment records. Meta Membership uses the membership cycle as the source of truth \u2014 so grace periods, fixed expiry dates, and renewal behaviour work the way your organisation expects, regardless of payment history.<\/p><\/dd>\n
Does this plugin handle fixed annual expiry dates?<\/h3><\/dt>\nYes. You can set a fixed expiry date (e.g. 1 April) that applies to all memberships of a given type, with configurable grace periods and optional pro-rata fees for members joining mid-year.<\/p><\/dd>\n
Does this plugin support recurring payments?<\/h3><\/dt>\nNot yet. Stripe-based recurring payments \u2014 where a card is charged automatically without member action \u2014 are on the roadmap. Meta Membership handles one-off payments for registration and renewal, supported by automated expiry notifications and grace periods that guide members through the renewal process at the right time.<\/p><\/dd>\n
Can I migrate my existing members from another plugin?<\/h3><\/dt>\nYes. Meta Membership includes a CSV import tool that handles member records, membership types, expiry dates, registration status, renewal intent, and custom member fields.<\/p><\/dd>\n
Can I extend or customise the member fields?<\/h3><\/dt>\nYes. Member profiles are stored in a dedicated database table, and custom fields can be defined with privacy controls, editability settings, and required flags. The plugin is extensible via actions and filters.<\/p><\/dd>\n
Will my members need to reset their passwords after migrating to Meta Membership?<\/h3><\/dt>\nNo. Meta Membership is designed to work with existing WordPress user accounts. During member import, if an email address matches an existing WordPress user, that account is preserved and linked to the new membership record. Members can log in with their existing credentials immediately after migration \u2014 no password reset required.<\/p><\/dd>\n
Does this work with MailPoet?<\/h3><\/dt>\nYes, via the free Meta MailPoet add-on, which syncs membership status and type to MailPoet lists automatically. No paid MailPoet tier required.<\/p><\/dd>\n
Does this work with Ultimate Member?<\/h3><\/dt>\nMeta Membership can coexist with Ultimate Member. A common setup is to use Ultimate Member for its member profile UX and directory features, while Meta Membership handles membership logic \u2014 with Ultimate Member's own membership features disabled to avoid conflict. Role Sync Rules can be used to keep WP roles aligned with membership status for compatibility.<\/p><\/dd>\n
Is this plugin multisite-compatible?<\/h3><\/dt>\nNot yet tested with multisite. It should work on a per-site basis, but has not been formally validated in a network setup.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.0.0<\/h4>\n\n\n- Initial public release<\/li>\n
- Membership cycle architecture with renewal tracking<\/li>\n
- Three renewal modes: fixed expiry, anniversary, never expires<\/li>\n
- Pro-rata fee support for fixed expiry memberships<\/li>\n
- Configurable grace periods<\/li>\n
- Stripe Checkout integration via Minimal Stripe Wrapper<\/li>\n
- Manual payment option<\/li>\n
- Event-triggered system notifications and configurable time-based membership reminders<\/li>\n
- Page, post, and menu visibility settings by membership status<\/li>\n
- Registration policy framework: open, admin approval, admin-only<\/li>\n
- Custom member fields with privacy and editability controls<\/li>\n
- WordPress role sync rules<\/li>\n
- CSV member import and export<\/li>\n
- Member dashboard and registration shortcodes<\/li>\n
- Developer-friendly modern architecture<\/li>\n<\/ul>","raw_excerpt":"WordPress membership built around the membership cycle, not transactions. Free, flexible, and designed with clubs and nonprofits in mind.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/arq.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/241723","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/arq.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/arq.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/arq.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=241723"}],"author":[{"embeddable":true,"href":"https:\/\/arq.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/jerrystewart99"}],"wp:attachment":[{"href":"https:\/\/arq.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=241723"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/arq.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=241723"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/arq.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=241723"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/arq.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=241723"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/arq.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=241723"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/arq.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=241723"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}