| You have | Go to |
|---|---|
| A bug — something behaves incorrectly | Open an issue |
| An idea or a missing capability | Open an issue |
| A security vulnerability | Not an issue — see SECURITY.md |
| A "how do I…" question | The docs below, then an issue if they do not cover it |
| A commercial/support enquiry | https://memberistic.com |
docs/INSTALL.md— installation and first-run setupdocs/UPGRADE-2.0.md— upgrading from 1.xdocs/INTEGRATIONS.md— WooCommerce, Stripe, booking, POS and the rest, and why they are all off by defaultdocs/HOOKS.md— actions and filters for developersdocs/entitlements.md— how access decisions are madeREADME.md— shortcodes, REST routes, capabilities
Include all of these — without them a report usually cannot be reproduced:
- Versions. Memberistic version, WordPress version, PHP version, and (if involved) WooCommerce and theme.
- Steps. Numbered, from a state someone else can reach.
- Expected vs actual.
- Scope. Does it happen with all other plugins deactivated and a default theme? That single check resolves a large share of reports.
- Errors. The PHP error log entry and/or the browser console output. Redact keys, tokens and member personal data before pasting.
For anything touching payments, include whether Stripe was in test or live mode, and the event type — never the secret key.
This is maintained alongside other work. Issues are triaged in order of impact: data loss and access-control problems first, then payment correctness, then everything else. There is no support SLA on the free plugin, and no commercial support tier is currently on offer.