Start a Forum You Fully Own on WordPress With Jetonomy

A forum you fully own is one that runs on your own WordPress site, keeps every topic and member in your own database, and has no company between you and your members that can change the rules. With Jetonomy that’s a plugin install, a three-step wizard and a first space. With BuddyNext added, members also get profiles and a feed. You can have the first version live in an afternoon.

What takes longer is deciding what you want the room to be. This post follows a first week in order, from the moment you pick a home for it to the point where you add the social layer, and marks the places where owning it means doing some work yourself.

Key points

• Jetonomy stores the forum in its own wp_jt_ database tables on your site, not in a hosted service.
• The free plugin comes from wbcomdesigns.com as a ZIP, not from the WordPress plugin directory.
• The setup wizard takes about two minutes. You choose a URL, a space type and a first space.
• BuddyNext is optional. Add it when members start asking for profiles and a feed.

Day one morning: decide where it lives

Before you install anything, settle two small questions. They’re cheap now and annoying later.

What’s the address? By default Jetonomy puts the forum at yoursite.com/community/. You can change that word to forum, hub, discuss or your own brand name, and you can change it again later, because Jetonomy flushes the permalink rules when you save. There’s also a setting that serves the community home on your site’s front page, for sites where the forum is the whole point.

Is it a forum or something else? Jetonomy has four space types: Forum, Q&A, Ideas and Show & Tell, which the admin also calls Feed. A forum is threaded talk. Q&A lets the asker accept one answer. Ideas lets members vote and moves each idea through roadmap lanes. Feed is for short updates. You can mix them, one per space, and our post on picking a space type helps if you’re torn.

Start with one. A forum with a single busy space beats a forum with eight empty ones every time.

Day one: install it, and know why it’s a ZIP

Here’s the first thing that trips people. Jetonomy isn’t in the WordPress plugin directory, so searching for it inside wp-admin finds nothing. The free plugin is on the wbcomdesigns.com downloads page.

There are three ways in, and they all work:

• Upload the ZIP under Plugins, Add New Plugin, Upload Plugin, then activate.
• With WP-CLI, point at the ZIP file, not a name: wp plugin install /path/to/jetonomy.zip --activate. A bare name looks in the directory and fails.
• With Composer, require wbcomdesigns/jetonomy and activate it. The site needs composer/installers to put it in the plugins folder.

Check the basics first. You need WordPress 6.7 or newer, PHP 8.1 or newer, and MySQL 5.7 or MariaDB 10.4. Any theme works. BuddyX gives the best result with no extra setup, but it isn’t required.

What you’ve just made

Activation does real work, and it’s worth knowing what, because this is the part you now own.

Jetonomy doesn’t use WordPress posts. It creates its own tables, all starting with wp_jt_, for categories, spaces, posts, replies, votes, profiles, notifications and the rest. That’s deliberate. A forum with tens of thousands of replies behaves very differently when it isn’t squeezed into the posts table.

It also registers its own capabilities and maps them to your existing WordPress roles, flushes the permalinks, and schedules six background jobs through WP-Cron. They handle things like trust-level promotion, lifting expired restrictions and publishing scheduled posts.

None of that lives on a vendor’s server. It’s in your database, in your backups, under your hosting account. That’s what we mean by owning it.

Day one, ten minutes later: the wizard

A blue notice asks you to run the setup wizard. It has three steps, and you can leave and come back.

Step one is the community URL and the default space type. Step two is the first space, and here you choose a path.

Path A is for a real site. You name a category (the default is General) and a space (the default is Community Discussion), and Jetonomy creates it as public with an open join policy. Path B loads sample data, which is the right choice on a staging copy or a throwaway test, and the wrong one on the site you plan to show people.

Step three finishes up. When it’s done, the forum exists and you can open it as a member would.

If you’d like to look around before installing anything, there’s a free sandbox that launches a disposable Jetonomy site in your browser. It’s for clicking around, and it isn’t a community to join.

Day two: shape the rooms before you fill them

A space is one focused area, such as General Discussion, Product Feedback or Help and Support. Every space sits inside a category, and the categories are what members see as the sections of the community home. A space with no category won’t appear in the navigation at all, so create the category first.

Our advice matches the docs: start with three to five spaces and add more when people ask. Too many spaces early on spreads a small group thin, and every quiet room makes the forum feel emptier than it is.

Each space has two settings that decide who gets in. Visibility is Public, Private or Hidden. Join policy is Open, Requires Approval or Invite Only. Leave both alone and a new space is public and open, which is right for a first space. Hidden visibility always forces Invite Only, which makes sense, since nobody can request a room they can’t see.

One trap worth knowing before you build. Each space gets a URL slug made from its title, in the form /community/s/your-slug/. You can edit the slug, but if you change it after posts exist, links people have already shared will break. Settle the names now.

