PCIO VIS Boat
| 开发者 | pcio |
|---|---|
| 更新时间 | 2026年10月3日 04:01 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Adds a Boat Register to PCIO VIS Member Event for sailing clubs and other
boat-oriented organisations.
Features
- Register boats with: home harbour, name, type, model, build year, sail number and MMSI number.
- A boat belongs to a membership number. Everyone who shares that membership number is crew on the boat, so the crew group and the subscription follow the same number — there is no separate crew table to keep in sync.
- The home harbour is picked from the shared harbour list and stored by id, so the same harbour name cannot drift across boats.
- Members can maintain their own boat and crew from the core member profile — no administrator needed.
- When a core member is deleted their boat is removed only if they were the last member on that membership number; otherwise the boat stays with the remaining crew.
- Boat Register admin page at
/vis/boats, access-controlled by thevis_boat_managecapability (granted to Editor and Administrator on activation). - Harbours management page at
/vis/harbours— list, create, edit, and delete harbours on a map, with duplicate-name protection and delete-guard against harbours still in use. - Boat name appears in the core member list; clicking it opens a read-only popup with the full boat details and the crew group.
安装:
- Make sure PCIO VIS Member Event is installed and active.
- Upload the
pcio-vis-boatfolder to/wp-content/plugins/. - Activate the plugin in WordPress.
- Navigate to
/vis/boatsto start managing the boat register.
屏幕截图:
常见问题:
Where do I manage boats?
Go to /vis/boats on the front end. A "Boats" link also appears in the Vis
navigation and as a tile on the /vis/ landing page for users with the
vis_boat_manage capability.
Where do I manage harbours?
Go to /vis/harbours on the front end. A "Harbours" link appears in the Vis
navigation and as a tile on the /vis/ landing page for users with the
vis_boat_manage capability. A "Vis → Harbours" submenu in wp-admin redirects
there. Harbour names must be unique; existing duplicates are merged on upgrade.
Can crew members see their own boats?
Yes. GET /pcio-vis/v1/boat/member/{member_id} returns the boat registered for
that member's membership number — an empty list when they have none, otherwise
one boat with a crew array listing everyone on that number. The endpoint is
available to administrators and to the member themselves when they are logged
in. Members can also edit their own boat and add or remove crew at
/vis/members → their profile.
Does this plugin send any data externally?
No boat, member or order data ever leaves your server. The only outbound requests are the OpenStreetMap and OpenSeaMap map tiles drawn by the harbour map in wp-admin — see External services below for the details.
What happens when a member is deleted from the core plugin?
If they were the only member on their membership number, the boat is deleted. If other members still share that number, the boat is kept and stays with the remaining crew.
更新日志:
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}/crewandDELETE /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 withoutvis_memberis accepted and promoted. Removing a crew member clears their membership number and revokesvis_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 onvis_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_crewtable 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_harbourcolumn is removed fromme_boat_boatsand 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/acceptedstyle 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.
- Added a Harbours management page at
/vis/harbours(capabilityvis_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.namewas 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.
- Security: the harbour map endpoint that lists member names and membership
numbers now requires the
vis_membercapability instead of being public. - Security: creating a shared harbour now requires the
vis_boat_managecapability. Harbours added on the map during sign-up are stored only after membership is confirmed, removing the unauthenticated write path.
- Initial release.