Skip to content
View in the app

A better way to browse. Learn more.

ernestdefoe.online

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
ernestdefoe.online

Extensions, themes & support for Flarum and Invision Community

Vibe coding for the community web. Report a bug, request a feature, or dig into the source — this is where the tools you use get built, in the open.

We do custom Bespoke Invision Community apps. If you have an idea for something you want then use the contact form to get in touch with us.
Knowledge base

Things that cost me a day, so they cost you none

Working notes from building Invision Community and Flarum applications. Mostly the failures that give no error at all — the ones where everything installs cleanly and quietly does the wrong thing.

92 articles

Invision Community 5

86 articles

Extensions and contracts

39

What each extension point is for, what it must declare, and what happens when it is wrong — which is usually nothing visible.

Languages and text

5

The string table, translation, and the places where text does not appear where you expected it to.

Theming, templates and forms

9

Theme hooks, CSS that survives both colour schemes, and building forms that do not throw on render.

Background work and scheduled tasks

5

The queue system, work that has to happen after the response, and jobs that finish without doing anything.

Data, settings and storage

11

The database layer, settings, tags, file storage, and backing up a live site.

AI features and expectations

5

What these features do, what they cost, and what buyers reasonably but wrongly assume they do.

Application structure and releases

11

The JSON files an application is made of, versioning and upgrade steps, and testing from the command line.

Realtime, chat and calls

1

WebSocket gateways, relays and the server-side pieces live features depend on — where "it works when I test it" and "it works for your members" are different claims.

Nothing matches that.

Your friendly URLs have the app name in them twice

You define a friendly URL, load the page, and the address reads /discord/discord/invite/abc123. The route works, nothing errors, and the duplication looks like a typo somewhere you cannot find.

It is not a typo. Invision Community prepends topLevel to every friendly path in the file. Repeat it in the path and you get it twice.

Wrong

{
    "topLevel": "discord",
    "pages": {
        "myapp_invite": {
            "friendly": "discord/invite/{@key}",
            "real": "app=myapp&module=discord&controller=invite"
        }
    }
}

Produces /discord/discord/invite/abc123.

Right

{
    "topLevel": "discord",
    "pages": {
        "myapp_invite": {
            "friendly": "invite/{@key}",
            "real": "app=myapp&module=discord&controller=invite"
        }
    }
}

Produces /discord/invite/abc123.

The top-level landing page is the exception, and it is an empty string

The obvious guess for "the page at /podcasts" is "friendly": "podcasts". That gives you /podcasts/podcasts/. Every core application uses an empty string instead:

grep -A2 '"topLevel"' applications/forums/data/furl.json
#   "topLevel": "forums",
#   "pages": { "forums": { "friendly": "", ... } }

So:

{
    "topLevel": "podcasts",
    "pages": {
        "myapp_index":   { "friendly": "",                "real": "..." },
        "myapp_show":    { "friendly": "{#id}-{?}",       "real": "..." },
        "myapp_episode": { "friendly": "episode/{#id}-{?}","real": "..." }
    }
}

Which gives /podcasts/, /podcasts/12-my-show/ and /podcasts/episode/34-my-episode/.

The placeholder types are not interchangeable

A second way to lose an afternoon. {#name} is a number and {@name} is a string:

"friendly": "invite/{#key}"   <-- a hex key becomes 0. Every link resolves to the same record.
"friendly": "invite/{@key}"   <-- correct for anything non-numeric

Use {?} for a slug you do not intend to read back — the human-readable part of /podcasts/12-my-show/.

Check it rather than assume it

Neither mistake throws. Both produce URLs that resolve, so tests pass and the page loads. Print the URLs once, from code, and read them:

printf( "%s\n", Url::internal(
    'app=myapp&module=x&controller=y&id=1', 'front', 'myapp_show', array( 'the-slug' )
) );

This matters more than tidiness for anything a person keeps. A podcast feed address is permanent once somebody subscribes; an invite link gets pasted into chat and printed on things. Fixing the URL later means breaking every copy of it that already exists.



User Feedback

Recommended Comments

There are no comments to display.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.