jerrystewart99

Meta Membership is a clean, flexible, developer-friendly plugin for membership sites. Most membership plugins treat payments as the source of truth. Meta Membership is built around the membership cycle — so renewals, grace periods, and fixed annual expiry dates work the way your organisation actually expects.
Designed with clubs, nonprofits, professional associations, and community groups in mind.
Try it now — no install needed. Explore a fully-configured demo site running entirely in your browser, with sample membership types, members in different lifecycle states, and a working registration flow: <a href="https://playground.wordpress.net/?blueprint-url=https://plugins.webworkz.nz/mm-demo.json" rel="nofollow ugc">Launch the live demo</a>
It includes:
<ul>
<li>Stripe-based payments and renewals (via <a href="https://wordpress.org/plugins/minimal-stripe-wrapper/" rel="ugc">Minimal Stripe Wrapper</a>)</li>
<li>Three renewal modes: fixed expiry date, anniversary, or never expires</li>
<li>Fixed expiry with pro-rata fees for mid-year joiners</li>
<li>Configurable grace periods — members retain access while they renew</li>
<li>Registration policies: open, admin approval, or admin-only</li>
<li>Page, post, and menu access control by membership status</li>
<li>Built-in notifications for expiry reminders and admin alerts</li>
<li>CSV import and export — migrate in from another plugin without losing your data</li>
<li>Native MailPoet integration (via free Meta MailPoet add-on)</li>
</ul>
Whether you need a simple signup flow or granular control over membership logic, Meta Membership is built to adapt — without the bloat.
For documentation, visit <a href="https://plugins.webworkz.nz" rel="nofollow ugc">plugins.webworkz.nz</a>
<h3>Ideal For</h3>
<ul>
<li>Not-for-profit organisations</li>
<li>Professional and hobby clubs</li>
<li>Community and advocacy groups</li>
<li>Event-based member programmes</li>
<li>Developers building custom member workflows</li>
</ul>
<h3>Features</h3>
<ul>
<li>Membership cycle as source of truth — status driven by cycle, not payment history</li>
<li>Three renewal modes: fixed expiry date, anniversary, or never expires</li>
<li>Fixed expiry date support — e.g. all memberships expire 1 April each year</li>
<li>Pro-rata fees for members joining mid-period on fixed expiry memberships</li>
<li>Configurable grace periods — expired members retain access while they renew</li>
<li>Multiple membership types with separate fees, renewal rules, and registration policies</li>
<li>Separate registration fee and renewal fee per membership type</li>
<li>Stripe-integrated membership payments (via Minimal Stripe Wrapper)</li>
<li>Manual payment option for members who pay offline</li>
<li>Registration policies: open, admin approval, or admin-only</li>
<li>Email validation option on registration</li>
<li>Page, post, and menu visibility control by membership status</li>
<li>Custom member fields (meta fields) with privacy and editability controls</li>
<li>Two notification systems — event-triggered system notifications and configurable time-based membership reminders</li>
<li>CSV member import — migrate from your existing system with membership type, expiry, status, and custom fields</li>
<li>CSV member export</li>
<li>WordPress role sync — optionally map membership types and statuses to WP roles for compatibility with other plugins</li>
<li>Developer-friendly: modern architecture with PSR-4 autoloading and clean namespacing under MIME</li>
<li>Built with not-for-profit governance workflows in mind</li>
</ul>
<h3>Notes for Developers</h3>
This plugin is built with a modern architecture using PSR-4 autoloading, namespacing under <code>MIME</code>, and follows WordPress best practices for escaping, sanitizing, and hooking. Documentation at https://plugins.webworkz.nz

Meta Membership

WordPress membership built around the membership cycle, not transactions. Free, flexible, and designed with clubs and nonprofits in mind.

Andie Hunt

