connect v1.0.0 Connect brings automation to Flarum 2 — outgoing webhooks, a scoped REST API, an in-app Rules engine, and an embedded Zapier experience. Free and MIT-licensed. Highlights Set up automations without leaving your forum. Connect embeds Zapier's official experience in your admin panel — browse 6,000+ apps and wire up "share new discussions to a Facebook Page", Slack, Discord, Mailchimp and more, with curated one-click recipes. In-app Rules engine. Trigger → conditions → actions, running entirely on your server (no external service). Auto-reply, add/remove tags, add/remove groups, or call a webhook — with 10 condition operators and match-all/any. Outgoing webhooks. HMAC-signed deliveries, REST Hooks (subscribe/unsubscribe), and automatic pruning of dead subscriptions. Scoped REST API + Zapier CLI app. Keys that act as a real user (read/write scopes); triggers for new discussions, replies, and users; actions to create discussions and replies. Works with Zapier, Make, IFTTT, and n8n. Fully translatable. Requires Flarum ^2.0 and PHP ^8.3, plus a running queue worker for webhooks and rule actions. View release on GitHub

typesense v0.2.1 What's Changed No changes Full Changelog: https://github.com/ernestdefoe/typesense/compare/v0.2.0...v0.2.1 View release on GitHub

page-builder 3.1.0 The Section Builder Building a page used to mean starting from a blank canvas and doing the design work yourself. This release flips that around: pick from ready-made sections that already match your forum's theme, and the design decisions are already made for you. New page → full-screen editor: your sections on the left, a live preview in the middle, settings on the right. The public page is rendered by the exact same code as the preview, so what you design is what visitors get. Twelve sections Hero · Feature grid · Articles · Image + text · Stats band · Latest discussions · Newest members · Testimonial · Pricing · Call to action · Logo strip · FAQ Every section drops in already wearing your forum's colours, fonts and corner rounding. There's no separate theme to configure. Four sections keep themselves current Latest discussions, Newest members, Articles and the Stats band read straight from your forum — real threads, real members, real counts. Place them once and never edit them again. Edit by clicking Click any text on the page and type: headlines, buttons, feature cards, pricing plans, FAQ rows, stat numbers. Items can be added and removed from the panel on the right. Guardrails you can loosen Each section exposes a small, safe set of controls — background, accent colour, alignment, spacing, plus per-section extras like the image side of a split or the layout of the Articles grid. Enough to make a page feel like yours, not enough to break the design. Articles, written or promoted Write an article from scratch, or promote any forum discussion into one, without leaving the editor. Both kinds show up in the Articles section, which can render as a grid or an auto-scrolling carousel. It follows your theme Sections and the editor read Flarum's own colour variables, so everything tracks light, light high-contrast, dark and dark high-contrast along with your forum, and picks up your forum's primary colour. Fully translatable Every string in the new builder — section names, labels, hints, seeded content — goes through the translator, with English shipped in locale/en.yml. Fixes and improvements A default Articles content type (with body, summary and cover fields) is created on install, so writing and promoting articles works out of the box. Article excerpts no longer leak upload markers or markdown into card summaries. The record editor's body field fills the form and keeps its padding, whether you use flarum/markdown or fof/rich-text; short fields stay short. An attach-image button in the body editor when fof/upload is installed. Real member avatars in the discussion feed and on article cards. Reply counts pluralise correctly. Notes The classic block designer, the freeform builder and content types are all unchanged and still available — the section builder sits alongside them as a faster way to build a page. Upgrading: run your usual composer update and php flarum migrate. Two migrations run: they create an Articles content type and its fields only if you don't already have them, so existing setups are left alone. View release on GitHub

hero-builder v1.4.0 The hero badge now shows each tag's icon/logo in its own colour on a solid white chip, instead of forcing every icon to white on a translucent chip (which turned full-logo tag icons — e.g. Font Awesome Kit conference/team logos — into washed-out white silhouettes). Icon takes the hero's primary colour, auto-darkened just enough to stay legible on white when the primary is light (hue preserved). Larger badge (92px tall) that widens to fit wide wordmark logos, with generous side padding. Glyph is flex-centred so icon-font baseline metrics can't push it off-centre. View release on GitHub

