Skip to content

Jetonomy 1.9.2 - read-only members stop seeing controls the server refuses, and leave-space

Choose a tag to compare

View all tags
@vapvarun vapvarun released this 11 Aug 08:48
· 163 commits to main since this release
v1.9.2
fb5e746
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Read-only members stop being shown controls the server then refuses, and a member can leave a space from the same place they joined it.

  • New - A member can leave a space from the front end, the same place they joined it, instead of only being able to join.
  • Fix - A member admitted to a space by a read-only access rule was shown Vote controls, a New Topic button, the empty-space call to action and a reply box, then refused by the server on use. Each control now appears only when the member is actually allowed to use it, so a read-only member sees the content without the dead buttons.
  • Fix - A single topic in a private space now opens for a member admitted by an access rule, matching what the server allows.
  • Fix - Tag, space and author listings open again when there is no search text, instead of returning nothing.
  • Dev - Member and leaderboard payloads carry author_last_seen_at so a client can show the online dot under an avatar.
  • Dev - New AccessRule::spaces_with_level_prefix() lists every space gated on a membership-level rule, so an integration can show the spaces a member can reach by access rather than only those they have formally joined.
  • Dev - New Space::unique_slug() is the one rule for space-slug uniqueness, shared by every path that creates a space.

Pairs with Jetonomy Pro 1.9.2. Install both updates together.

Full changelog: https://wbcomdesigns.com/release-notes/jetonomy/

Assets 3
Loading