PCIO VIS Boat

Changelog

1.1

• Added: Member boat profile. Signed-in members can now edit their own boat
  and manage their crew directly on the core member profile page, with no
  administrator involved. New “Boat details” and “Crew” sections appear there,
  backed by a new [pcio_boat_edit_profile] shortcode alias.
• Added: Crew management for members. New self-service routes
  GET/POST /pcio-vis/v1/boat/my-boat/{id}/crew and
  DELETE /pcio-vis/v1/boat/my-boat/{id}/crew/{member_id} let a boat owner add
  and remove crew. A new crew member is created in the core member register,
  given a WordPress login and the welcome email; an existing WordPress user
  without vis_member is accepted and promoted. Removing a crew member clears
  their membership number and revokes vis_member.
• Added: Boat detail popup in the core member list. The Boat cell is now a
  button that opens a read-only dialog with type, model, home harbour, build
  year, sail number, MMSI, membership number, note and the full crew group.
• Added: Harbour list navigation — a “Harbours” entry in the Vis navigation
  and a tile on the /vis/ landing page, both gated on vis_boat_manage.
• Added: Shortcode reference — the Boat plugins are documented in the core
  shortcode reference with a dedicated sidebar group.
• Changed: Crew is now the membership number. The me_boat_crew table is
  gone; every member carrying the boat’s membership number is crew on that
  boat, so the crew group and the subscription always agree. A boat’s owner
  column is the membership number and is unique — one boat per membership
  number.
• Changed: Home harbour is stored by id. The free-text home_harbour
  column is removed from me_boat_boats and the harbour name is resolved by
  joining the harbours table, so the same harbour cannot be spelled differently
  on two boats. The sign-up form and the boat form now save only the selection;
  typing free text without picking a harbour no longer stores a name.
• Changed: Harbour names are unique. A case-insensitive unique index is
  added to me_boat_harbours.name, and any duplicates found on upgrade are
  merged — boats are repointed to the surviving harbour before the duplicate rows
  are removed.
• Changed: Harbour picker is keyboard-navigable. The autocomplete supports
  Arrow Up/Down, Enter and Escape with aria-activedescendant, and editing the
  text after picking clears the selection so a typo cannot save the wrong
  harbour.
• Changed: The Boat Register table shows a Crew column instead of an Owner
  column, with each crew name linking to the member directory when the viewer
  is allowed to see it.
• Improved: Boat form validation now reports a missing boat name, an MMSI that
  is not exactly 9 digits, a build year outside 1900–this year, and invalid
  harbour coordinates, inline on the offending field.
• Improved: The /shop/accepted style confirmation is unchanged, but a crew
  member without their own subscription now inherits the shared membership’s
  status instead of showing an unknown state.
• Security: a harbour placed on the map is now created only when the caller is
  entitled to it — a confirmed order for sign-ups, or a signed-in member for
  profile saves. Previously a sign-up that completed without a payment (no
  active membership product, or Stripe not configured) could write a harbour
  row from the anonymous form post.
• Fixed: The harbour map could show no members for any harbour, because it
  matched the boat’s owner column against the member id while the rest of the
  plugin had moved to membership numbers.
• Fixed: Boats whose owner membership number no longer existed were silently
  orphaned by the ownership check on the REST routes.

1.0.3

• Added a Harbours management page at /vis/harbours (capability vis_boat_manage):
  list, create, edit and delete harbours with a Leaflet draggable-marker map.
• Deleting a harbour that still has boats is blocked with a 409 response showing
  the boat count; move the boats first.
• Creating or editing a harbour rejects duplicate names (case-insensitive) with a
  409 response, and a unique index on me_boat_harbours.name was added.
• “Boats” column on the management page shows the boat-row count for each harbour.
• A “Vis → Harbours” wp-admin submenu entry redirects to the front-end page.

1.0.1

• Security: the harbour map endpoint that lists member names and membership
  numbers now requires the vis_member capability instead of being public.
• Security: creating a shared harbour now requires the vis_boat_manage
  capability. Harbours added on the map during sign-up are stored only after
  membership is confirmed, removing the unauthenticated write path.

1.0.0

• Initial release.