favorite-team 2.0.5 Fixed Enabling the extension no longer 500s the forum on Flarum 2. TeamRepository read its bundled teams.json via the Laravel File facade, which isn't reliably bound in Flarum's container — so it threw "A facade root has not been set" while the user API document was built, taking down the forum frontend the moment the extension was enabled (Flarum's error handler masked it, so logs only showed the facade error). It now reads the file with plain file_exists()/file_get_contents(). Regression introduced in 2.0.4. View release on GitHub

Logged. Here's a consolidated tracker of the Social Groups issues reported by @flavour1 (latest against v2.3.67 / Flarum 2.0.0-rc.3), so nothing gets lost: Permissions / visibility Guests could read group discussions despite members-only permissions — reported fixed in v2.3.67 (restricted access now works as expected). Opening a /groups/… URL as a guest now shows "Failed to load group." plus a "The requested resource was not found." error modal. Behavior is correct, but the modal is noisy and should be suppressed for the not-authorized/not-found case. Posting & replies Replying to a group post fails: 403 on social-group-posts with "You do not have permission to do that." — even though the admin Permissions table only exposes Create Social Groups and Edit & delete any social group, with no per-group "reply" permission surfaced. Standard discussion replies work fine. Editing posts as an admin fails (Failed to save edit. / "You do not have permission to do that."); only whole-discussion deletion is available. Composer / editor No TextEditor formatting controls render in the group composer footer — only third-party buttons (fof/upload, fof/polls) appear. The SGFeed composer area isn't auto-sizing: pasting enough content to fill the box makes it uneditable. Content rendering Links/image URLs that should embed don't render on submit — a full page reload is required to display them. Images uploaded via fof/upload don't appear in the SGMedia tab. SGMedia lightbox author link opens an auto-generated gallery discussion; inside it the edit textarea sizes dynamically, but editing/replying fail with "Failed to save edit." / "You do not have permission to do that." @ernestdefoe already flagged he'll dig into these this weekend, and is looking at whether embed support can be added. @flavour1 — if you can share the exact fof/upload and fof/polls versions alongside Social Groups v2.3.67, that'll help isolate the composer-controls and 403 reply issues.

onair-plus v0.1.5 Fixed Past Streams / VOD recordings wouldn't play (infinite spinner). The player routed recording .mp4 URLs through hls.js, which only understands HLS .m3u8 playlists — it failed silently and never attached the video. Progressive files (.mp4) now play natively; live HLS streams are unaffected. View release on GitHub

projects v1.5.1 Fixed Featured-project badge icon colour (reported by SergeyTS) — the badge icon inherited the theme's link colour at rest (correct only on hover) because a theme .PostUser a rule outranked the badge's own colour. The icon now uses an explicit colour that holds in every state. View release on GitHub

projects v1.5.0 Added "Made with AI" declaration — an optional toggle on the project form. When enabled, a disclaimer chip appears on the project card and a fuller notice on the detail page, so viewers know the work was AI-assisted. Fully translatable. Fixed Featured-project badge clash (reported by SergeyTS) — the featured badge next to the username reused fof/badges' .PrimaryBadge class, causing the two badges' styles to conflict. It now uses its own standalone .ProjectFeaturedBadge class with self-contained styles, so the two render independently. View release on GitHub

projects v1.4.5 What's Changed fix(filters): keep filter dropdown label + chevron on one line Full Changelog: https://github.com/ernestdefoe/projects/compare/v1.4.4...v1.4.5 View release on GitHub

respawn 3.0.3 What's Changed Translate the player card and rarity tiers legend fix(tags): drive TagLabel outline + text from --tag-bg so labels stay readable on dark Full Changelog: https://github.com/ernestdefoe/respawn/compare/3.0.2...3.0.3 View release on GitHub

projects v1.4.4 What's Changed SergeyTS follow-up: editor toolbar/resize, byline, links box, filter dropdowns Full Changelog: https://github.com/ernestdefoe/projects/compare/v1.4.3...v1.4.4 View release on GitHub

projects v1.4.3 The Details editor toolbar now spreads its buttons evenly across the full width, with no icons overflowing the editor. View release on GitHub

projects v1.4.2 The Details editor now spans the full width of the form (it was shrinking to fit the placeholder), lining up with the other fields. View release on GitHub

projects v1.4.1 Follow-up UI polish from SergeyTS's feedback on v1.4.0: Details editor — inner padding (text no longer against the edges), taller box, and a wrapping toolbar so the formatting tools fit on narrow screens. Links section — more spacing between link rows. Author separator — the middot now aligns with the author names (baseline alignment; avatars stay centred). Dropdowns — now a Flarum-styled dropdown menu (built from Flarum's own Dropdown), instead of a native <select> whose popup used the browser's chrome. View release on GitHub

