ICO/STO/IDO v6.2.8

Release Date: September 4, 2026 Tags: CREATOR, UPDATES

Requires Core v6.7.6.

Overview

Editing or deleting a project update has never worked, and posting one looked like it had failed. Two separate faults on the same small feature, found while verifying the release notes for another:

• Edit and delete answered "Missing update ID" to every request. Both routes read their path parameter under the name updateId, and the route segment is [id], so the value was always absent and the guard refused before anything else ran. Every sibling route in this addon reads id.
• Posting an update rendered a blank row. The creator's list read the route's whole response envelope as if it were the update record, so a newly posted update showed an empty title and empty body until the page was reloaded. That one was saved correctly; only the display was wrong.

Neither reported itself usefully. The platform's fetch helper does not throw on a shape it did not expect, so a field that is not where the caller looked is simply undefined on its way into the page, and a 400 from a save surfaces as a generic failure rather than as the reason.

Update Instructions

# 1. Update the addon in Admin → System → Extensions
# 2. Apply the release
pnpm updator

No schema change and no seeder. Both halves matter: the two routes are server-side and the update list is in the browser bundle, and pnpm updator rebuilds both.

Upgrade Notes

Edits your creators thought they had saved were never saved

Because the edit route refused every request, no edit to a project update has ever been written — the original text stayed in the database and the creator was shown a save failure. There is nothing to repair in your data: the rows are as they were first posted. Tell any creator who reported an edit "not sticking" that it will now hold.

Fixed

• Fixed — the edit and delete routes for a project update read their path parameter as updateId while the route segment is [id], so both refused every request with "Missing update ID" before reaching the record. Both now read id, as every other route under this tree does.
• Fixed — posting a project update prepended the response envelope ({ message, update }) to the creator's list instead of the update inside it, so the row that had just been written rendered blank until the page was reloaded.
• Fixed — the same list matched rows on an id read off that envelope, where there is none, so an edit could not have reached the list even once the route behind it started answering.