Member profile fields gained a display-order setting.
The platform underneath your site keeps changing. Updater is the running record of those changes, in plain language.
Monthly · plain language · included with a Nebula Membership
Your directory site sits on a platform that is actively developed. That is a good thing, right up until something shifts and you find out by accident.
A setting sits somewhere new, or a page renders differently, and the only signal you got was your own second glance.
Shorthand, internal names, and no answer to the only question you actually have.
Most changes will never touch your site. Working out which ones do is the whole job, and it is the part nobody does for you.
Each entry is written to be read once and acted on, or skipped with confidence.
Said plainly. Not the release-note wording, and not a list of commits.
The line that decides whether you read on or move to the next entry.
If something needs your hand, the steps. If nothing does, that is said outright.
Entries stay put, so the record builds into something you can look back through.
v2026.07 so you can tell where your site sits against the record.
This is the shape of an entry. Three lines, and you know whether it is your problem.
Member profile fields gained a display-order setting.
Only if you have customized your profile layout. Default layouts are unaffected.
Nothing. The new setting inherits the order you already had until you change it.
feat(profile): add display_order to user_meta field config; migration backfills null as insertion index
You can now choose the order your member profile fields appear in. Sites that already have a custom order keep it.
Changes land, usually without an announcement you would notice.
Every release note, including the ones written for developers.
Into what it means for a directory site, and who it actually affects.
Dated, kept, and readable in a couple of minutes.
“The entry that saved me was the one about…”
“I stopped finding out about changes by…”
Most tiers in the HelpDesk ladder are bought on their own, whenever you want one. This first tier is the exception: the only way in is a Nebula Membership, our base membership tier.
Reading every platform release and working out what it means for a directory site takes real time each month. A Nebula Membership is what pays for that time, and Updater is one of the things it buys.
Access follows the membership. If it lapses the entries stop, and when it resumes they come back.
Monthly. If a month brings nothing that affects directory sites, the entry says so rather than padding itself out.
No. Those are published by the platform and written for developers. Updater is our reading of them, aimed at somebody running a directory site.
Rarely. Most changes need nothing from you, and each entry says outright when that is the case.
Yes. Entries are dated and stay available, so the record builds up over time rather than scrolling away.
Access to the entries stops, and returns when the membership does.
Part: your directory site · Action: stay current
One entry a month, and you know where your site stands.