FAQ

Does Memberz handle logging in?

No. Craft does. Use Craft's own users/login action, or its {{ craft.app.user }} API, exactly as you would without this plugin.

What about Google or GitHub sign-in?

That is Verbb Auth, and the two work together with nothing to configure. Auth creates and authenticates the account; Memberz renders the profile, the account area and the directory around it. An account that arrived through Auth gets a profile slug the first time one is asked for, like any other.

Can I charge for membership with this?

No, and that is deliberate. Subscriptions, tiers, content gating and drip content are Headcount. Memberz holds no price, no plan and no paywall.

They are built to sit on the same site: Headcount decides what a member may read, Memberz draws the account area around it.

Why won't my registration form work?

Almost always one of Craft's own settings, under Settings → Users → User Settings:

• Allow public registration is off. Every submission is refused and the refusal is logged. Memberz will not work around it.
• Use email as username is off and your form has no Username row. Memberz refuses to save such a form, so this should surface while you are building it.

Then check the form's spam settings: a minimum seconds on screen that is too high refuses genuine submissions, and a honeypot input removed from a custom template means the check never sees the field it is looking for.

Why can't I put a Matrix field on a form?

Because Memberz renders plain front-end HTML rather than Craft's control-panel inputs, and there is no honest plain-HTML rendering of a Matrix field.

Craft's own inputs pull in its asset bundles and JavaScript and assume the control panel's stylesheet; several do not work outside it. A finite list of field types that genuinely work is a better bargain than a fallback that renders a text box for a Matrix field and loses what the member typed. See Forms for the list.

Why is a private profile a 404 rather than a 403?

Because a 403 confirms the account exists. That turns the profile URL into a way of testing whether a given username is registered, and for a member who set their profile private, being discoverable is exactly what they asked not to be.

A member hid a field, but their username is still in the profile URL.

It has to be — a link to a profile has to say which profile it is. If that matters for your site, set Profile URLs are built from to A random string, and new members get an opaque slug. Existing slugs are never rewritten, because a changed profile URL is a broken link on someone else's site.

Does Memberz send member data anywhere?

No. There is no Gravatar call, no analytics, no licence phone-home. The photo fallback is drawn on your server. See Member photos.

Can members delete their own accounts?

Not through Memberz. Account deletion in Craft has consequences Memberz cannot see — content transfer, Commerce orders, whatever else is related — and a free profile plugin is the wrong thing to be making that decision. Members can hide their profile and remove themselves from directories; deletion goes through you.

What happens if I uninstall it?

Accounts, their fields and their photos are untouched — they are Craft's data and Memberz never kept a copy. What goes is the memberz_profiles table, which holds members' privacy preferences and slugs, and the forms and directories in project config.