Bug fix·Mon Aug 31·2026-09-01

Saving a pass or membership works again

Editing any pass type on the Passes page failed with "Something went wrong" and saved nothing. Saving works again, and a refused save now tells you the real reason instead of a generic message.

Editing a pass type on **Passes** failed. The form looked normal, you pressed
Save, and the only thing you got back was **"Something went wrong. Please try
again."** Retrying never helped, because nothing was ever written — the change
was refused by the database before it could be stored.

It was not caused by anything you typed. A recent internal security change
tightened how one part of the system looks up your venue, and a lookup that runs
on every pass-type save stopped resolving. The effect was the same whatever you
edited: a price, a class count, an over-30 price, the shop visibility — all of it
was refused the same way.

**Saving works again.** If you gave up on an edit this morning, open the pass
type and make the change now; it will stick. Nothing that was already saved was
affected, and no pass, membership or client was changed by the fault — a refused
save changed nothing at all, so there is nothing to check or undo.

Two things are better than before:

- **A refused save now tells you what happened.** Where the page used to say
  "Something went wrong", it now names the actual reason — a validation rule you
  hit, a name already in use, or a genuine system fault — and says whether trying
  again will help. You should not have to guess again.
- **The same class of fault is now blocked at the source.** The lookups involved
  are checked automatically from now on, so this cannot come back quietly.

Next update

Safer website marketing and SEO controls

Connect common marketing IDs, review deterministic SEO findings, and keep site-host search materials isolated to one website.

Editing a pass type on **Passes** failed. The form looked normal, you pressed Save, and the only thing you got back was **"Something went wrong. Please try again."** Retrying never helped, because nothing was ever written — the change was refused by the database before it could be stored. It was not caused by anything you typed. A recent internal security change tightened how one part of the system looks up your venue, and a lookup that runs on every pass-type save stopped resolving. The effect was the same whatever you edited: a price, a class count, an over-30 price, the shop visibility — all of it was refused the same way. **Saving works again.** If you gave up on an edit this morning, open the pass type and make the change now; it will stick. Nothing that was already saved was affected, and no pass, membership or client was changed by the fault — a refused save changed nothing at all, so there is nothing to check or undo. Two things are better than before: - **A refused save now tells you what happened.** Where the page used to say "Something went wrong", it now names the actual reason — a validation rule you hit, a name already in use, or a genuine system fault — and says whether trying again will help. You should not have to guess again. - **The same class of fault is now blocked at the source.** The lookups involved are checked automatically from now on, so this cannot come back quietly.

All updates