projects v1.4.0 Full 15-item feedback batch from SergeyTS, plus a rich Details editor. Forum Co-authored projects now show on the co-author's profile Details field uses Flarum's composer editor (formatting toolbar) instead of a plain textarea Oversize cover-image uploads show feedback again; size hint added "Feature on profile" is now instant (optimistic) Author separator (·), required-asterisk visibility (+ on Title), link-button wrapping, param name/value spacing, Links-section styling Scroll position restored when returning from a project Core Flarum Select dropdowns Linked discussion accepts a pasted URL or a bare ID Admin Reorder tags / parameters / buttons (drives display on form, cards and pages) Publish-badge picker rebuilt so its options actually populate View release on GitHub

importer v0.1.0 First release of the Flarum 2 importer / converter. Migrate into Flarum 2 from: phpBB 3.x · vBulletin 3/4 · vBulletin 5/6 · XenForo 1.x/2.x · MyBB 1.8 · SMF 2.0/2.1 · Vanilla · NodeBB · Invision Community (IP.Board) · Discourse · Convoro. Highlights Runs on shared hosting — a resumable, batched step machine driven from the browser; no queue worker or SSH required, and it can't time out. Uses a queue worker automatically if one is present. Two ways in — connect to a live source database, or upload a mysqldump/SQLite dump. Resumable — progress, cursors and source→Flarum id-maps are persisted, so a run survives a closed tab or dropped connection. Faithful content — BBCode / HTML / Markdown convert to Flarum's native rich-text format (bold, italics, links, quotes, lists, code). Relations preserved — members (bcrypt logins kept where possible), tags, discussions, first/last-post pointers, comment & participant counts. Categories import as tags when flarum/tags is installed. Everything is driven from the admin panel, with a live progress bar. A CLI (php flarum importer:run) is included for very large migrations. View release on GitHub

