Link Robins Blog — Ghost-style blog with a built-in newsletter

KBExit

Silvestrus if this is what everyone wants. I'll do a rebuild..

KBExit

I'll try and get the rebuild shipped before my trip Wednesday. This rebuild will include migrations from the Blog posts to Discussions so you're not penalized for using this extension with it's current structure.
I hope this will make everyone happy 🙂

GreXXL

If the old extension is a target it’s worth mentioning that it’s planned to move and upgrade the old blog extension within @FriendsOfFlarum. Maybe efforts can be combined to avoid using precious development resources to have two things existing in parallel doing the same thing.

KBExit

GreXXL I personally never liked the way the original blog extension worked. If necessary, I can change the name of my extension as well moving forward if preferred. My end result is something that visually looks completely different. I started with it being its own thing, but it seems everyone wants it to use discussions as the source of truth.

GreXXL

There is no need for changing the name. I was just pointing out that extensions should remain different in order to make sense the maintenance effort. Everything is fine if this is a different extension then the origianl one.

KBExit

After thinking about it, it's not worth it to switch this one. It will be too much like the other, that it's not necessary and could further complicate and break due to schema changes.

KBExit

Blog — v1.1.0 linkrobins/blogreleases/tag/v1.1.0

Performance

Blog listings no longer issue N+1 queries. The index/category pages used to fire ₃ extra database queries per post (commentCount + discussionId) and one COUNT per category. These are now batched into one query each for the whole page via eager-loading. On a 12-post index that's ₂ queries instead of ₃₆.

Removed

Dead BroadcastPostController (it had no route; newsletters already auto-send on publish).
Dead, unregistered Content/BlogPost handler.
Orphaned comment-report permissions left in the database after the reporting feature was removed (cleanup migration — run php flarum migrate).

Internal / conventions

Added a webpack + TypeScript build pipeline; the frontend now compiles to js/dist/.
The four server-side content handlers now log failures instead of swallowing them silently.
Service-provider hooks use dependency injection instead of the service locator.

i18n

The Markdown editor toolbar (tooltips, inserted snippets, prompts) and a couple of admin strings are now translatable.
Fixed the category "slug" help text, which rendered as a raw key.

UI

The category editor modal now has consistent field spacing matching the post editor.

KBExit

linkrobins/blogreleases/tag/v1.1.2

Feature

The blog post body editor now uses Flarum's Markdown composer editor (toolbar + @mention autocomplete), matching the rest of the forum, with a plain-textarea fallback. Image uploads insert through the editor; the post's Publish / Save-draft buttons remain the actions.

Security hardening (audit)

coverImageUrl now rejects non-http(s) schemes server-side (mirrors coverImageCreditUrl), closing a latent XSS foot-gun.
visibility is constrained to public/members; unknown values fall back to public.

A full security & performance audit found authorization, IDOR, SQL-injection, mass-assignment, and XSS all sound, N+1 queries properly eager-loaded, and listing indexes adequate.

KBExit

linkrobins/blogreleases/tag/v1.2.0

Author blog posts with Flarum's real composer

Writing and editing blog posts now happens on a full page (/blog/compose) instead of a modal, and the body is written in Flarum's real docked composer — so FoF Rich Text, FoF Upload, @Mentions and Emoji all work in the post body, exactly as in a normal forum reply.

Changed

The post editor is now a page, not a modal. The title, excerpt, cover image, category, visibility and comments-toggle stay on the page; the body opens the docked composer via the same click-to-write placeholder + live preview Flarum shows at the end of a discussion.
Publish / Save draft / Cancel / Delete are page actions; the composer's submit publishes.
Editor routes are registered server-side so direct loads/refreshes of /blog/compose work.

Notes

Blog comments already used the native composer (they're ordinary discussions), so they were unaffected by the earlier editor issues.

Upgrade

composer require linkrobins/blog
php flarum migrate && php flarum assets:publish && php flarum cache:clear

KBExit

linkrobins/blogreleases/tag/v1.2.1

Smoother article pages. Article content no longer gets rebuilt on every page update while you read. This also fixes a long-standing issue where add-ons that enhance the article body couldn't keep their changes on screen — for example, Link Robins Table of Contents now shows its Contents box on blog articles.

Also:

The "Draft" and "Members" badges can now be translated.
Internal modernization to Flarum's standard TypeScript structure, plus removal of leftover unused code.

Nothing to do after updating.

KBExit

Since the Blog Extension by Friends of Flarum is getting an update, I am debating on redoing this extension as a Ghost CMS to Flarum bridge. I think that it would be more of a value being a cross ecosystem bridge and not be a conflict of having 2 similar extensions here.
Let me know what you think.

luceos

KBExit I wouldn't redo it. Maybe sunset this one, and whatever ideas you have can live in a new project.

Ps just read all the changes, you've been on fire man.

KBExit

After careful consideration, I haveAbandoned this extension.
Instead, I will see about creating a theme or two for the FoF Blog extension.

« Previous Page