LoopDues for WordPress

Join form, member login and members-only content for organizations that run their memberships on LoopDues.

Members sign in with their LoopDues account and come back to your site logged in. WordPress never stores their password. Access follows each membership: when a member renews, lapses or changes tier, LoopDues tells your site straight away.

Download the latest version (loopdues.zip) · All releases · Changelog

LoopDues no longer provides a WordPress plugin. This one is maintained independently and is built only on the public LoopDues integration ("Sign in with LoopDues", the connection check and webhooks).

Contents

• Features
• Requirements
• Installation
• Using it on your site
• Using member data in themes and other plugins
• How it works
• Releasing a new version

Features

• Join form. The LoopDues signup form as a block or the [loopdues_join] shortcode, with the same options as the embed code in LoopDues.
• Member login. A login button (block, shortcode or on wp-login.php). Signed-in members see My account, which opens their LoopDues portal, and Log out.
• Members-only pages and posts. A Who can see this (LoopDues) box on every public post type: Everyone, Current members, or Members in these tiers. The content is also kept out of excerpts, search results, feeds and the REST API.
• Members-only sections. The LoopDues members only block, or [loopdues_members_only], for part of a page.
• Renew prompt. Lapsed members can still log in and see a Renew my membership button in place of members-only content.
• Live updates. A signed webhook keeps each member's status, tier and paid-through date current, without the member signing in again.
• Safe with existing accounts. It never deletes or replaces users. It links an existing account only if the email matches and the account is a Subscriber, and never links author, editor or administrator accounts.
• Admin overview. A LoopDues column on the Users list (standing, tier, paid-through date), and an Access column on Pages and Posts.
• Members stay out of the dashboard. By default members don't see the admin bar or wp-admin (this can be changed in Settings → LoopDues).

Requirements

• WordPress 6.2 or newer and PHP 7.4 or newer
• An HTTPS site
• A LoopDues organization, with access to Admin → Website sign-in

Installation

1. Download loopdues.zip.
2. In WordPress, go to Plugins → Add New → Upload Plugin, choose the zip and click Activate.
3. In LoopDues, go to Admin → Website sign-in, enter your site's address under Add your site and copy the connection key.
4. In WordPress, go to Settings → LoopDues, paste the key and save. You should see "Connected to" with your organization's name.
5. For the join form, add your site's address to Allowed websites under Settings → Website signup widget in LoopDues. The form only loads on sites listed there.

Updating: download the new zip and upload it the same way. WordPress offers to replace the installed version. The plugin sets Update URI: false, so WordPress never offers to "update" it with an unrelated plugin from WordPress.org.

From git, for development: clone into wp-content/plugins/loopdues, so the folder name matches the release zip.

git clone https://github.com/tenutso/loopdues-wordpress.git wp-content/plugins/loopdues

Using it on your site

Join form

Add the LoopDues join form block, or the shortcode:

[loopdues_join]
[loopdues_join tiers="3,7" width="full" logo="hide" font="inherit" frame="none" color="#1d4ed8" signin="hide"]
[loopdues_join tier="12"]

Tier ids appear in the block's sidebar and in Settings → LoopDues once the site is connected.

Member login

The LoopDues member login block, or [loopdues_login] (optional label="…"). Put it in a header, menu area or page.

Members-only content

• A whole page or post: use the Who can see this (LoopDues) box when editing it. Anyone who can edit the post always sees it.
• Part of a page: use the LoopDues members only block and put other blocks inside it, or the shortcode:

[loopdues_members_only]Only current members see this.[/loopdues_members_only]
[loopdues_members_only tiers="3,12"]Only members in tiers 3 or 12 see this.[/loopdues_members_only]

Settings → LoopDues

Using member data in themes and other plugins

The plugin stores each linked member's record on their WordPress user and exposes a few functions. Everything below is safe to use from a theme or another plugin.

Always check that the plugin is active before calling its functions, so your site keeps working if it's deactivated:

if ( function_exists( 'loopdues_is_current_member' ) && loopdues_is_current_member() ) {
    // current member
}

Who counts as a current member

A current member is a linked user whose LoopDues status is active or grace_period (a renewal payment is being retried). These are listed in the LOOPDUES_CURRENT_STATUSES constant.