Importer / Converter for Flarum 2Migrate an existing forum into Flarum 2 — from phpBB, vBulletin (3/4/5), XenForo, MyBB, SMF, Vanilla, NodeBB, Invision, Discourse, or Convoro. Everything is driven from the admin panel: pick a platform, connect to its database (or upload a dump), test it, then run the import in small batches with a live progress bar — so even a large forum won't time out. Ported from the Convoro importer suite. Members keep their passwords where possible (bcrypt hashes are copied straight across; other formats are randomised so the member simply resets on first login). Post bodies are converted to Flarum's native rich-text format, so BBCode / HTML / Markdown comes across as real formatting — bold, italics, links, quotes, lists and code. Runs on shared hostingNo queue worker and no SSH required. The import runs as a loop of small "step" requests straight from your browser, each processing one bounded batch and returning — so it can never hit a web timeout. Progress and the source→Flarum id-maps are persisted in the database, so if the tab is closed or the connection drops, reopen the page and it resumes exactly where it left off. If you do have a queue worker (e.g. fof/redis), the import is handed to it and runs fully in the background instead — either way it's safe. The admin areaThe whole tool lives on the extension's settings page. 1. The wizardPick a source platform, then either connect to a database (host, port, database name, username, password, and table prefix) or upload a database file (a mysqldump .sql/.sql.gz, or a SQLite file) for hosts that only hand you a dump. Nothing is written until you start. 2. Test the connectionTest connection validates the credentials, confirms it really is the platform you picked, then reports exactly what it found — here 21 Users, 4 Categories, 30 Topics, 371 Posts — so you know it will pull the right data before committing. Start import only lights up once the test passes. 3. Watch it runStart import kicks off the batched run and shows a live progress bar with the current phase and running totals — categories, members, topics and posts — updating as it goes. When it finishes you get a summary of everything imported, and can start another. Supported sources| Platform | Notes | |----------|-------| | phpBB 3.x | BBCode posts; bcrypt passwords copied across | | vBulletin 3 / 4 · vBulletin 5 / 6 | one option covers both — vB5's node schema is auto-detected | | XenForo 1.x / 2.x | BBCode posts; XF2 bcrypt passwords copied | | MyBB 1.8 · SMF 2.0 / 2.1 | BBCode posts | | Vanilla · NodeBB | Markdown / mixed formats; NodeBB reads its Redis store (needs the redis PHP extension) | | Invision Community (IP.Board) | HTML posts, quotes & mentions cleaned up | | Discourse | PostgreSQL source (needs pdo_pgsql) | | Convoro | Convoro → Flarum; bcrypt passwords copied, so members keep their logins | Categories are imported as tags (requires flarum/tags); if tags aren't installed, discussions and posts still import, just untagged. How it worksTimeout-proof — the run is a resumable state machine; each request processes one small batch and returns, so memory stays flat and nothing runs long enough to time out. Works with or without a queue worker. Resumable — progress, cursors and the source→Flarum id-maps live in the database, so a run survives a closed tab, a reload, or a dropped connection. Faithful content — post bodies go source → HTML/Markdown → Flarum's formatter, landing in Flarum's native stored format so they render as proper rich text. Relations preserved — members, tags, discussions, first/last-post pointers, comment counts and participant counts are all rebuilt. Requirements & tipsImport into a fresh Flarum for the cleanest result. A queue worker is optional — the import runs from the browser without one. If you have fof/redis + a worker, it runs in the background instead. There's also a CLI for very large migrations or scripting: --host=127.0.0.1 --database=my_old_forum --username=root --password=secret --prefix=phpbb_ # add --test to only check the connection and show counts``` ## License MIT © ernestdefoe