You can also let people you choose create spaces from the front end, without giving them wp-admin access. That’s useful later, when a trusted member wants to run a corner of the forum. It’s overkill on day two.

Day three: write the room’s rules before anyone arrives

An empty forum isn’t a technical problem, it’s a human one. Before you invite a single person, write a few plain lines on what the room is for, what gets removed and who decides.

Pin them in the first space. Members read a short, plain statement far more often than a policy page. Something like “this is for people running small WordPress shops to compare notes, and we remove sales pitches” is enough.

Then decide how people get in. A public space with an open join policy is the default. If the community is for customers or members only, that’s a different shape, and our post on a private forum for WordPress covers invites, join requests and paid access.

Day four to seven: invite ten people, not a thousand

Resist the launch email to your whole list. Invite ten people you know will post. Ask each of them one real question in the first space, and answer anything that appears within the day.

Why the small start? Because a forum earns its first real members through the replies they get, not through the announcement. A newcomer who posts and hears back within hours comes back. A newcomer who posts into silence doesn’t.

While you’re doing this, keep an eye on the admin dashboard: new members, new topics, and how many topics have no reply. That last number is the one that matters in week one. Aim for zero.

When the first spam arrives, and it will, you’ll want a routine. We wrote a weekly moderation workflow for exactly this, and the trust levels post explains how newer members are limited until they’ve earned more room.

When members start asking for profiles and a feed

Somewhere in week two, someone will ask whether they can follow people, or see what’s new in one place, or look at another member’s page. That’s the signal that you want a social layer, and it’s what BuddyNext is for.

BuddyNext is a free plugin that adds member profiles, an activity feed and notifications. Jetonomy and BuddyNext are built to work together, and the pairing needs no settings. Jetonomy notices BuddyNext, and a few things change on their own.

What the free BuddyNext plugin does with your forum, from its Jetonomy bridge:

• A new discussion appears in the BuddyNext feed as a link card pointing back to the forum.
• Discussions are added to BuddyNext’s search, and @mentions in them are picked up.
• Reply, mention and accepted-answer notifications reach the BuddyNext bell.
• A Discussions item appears in the navigation, a Discussions tab can show on a space, and a member’s profile carries a count of their discussions.

On the Jetonomy side, it takes on BuddyNext’s colours, fonts and dark mode, and it drops its own header and navigation so you don’t see two of them. That needs BuddyNext 1.0 or later with the community hub switched on.

A few honest edges, so you don’t promise members more than they get.

Forum notifications show in the bell but aren’t emailed through BuddyNext. Jetonomy keeps the text, the visibility rule and the email, and BuddyNext never sends mail on its behalf. And if you’re running Jetonomy Pro, its private messaging steps aside when BuddyNext is active, so members get one inbox and not two.

What you actually own, and what you now have to run

Here’s the short version of the trade you’ve made.

You own:

• Every topic, reply, vote and member record, in your own tables.
• The URL, the look and the rules.
• Your members’ email addresses, to use under your own privacy policy.
• The ability to export and erase one person’s data through the standard WordPress privacy tools, which Jetonomy registers with.
• A forum with no per-member fee and no commission on anything.

You now run:

• Hosting, updates and backups. If your host loses the database and you’ve no backup, the forum goes with it.
• Spam and abuse. Nobody else is moderating for you.
• Email delivery. If your site can’t send mail reliably, members won’t get their notices.
• The first thirty members, by hand.

None of that is a reason not to. It’s the price of the other list. But it’s better to see both columns on day one than to find the second one in week six.

When a hosted forum is the better call

We’d rather say it than have you find out. If you don’t want to think about servers at all, a hosted forum takes that job away. If you need to be live this afternoon and have no one to look after a site, the same goes. And if you already have a hosted community with active members, moving is a project of its own. Our post on moving a forum off a hosted platform covers what to save and what no importer can bring.

The WordPress route pays off when the conversation is something you plan to keep for years, and you’d rather the keys were yours.

Questions people ask before they start

Is Jetonomy free? Yes, there’s a free plugin with forums, Q&A, ideas and the feed space type. Pro adds more, such as anonymous posting with an audit trail, and the pricing page has the details.

Do I need BuddyNext? No. The forum works on its own. Add BuddyNext when members want profiles, a feed and a notification bell.

Can I change the forum URL later? Yes. Change the community base URL in Jetonomy’s general settings and the community links update.

Will it slow down my site? The forum keeps its data in its own tables rather than the posts table, which is built for large conversations. Any plugin adds some load, so test with your own host and a realistic amount of content.

What if I already use bbPress or wpForo? Activate Jetonomy first and finish setup, then use the importer under Jetonomy, Import. Your existing data isn’t touched until you start an import. The migration guide walks through it.

If you’d like the longer reference version of all this, the guide to adding a forum to WordPress is the page to keep open while you work.