Functions

User meta

Written at every sign-in and whenever LoopDues sends an update. Read it with get_user_meta( $user_id, $key, true ).

The member's first and last name are copied into the WordPress user's own first_name, last_name and display_name. When a member is erased or merged in LoopDues, all loopdues_* meta is removed. If the user's role was Member (LoopDues), it's changed back to Subscriber. The user account itself is kept.

Post meta

Prefer loopdues_post_rule() and loopdues_post_hidden() over reading these directly.

Filters

Reacting to changes

Use the loopdues_member_updated action (since 1.0.3). It runs whenever a linked member's record is stored: at every sign-in, and for every membership or payment webhook from LoopDues.

add_action( 'loopdues_member_updated', function ( $user_id, $current, $previous, $member, $context ) {
    $was_current = $previous && $previous['current'];

    if ( $current['current'] && ! $was_current ) {
        // joined, renewed after lapsing, or signed in for the first time as a current member
    } elseif ( ! $current['current'] && $was_current ) {
        // lapsed: grace period over, expired, cancelled…
    }

    if ( $previous && $previous['tier_id'] !== $current['tier_id'] ) {
        // changed tier
    }
}, 10, 5 );

Notes:

• It runs on every update, even when nothing changed (a member signing in again, a payment.received event), so compare $current with $previous.
• It doesn't run for an update that is older than the stored record (events can arrive late), or for members who have never signed in to the site.
• Webhook handlers must answer LoopDues within 10 seconds, so keep listeners quick. Hand slow work (a CRM or mailing-list call) to wp_schedule_single_event().
• Members are signed in with wp_set_auth_cookie() and the standard wp_login action runs too, so existing login hooks keep working.
• When a member is erased or merged in LoopDues, the plugin removes their loopdues_* user meta. To react to that, hook deleted_user_meta for the key loopdues_member_id.

Examples

A members' menu item or greeting in a theme:

<?php if ( function_exists( 'loopdues_is_current_member' ) && loopdues_is_current_member() ) : ?>
    <p>Welcome back, <?php echo esc_html( wp_get_current_user()->first_name ); ?>.
       Your membership runs to <?php echo esc_html( get_user_meta( get_current_user_id(), 'loopdues_paid_through', true ) ); ?>.</p>
<?php elseif ( function_exists( 'loopdues_login_url' ) ) : ?>
    <a href="<?php echo esc_url( loopdues_login_url() ); ?>">Member login</a>
<?php endif; ?>

Protecting a custom template or endpoint the same way as a members-only page:

if ( function_exists( 'loopdues_can_see' ) && ! loopdues_can_see() ) {
    echo loopdues_teaser_html(); // login / join, or renew for lapsed members
    return;
}

Restricting to particular tiers, with names from the connected organization:

$tiers   = wp_list_pluck( loopdues_org()['tiers'], 'name', 'id' ); // [ 3 => 'Active Member', … ]
$allowed = loopdues_is_current_member( null, [ 3, 12 ] );

Listing current members, e.g. for a directory:

$members = get_users( [
    'meta_query' => [
        [ 'key' => 'loopdues_status', 'value' => LOOPDUES_CURRENT_STATUSES, 'compare' => 'IN' ],
    ],
] );

Linking to the member portal ("Renew", "Update my card", "Receipts"):

$portal = loopdues_org()['portal_url'] ?: loopdues_url( 'portal' );

Need more than the fields above, such as addresses or custom fields? Use the LoopDues REST API, or a webhook of your own in LoopDues. The plugin keeps only what it needs to decide access.

How it works

Releasing a new version

1. Bump the version in loopdues.php (the Version: header and LOOPDUES_VERSION) and Stable tag in readme.txt.
2. Add the changes to CHANGELOG.md and to the changelog in readme.txt.
3. Commit, tag vX.Y.Z and push with tags.
4. Build the zip and publish the release:

git archive --format=zip --prefix=loopdues/ -o loopdues.zip vX.Y.Z && zip -qd loopdues.zip loopdues/.gitignore
gh release create vX.Y.Z loopdues.zip -t "LoopDues X.Y.Z" --notes-file notes.md

Always name the asset loopdues.zip, so the "latest" download link keeps working.

License

GPL-2.0-or-later.