projects v1.3.1 Follow-up to SergeyTS's v1.3.0 feedback. Fixed Badge awards now notify the recipient. The award goes through fof/badges' BadgeAwarder (which sends the "you earned a badge" notification, runs the badge's actions, and fires BadgeAwarded) instead of a raw pivot attach. Falls back to the direct attach on older fof/badges so the award still lands either way. The "award on publish" badge is now a real picker — a dropdown of badge names (loaded from the config endpoint), matching the per-category badge picker. No more raw numeric IDs; choose "None" to disable. Included (already in the 1.3.0 source, ensured here for installs that pre-dated it) Parameter (custom field) descriptions — add them in the field editor; they render under the parameter's name in the submission form. Per-category badge picker + tag descriptions on hover. Update: composer update ernestdefoe/projects then php flarum cache:clear. View release on GitHub

social-groups v2.4.11 Performance & conventions audit batch — no behaviour change, all query hygiene. Fixed Post-header primary-group chip no longer N+1s. sgPrimaryGroup moved into an injected UserResourceFields class and its relations are eager-loaded on the User/Post/Discussion endpoints (mirroring core's user.groups), so a 20-author page no longer fires ~60 correlated lookups. Group directory teasers batch-load. recentDiscussions reads an eager-loaded relation instead of one LIMIT query per group card. Member list canRemove/canMute memoized. The per-(actor, group) moderator lookup runs once per page instead of 40 correlated subqueries; endpoint policies are unchanged. Poll voting eager-loads the discussion's group (one fewer SELECT). Migrations 000003/000020 now document why the raw closure form is intentional. Update: composer update ernestdefoe/social-groups then php flarum cache:clear. View release on GitHub

bespoke 2.0.37 What's Changed fix: record discussion views — read {id} from route params, not query string refactor: injected API field classes; gate bespokeViews to grid mode refactor: split WidgetDataController into per-concern query services chore: use Migration::createTableIfNotExists helper; extract compiler block() Full Changelog: https://github.com/ernestdefoe/bespoke/compare/2.0.36...2.0.37 View release on GitHub

digest-mail 2.2.0 Full translatability (i18n) Every user-facing and admin string now goes through the translator — the extension is 100% translatable. Drop in a locale file for any language and the digest emails, unsubscribe pages, user settings, and the entire admin panel render in that language. Digest email: period words ("this day/week/month"), reply/post/vote/etc. counts, discussion meta ("Last reply by…", "Started by…"), the header badge, the "Visit" button, and the footer are now translated. Relative times ("1 hour ago") now localize with the recipient's language — Carbon's locale is set per recipient alongside the translator, so dates no longer stay English in a translated digest. Admin panel: settings, statistics, digest order, and the full server / queue / cron documentation are fully externalized. locale/en.yml ships every key; other locales (fr.yml, etc.) can be filled in by translators. Also included since 2.1.3 Fix digests failing to send — unguard UnsubscribeToken mass assignment (was 2.1.5). Audit fixes — honor disabled-frequency toggles; trim the leaderboard NEW-badge query (was 2.1.4). Migrating from resofire/digest-mail This is a drop-in-compatible fork — same database schema, idempotent migrations, and no subscriber data lost when you switch. See the "Migrating from resofire/digest-mail" section in the README for the full steps. Install / update php flarum migrate php flarum assets:publish php flarum cache:clear``` [View release on GitHub](https://github.com/ernestdefoe/digest-mail/releases/tag/2.2.0)

Typesense Search for FlarumA free, drop-in Typesense search driver for Flarum 2 — fast, typo-tolerant full-text search across discussions, users and posts that anyone can set up in a few minutes. Flarum 2 shipped a pluggable search architecture; this extension implements a Typesense driver for it. Text searches are answered by Typesense; everything else (filtering, browsing, permissions) stays exactly as Flarum does it. You choose per resource which searches Typesense answers. Why it's safe by designTypesense is only ever asked for candidate discussion IDs and their ranking. Which results a given user may actually see is decided entirely by Flarum's own whereVisibleTo (including tag restrictions) — never by Typesense. The search server holds no authorization logic, and the browser never talks to it. Your API key is stored server-side and is never exposed to visitors. RequirementsFlarum ^2.0 A running Typesense server (self-hosted is a single binary or Docker container, or use Typesense Cloud) Installcomposer require ernestdefoe/typesense Run Typesense (self-hosted example) -v typesense-data:/data typesense/typesense:27.1 \ --data-dir /data --api-key='CHANGE_ME' --enable-cors``` ## Set up 1. **Admin → Typesense Search.** Enter the host, port, protocol and API key, then **Save**. 2. Click **Test connection** to confirm Flarum can reach the server. 3. Click **Rebuild index** (or run `php flarum typesense:index`) to populate the index from your existing discussions. 4. Turn on **Use Typesense for discussion search** and save. That's it — searches for discussions are now served by Typesense. Search tabs that Typesense answers show a small **Powered by Typesense** badge in the search modal, so you can see at a glance which searches are using the driver. Only that on/off fact is sent to the browser — connection details and the API key stay on the server. ### Console ```php flarum typesense:index # build / refresh the index php flarum typesense:index --flush # delete the index``` ## How indexing works * Each discussion is one Typesense document: its title plus the concatenated text of its visible comment posts. * Creating, editing or deleting a discussion or post re-indexes the affected discussion automatically through Flarum's queued indexing pipeline. * **Configure a real queue driver** (`redis`, `database`, …) in production so indexing and rebuilds run in the background rather than inline on a web request. Several forums can share one Typesense server safely — collections are namespaced by a prefix (set one, or it's derived from your forum URL). ## What's indexed Everything Flarum can full-text search, each in its own namespaced collection: * **Discussions** — title + the concatenated text of visible comment posts. * **Users** — username and display name. * **Posts** — individual comment post text (post-scoped search). Each is toggled independently in the admin, so you can send discussion search to Typesense while leaving users or posts on the database, or run all three through it. (Groups and access tokens have no full-text search in Flarum, so they always stay on the database driver.) ## License [MIT](./LICENSE.md) © Ernest Defoe

Topic MapA Flarum 2 extension. A Discourse-style topic map under the first post of busy discussions: views, likes, outbound links, top participants and estimated read time at a glance — plus a Top Replies panel that jumps you straight to the most-liked answers. FeaturesStats bar on the first post once a discussion passes a reply threshold (admin setting): views · likes · links · participants (with avatars) · minutes-to-read. Top Replies — the most-liked replies with author + excerpt; click one to jump to that post. Works with flarum/likes or fof/reactions (the stat relabels itself "reactions"); hides when neither is installed. Links panel — the discussion's outbound links grouped by URL, tap the links stat to expand. View counting built in (guests count, one per browser session, visibility-checked). On forums running ernestdefoe/bespoke, Bespoke's view counter is used instead — one source of truth, never double-counted. Everything is computed server-side and cached; a 400-post scan cap keeps huge topics cheap. Fully translatable. Installation php flarum migrate php flarum cache:clear``` ## Updating ```composer update ernestdefoe/topic-map php flarum migrate php flarum cache:clear``` ## Links * [Packagist](https://packagist.org/packages/ernestdefoe/topic-map) * [GitHub](https://github.com/ernestdefoe/topic-map)

GitHub README Paste — Flarum 2 extensionPaste a GitHub repo URL into the Flarum composer and the URL is auto-replaced with the rendered README markdown. How it worksUser pastes https://github.com/owner/repo into any composer (new discussion, reply, edit, private message). The frontend recognizes it as a GitHub repo root URL and intercepts the paste. It calls POST /api/gh-readme/fetch on the Flarum backend. The backend fetches https://api.github.com/repos/{owner}/{repo}/readme, decodes the base64 payload, rewrites relative image / link / anchor URLs against the repo's HEAD branch on raw.githubusercontent.com, and returns the processed markdown. The frontend replaces the URL in the composer with the README markdown. The user can edit freely from there. Subsequent pastes of the same repo are served from a 10-minute server-side cache so a popular forum doesn't burn GitHub's rate limit. Works with both composer types| Composer | Behavior | | --- | --- | | Default Flarum (textarea + flarum/markdown) | URL replaced inline by the markdown source. The post renders as formatted markdown at display time. A visible italic "Loading…" marker shows in the textarea during the fetch. | | fof/rich-text (Tiptap WYSIWYG) | URL replaced by rich nodes — headings, paragraphs, lists, code blocks, blockquotes, images all appear formatted in the composer immediately. A toast notification shows during the fetch (no inline marker — finding a specific text node inside a ProseMirror document is brittle). | Detection is automatic via the presence of editor.editor on the active driver. No setting needed. Install php flarum cache:clear``` Then enable in **Admin → Extensions → GitHub README Paste**. `flarum/markdown` is a `suggest` dep — without it the inserted markdown ends up in the post but renders as plain text rather than formatted headings/lists/code blocks. ## Configure **Admin → Extensions → GitHub README Paste:** * **GitHub Personal Access Token** *(optional)* — raises GitHub's API rate limit from 60/hour-per-IP (unauth) to 5000/hour. No scopes required for public repos. * **Cache duration (minutes)** — how long the server caches each README before refetching. Default 10. Clamped 1–60. ## URL shapes accepted | URL | Behavior | | --- | --- | | `https://github.com/owner/repo` | ✅ expanded | | `https://github.com/owner/repo/` | ✅ expanded | | `https://github.com/owner/repo.git` | ✅ expanded (strips `.git`) | | `https://www.github.com/owner/repo` | ✅ expanded | | `https://github.com/owner/repo/tree/main` | ❌ left as-is (use the root URL) | | `https://github.com/owner/repo/blob/main/file.md` | ❌ left as-is (file links, not repos) | | `http://github.com/owner/repo` | ❌ rejected (must be https) | | `https://gitlab.com/owner/repo` | ❌ not GitHub | ## Security notes * Strict URL allowlist (`github.com` host only). * Owner/repo regex-allowlisted to GitHub's own charset. * The backend never fetches the user-supplied URL directly — it constructs the API call from validated owner/repo segments. SSRF surface is the GitHub API host only. * Response body capped at 2 MB. * 10s connect + 15s total request timeout. * TLS verification on. * Endpoint requires an authenticated Flarum actor; throttled by Flarum's standard per-actor API throttler. ## License MIT — see [LICENSE](LICENSE).