Boat records are migrated automatically. The owner column becomes the membership number, the free-text home harbour column is removed, and the membership number is made unique. Boats needing manual attention are listed in the PHP error log \u2014 see the changelog.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3709070,"resolution":"128x128","location":"assets","locale":"","width":1100,"height":1100},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3709070,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3709070,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3709070,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.1","1.1.0","1.1.1"],"block_files":[],"assets_screenshots":{"screenshot-1.jpg":{"filename":"screenshot-1.jpg","revision":3709070,"resolution":"1","location":"assets","locale":"","width":1243,"height":1059},"screenshot-2.jpg":{"filename":"screenshot-2.jpg","revision":3709070,"resolution":"2","location":"assets","locale":"","width":1149,"height":643},"screenshot-3.jpg":{"filename":"screenshot-3.jpg","revision":3709070,"resolution":"3","location":"assets","locale":"","width":1313,"height":1058}},"screenshots":{"1":"New register for boat data","2":"Map showing members home habour","3":"Advanced member statistics and sponsor activity (number of link clicks)"}},"plugin_section":[],"plugin_tags":[13696,14241,1919,132457],"plugin_category":[58],"plugin_contributors":[265152],"plugin_business_model":[],"class_list":["post-366786","plugin","type-plugin","status-publish","hentry","plugin_tags-boats","plugin_tags-club","plugin_tags-members","plugin_tags-nautical","plugin_category-user-management","plugin_contributors-pcio","plugin_committers-pcio"],"banners":{"banner":"https:\/\/ps.w.org\/pcio-vis-boat\/assets\/banner-772x250.png?rev=3709070","banner_2x":"https:\/\/ps.w.org\/pcio-vis-boat\/assets\/banner-1544x500.png?rev=3709070","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/pcio-vis-boat\/assets\/icon-128x128.png?rev=3709070","icon_2x":"https:\/\/ps.w.org\/pcio-vis-boat\/assets\/icon-256x256.png?rev=3709070","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/pcio-vis-boat\/assets\/screenshot-1.jpg?rev=3709070","caption":"New register for boat data"},{"src":"https:\/\/ps.w.org\/pcio-vis-boat\/assets\/screenshot-2.jpg?rev=3709070","caption":"Map showing members home habour"},{"src":"https:\/\/ps.w.org\/pcio-vis-boat\/assets\/screenshot-3.jpg?rev=3709070","caption":"Advanced member statistics and sponsor activity (number of link clicks)"}],"raw_content":"\n
Adds a Boat Register<\/strong> to PCIO VIS Member Event for sailing clubs and other\nboat-oriented organisations.<\/p>\n\n Features<\/strong><\/p>\n\n This plugin stores all its data locally in two custom database tables. It does not\ncommunicate with any external service, apart from the harbour map tiles listed\nunder External services<\/strong> below.<\/p>\n\n Deleting the plugin from Plugins<\/strong> removes its The database tables are deliberately kept<\/strong>, because they hold your club's boat register and harbour list. These tables survive:<\/p>\n\n If you want a full wipe, drop both tables manually from phpMyAdmin or a SQL client. Also delete the leftover The plugin itself makes no outbound requests: all boat, harbour and member data stays in your local database, no analytics or tracking is included, and no account with any third party is required.<\/p>\n\n The one exception is the harbour map on The map is only used in wp-admin and requires the Go to Go to Yes. 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 \u2014 see External services<\/strong> below for the details.<\/p><\/dd>\n If they were the only member on their membership number, the boat is deleted.\nIf other members still share that number, the boat is kept and stays with the\nremaining crew.<\/p><\/dd>\n\n<\/dl>\n\n\n\n
\/vis\/boats<\/code>, access-controlled by the\n vis_boat_manage capability (granted to Editor and Administrator on\nactivation).<\/li>\n\/vis\/harbours<\/code> \u2014 list, create, edit, and delete\nharbours on a map, with duplicate-name protection and delete-guard against\nharbours still in use.<\/li>\nUninstall<\/h3>\n\n
pcio_me_boat_db_version<\/code> option, so a reinstall rebuilds the tables from scratch.<\/p>\n\n\n
{prefix}me_boat_boats<\/code><\/li>\n{prefix}me_boat_harbours<\/code><\/li>\n<\/ul>\n\n{prefix}me_boat_crew<\/code> table if your site was created before 1.1 \u2014 it is no longer used and is dropped automatically on the 1.1 upgrade.<\/p>\n\nExternal services<\/h3>\n\n
\/vis\/boats<\/code> and \/vis\/harbours<\/code>, which displays map tiles in your browser:<\/p>\n\n\n
https:\/\/{s}.tile.openstreetmap.org\/{z}\/{x}\/{y}.png<\/code>. Your browser's IP address is visible to OpenStreetMap, along with the map area you pan to. No boat or member data is sent. Their tile usage policy<\/a> applies.<\/li>\nhttps:\/\/tiles.openseamap.org\/seamark\/{z}\/{x}\/{y}.png<\/code>, a transparent overlay of seamarks. Same conditions as above; see the OpenSeaMap site<\/a>.<\/li>\n<\/ul>\n\nvis_boat_manage<\/code> capability. You can replace both tile URLs in assets\/harbour-map.js<\/code> and assets\/harbours-admin.js<\/code> with your own tile server or a local tile set if you would rather not contact them at all.<\/p>\n\n\n\n
pcio-vis-boat<\/code> folder to \/wp-content\/plugins\/<\/code>.<\/li>\n\/vis\/boats<\/code> to start managing the boat register.<\/li>\n<\/ol>\n\n\n\n
Where do I manage boats?<\/h3><\/dt>\n
\/vis\/boats<\/code> on the front end. A \"Boats\" link also appears in the Vis\nnavigation and as a tile on the \/vis\/<\/code> landing page for users with the\n vis_boat_manage capability.<\/p><\/dd>\nWhere do I manage harbours?<\/h3><\/dt>\n
\/vis\/harbours<\/code> on the front end. A \"Harbours\" link appears in the Vis\nnavigation and as a tile on the \/vis\/<\/code> landing page for users with the\n vis_boat_manage capability. A \"Vis \u2192 Harbours\" submenu in wp-admin redirects\nthere. Harbour names must be unique; existing duplicates are merged on upgrade.<\/p><\/dd>\nCan crew members see their own boats?<\/h3><\/dt>\n
GET \/pcio-vis\/v1\/boat\/member\/{member_id}<\/code> returns the boat registered for\nthat member's membership number \u2014 an empty list when they have none, otherwise\none boat with a crew<\/code> array listing everyone on that number. The endpoint is\navailable to administrators and to the member themselves when they are logged\nin. Members can also edit their own boat and add or remove crew at\n \/vis\/members \u2192 their profile.<\/p><\/dd>\nDoes this plugin send any data externally?<\/h3><\/dt>\n
What happens when a member is deleted from the core plugin?<\/h3><\/dt>\n
1.1<\/h4>\n\n
\n
[pcio_boat_edit_profile]<\/code> shortcode alias.<\/li>\nvis_member<\/code> is accepted and promoted. Removing a crew member clears\ntheir membership number and revokes vis_member<\/code>.<\/li>\n\/vis\/<\/code> landing page, both gated on vis_boat_manage<\/code>.<\/li>\nme_boat_crew<\/code> table is\ngone; every member carrying the boat's membership number is crew on that\nboat, so the crew group and the subscription always agree. A boat's owner\ncolumn is the membership number and is unique \u2014 one boat per membership\nnumber.<\/li>\nhome_harbour<\/code>\ncolumn is removed from me_boat_boats<\/code> and the harbour name is resolved by\njoining the harbours table, so the same harbour cannot be spelled differently\non two boats. The sign-up form and the boat form now save only the selection;\ntyping free text without picking a harbour no longer stores a name.<\/li>\nme_boat_harbours.name<\/code>, and any duplicates found on upgrade are\nmerged \u2014 boats are repointed to the surviving harbour before the duplicate rows\nare removed.<\/li>\naria-activedescendant<\/code>, and editing the\ntext after picking clears the selection so a typo cannot save the wrong\nharbour.<\/li>\n\/shop\/accepted<\/code> style confirmation is unchanged, but a crew\nmember without their own subscription now inherits the shared membership's\nstatus instead of showing an unknown state.<\/li>\n1.0.3<\/h4>\n\n
\n
\/vis\/harbours<\/code> (capability vis_boat_manage<\/code>):\nlist, create, edit and delete harbours with a Leaflet draggable-marker map.<\/li>\nme_boat_harbours.name<\/code> was added.<\/li>\n1.0.1<\/h4>\n\n
\n
vis_member<\/code> capability instead of being public.<\/li>\nvis_boat_manage<\/code>\ncapability. Harbours added on the map during sign-up are stored only after\nmembership is confirmed, removing the unauthenticated write path.<\/li>\n<\/ul>\n\n1.0.0<\/h4>\n\n
\n