You can use the CiviEvent widget to add two types of widgets for upcoming public events from CiviCRM. There’s no limit to the number of widgets you can add of either type. You can include the widgets in the sidebar like normal, or you can include them via shortcodes in the body of your posts.
<h4>CiviEvent List Widget</h4>
This widget is a basic, flexible listing of upcoming events that are marked as public. You have options to customize the appearance and number of events. There is the option to add the event’s city, state, and/or country to the listing if “Show location” is enabled on the event.
<h4>Single CiviEvent Widget</h4>
This widget displays a single public event from CiviCRM. By default, it will display the first event from the current day or the future, or you can set an offset to skip one or more and display the second or third upcoming event. You may display the location if “Show location” is enabled on the event.
<h4>Shortcodes</h4>
Both widgets are available to be inserted into the body of a post using a shortcode. Use the <code>[civievent_widget]</code> shortcode for the events listing and the <code>[civievent_single_widget]</code> shortcode for the single next (or offset) event. The available parameters for the shortcodes are as follows:
<ul>
<li><code>title="Your Title"</code> The widget title (default: “Upcoming Events” for the list widget, or the event’s title for the single widget).</li>
<li><code>summary=1</code> Display the event summary. Omit the parameter or set it to 0 to hide the summary. (List widget only.)</li>
<li><code>limit=5</code> Display the specified number of events (default: 5). (List widget only.)</li>
<li><code>alllink=1</code> Display “view all” with a link to the page with a full list of public events. Omit the parameter or set it to 0 to hide the link. (List widget only.)</li>
<li><code>wtheme="mytheme"</code> The widget theme (a class added to the widget div). Set a new one and handle it in your theme’s CSS. (Default for list widget: “stripe”, with “divider” as an alternative. Default for single widget: “standard”.)</li>
<li><code>divider=" | "</code> The location field delimiter (default: comma followed by a space).</li>
<li><code>city=1</code> Display the event’s city. Omit the parameter or set it to 0 to hide the city.</li>
<li><code>state="abbreviate"</code> Display the event’s state/province. Default is “none”, which will display nothing about the state or province. Display options are “abbreviate” for the state/province abbreviation or “full” for the full name.</li>
<li><code>country=1</code> Display the event’s country. Omit the parameter or set it to 0 to hide the country.</li>
<li><code>offset=2</code> Skip the given number of events before displaying the next one (default: 0). (Single widget only.)</li>
<li><code>admin_type="simple"</code> Whether to use the “simple” (default) or “custom” display options (as appear in the widget settings). The <code>custom_display</code> and <code>custom_filter</code> parameters only function alongside <code>admin_type="custom"</code>. The <code>summary</code>, <code>alllink</code>, <code>divider</code>, <code>city</code>, <code>state</code>, and <code>country</code> parameters only function when <code>admin_type="simple"</code> (or reverting to the default). (List widget only.)</li>
<li><code>custom_display='{"event_title_infolink":{"title":0,"prefix":null,"suffix":null,"wrapper":1},"description":{"title":1,"prefix":null,"suffix":null,"wrapper":1}}'</code> Custom options for displaying results when <code>admin_type="custom"</code>. The value should be an object written in JSON. Each property name should be a field to display, and the property value should be an object with the following properties: <code>title</code> (1 or 0: whether to display the field name), <code>prefix</code> (<code>null</code> or a string with markup to precede the field), <code>suffix</code> (<code>null</code> or a string with markup to follow the field), and <code>wrapper</code> (1 or 0: whether to wrap the field with the default wrapper elements. You may configure a widget using the standard widget interface, click “Show JSON”, and copy the JSON into this parameter. If <code>custom_display</code> is missing, the listing will revert to displaying in the “simple” mode despite the <code>admin_type</code> value. (List widget only.)</li>
<li><code>custom_filter='{"start_date": {">=": "2015-12-16"}, "is_public": 1, "options": {"sort": "start_date ASC"}}'</code> Custom options for filtering results when <code>admin_type="custom"</code>. The value should be an object written in JSON. The object should be a valid set of parameters for the CiviCRM API. The default is to list all public events starting on today’s date or later, sorted by start date ascending. (List widget only.)</li>
<li><code>event_type_id=3</code> Display Event with event type id 3 (default: show all event). (only work with admin_type=”simple”.)</li>
</ul>
<h4>Further Notes</h4>
This plugin requires CiviCRM 4.3 or higher to function. It is only supported with CiviCRM 4.6 or higher.
Read more at https://aghstrategies.com/civievent-widget

CiviEvent Widget

Display widgets for CiviCRM events: the next public event or a whole list. Embed widgets as shortcodes, too!

Meta Membership vs CiviEvent Widget