How Do You Get Support for Flarum in the Flarum Community Forum?

Flarum Community (discuss.flarum.org) is the official community support forum for Flarum, the open-source forum software. It's where you ask questions, report problems, and get help from other users and extension developers. It is not a product homepage, a download page, or a login portal, and it is not a ticketing system — support there is community-driven, so the quality of the answer you get depends heavily on how you frame the question. Use it when you have a Flarum usage, installation, or extension-development problem and you're willing to search first and post details.

What the Flarum Community forum is (and isn't)

It is	It isn't
The official community discussion and support board	A guaranteed-response help desk
A place to search past answers before posting	A download or purchase page
A place to follow release and extension announcements	A private account or billing portal
A place where extension authors answer questions about their own extensions	A substitute for reading the documentation

The board's front page is a running list of discussions. Alongside support threads you'll see release and announcement topics — for example "Flarum 2.0.0-rc.8 released," "Flarum 1.8.20 Maintenance Release," and "Introducing the Official Extension Discovery (Beta)" — plus extension threads such as "FoF Bookmarks," "Verified - User verification," and "Rank Banner - Group rank badges under usernames." That mix matters: some of your answers already exist as announcements rather than as replies to a question.

Before you post: search and self-check

Most "it's broken" reports are already answered. Do these first:

Search the forum for your exact error text and your extension name. The board is indexed, and version-specific issues usually have a thread.
Check the release announcements for your version. If you're on a release candidate or an older maintenance line, a known issue may already be documented.
Check extension compatibility threads. Flarum 2.0-era discussions (for example "Friends of Flarum — 2.0 Compatibility Progress") exist precisely because extensions lag behind core releases. If your problem started after a core upgrade, an incompatible extension is a prime suspect.
Reproduce it on a clean install if you can. This tells you whether the cause is core, an extension, or your environment.

If the search turns up nothing, you now have a much better question to ask.

What to include in a support post

A post that gets answered quickly contains, in roughly this order:

Flarum version — exact, including any -rc or patch number.
PHP version and how Flarum is installed — Composer, a one-click installer, Docker, shared hosting, etc.
Full extension list with versions. Extension conflicts are the single most common cause of odd behavior.
The exact error — copy the message and the stack trace, not a paraphrase. Use a code block so it stays readable.
Steps to reproduce — numbered, starting from a known state.
What you already tried — including the clean-install test above.
Expected vs. actual behavior — one sentence each.

A vague "my forum is broken, help" post usually gets either silence or a request for the information you should have included. A post with the list above often gets a diagnosis in the first reply.

Where different kinds of questions belong

Using Flarum (permissions, tags, notifications, theming): general support discussions on the board.
Installing, upgrading, or migrating: support discussions, but state your hosting environment and whether you have shell/Composer access — the answer differs completely between a VPS and shared hosting.
Extension development (writing or debugging your own extension): the development-oriented discussions, where other developers and extension authors are active.
A specific third-party extension: post in that extension's own discussion thread. The author is the person most likely to know, and other users of the same extension will see it.
Bug reports against Flarum core: the community board is where you confirm whether others see it too; reproducible core bugs are what actually get fixed.

Community support vs. paid support

The Flarum Community forum is free, public, and best-effort. Nobody is obligated to answer, and response times vary with how many people are active and how well you've described the problem. There is no service-level agreement, no private channel, and no guarantee that a maintainer will see your thread.

If you need a guaranteed response, a private channel, or help with a customized production forum, that is a different arrangement than what the community board provides — treat the board as peer help, not as a contract. For anything involving credentials, private data, or a security issue, don't post it publicly; look for the project's designated private reporting route instead.

Common pitfalls

Posting the same question in multiple threads. It fragments the answers and gets ignored. One clear thread is better.
Bumping repeatedly. Give it a day; if there's no reply, add new information (a log, a test result) rather than just "anyone?"
Assuming a release candidate is stable. If you're running an -rc build, say so — advice for a stable release may not apply.
Leaving the thread unresolved. If you fix it yourself, post what worked. That's what makes the next person's search succeed.