PCIO VIS Member Event

Өзгөртүүлөр

1.5.0

• Added: Rewritten member profile page — [pcio_me_edit_profile] is now a server-rendered form (new templates/member-profile.php plus its own stylesheet) with browser-side validation, an inline error box and a success message. The membership number is shown read-only so members cannot change it. Extensions can add their own fieldsets with the new pcio_me_profile_extra_sections filter.
• Added: Member save validation hook — the new pcio_me_member_update_validate filter lets extensions reject a save (from the member dialog or the profile form) before anything is written; the request is answered with a 422 and the extension’s message.
• Added: Vis → Sponsor Links — a dedicated admin page documenting the pcio-sponsor-link class, moved off the Shortcode reference page, with step-by-step instructions for the block editor, the classic editor and Divi (plain text links and Image modules).
• Added: Exact membership-number deep link — /vis/members?member_number=42 pre-fills the membership-number filter and matches that number exactly, so a short number can no longer match a longer one. Used by the Boat register’s crew links.
• Added: “No members match your search” message on the [pcio_me_members] list when a search filters every row out.
• Added: Signup fulfilment context — new public methods PCIO_VIS_Member_Signup_Fulfillment::stash_order_context(), get_order_context(), take_order_provision(), claim_order_welcome() and is_order_welcome_claimed() let extensions running on pcio_mep_order_confirmed share the created member, read the provisioned WordPress account, and take over (or hand back) the welcome mail.
• Changed: One membership number instead of two. The separate “Membership #” field is retired; the # column is now the membership number itself, stored as an integer, and any number of members can share it (that is how a boat or household is grouped).
• Changed: The numbering upgrade migrates your data automatically on the next admin page load. Members with a “Membership #” keep that number; members without one get the leading digits of their old “#”; a “#” that was not a plain number is preserved as a legacy_member_number row in wp_me_member_meta. The finance journal and the Products extension’s subscription table are converted the same way. The routine is safe to re-run and resumes by itself if a step fails.
• Upgrade procedure:
  1. Export wp_me_members (and wp_me_p_subscriptions if you use the Products extension) from your database admin tool, so you can restore the old numbers if anything looks wrong.
  2. Update the plugin, then open any wp-admin page to run the upgrade.
  3. Check Vis → Members: several members may now share one number, and a number that used to carry a letter suffix has lost it. Correct anything that looks wrong by hand.
  4. Update the Products, Tickets and Boat extensions to their matching 1.5.0 release. Older extension versions read the retired column, so membership status would look out of date until they are updated.
  5. If the upgrade did not run (for example because a host blocks ALTER TABLE), a member_number_legacy_140 column is left behind on wp_me_members holding the original numbers — leave it in place and open any wp-admin page again; the next attempt resumes from there.
• Fixed: the members and finance-journal tables are now actually brought up to date on an existing site. Their CREATE TABLE statements no longer use IF NOT EXISTS, which made dbDelta() treat “IF” as the table name and skip the table completely.
• Changed: Collision-free number allocation — new sign-ups get the next free membership number through the new PCIO_VIS_DB::create_with_next_number(), which re-checks for a concurrent claim. Two simultaneous sign-ups can no longer be handed the same number.
• Changed: Member meta writes are hardened — PCIO_VIS_Meta_DB::set() now accepts a member id or a member row (or a single-row list) and silently ignores a non-numeric id instead of raising a type error that killed the request.
• Changed: Welcome mail can be rendered without being sent — render_welcome() returns the resolved subject and body (and an empty result when the template, member or address is unusable); send_welcome() keeps its old behaviour and now falls back to nothing instead of sending an empty mail.
• Changed: No inline script in the members shortcode — the live search and the boat detail popup were previously emitted as an inline <script> block; the search now lives in assets/members-public.js and the boat popup is gone (boat details are on the profile page).
• Changed: PCIO_VIS_DB member-number helpers were renamed and aligned: get_next_member_number(), get_next_free_member_number(), member_number_is_taken(), create_with_next_number(), get_member_number_by_id(), set_member_number(), get_member_ids_by_member_number() and get_members_by_member_number(). The next_member_number() / next_subscription_number() / *_subscription_number() methods are removed — extensions that called them must be updated.
• Changed: the finance journal stores the membership number as an integer, and the journal REST payload no longer returns it as a string.
• Changed: refreshed the Danish (da_DK) translation and regenerated the translation template (.pot) — the recurring-events strings, the new Sponsor Links page, the sign-up modes and the rewritten profile form were all untranslated before.
• Fixed: member search in the [pcio_me_members] list lowercases with mb_strtolower(), so Danish letters (Ø, Æ, Å) now match a search typed with a Danish keyboard.
• Fixed: the sponsor-link help section is no longer listed twice (the scroll-spy index and the page no longer disagree).

1.4.0

• Added: Recurring events — a new Recurrence tab on the event editor. Define a repeat rule on the first event in a series (daily, weekly, monthly by weekday, monthly by date, or yearly) and generate linked copies; the series can be navigated, extended or resolved into standalone events. A new database table stores the series rules.
• Added: Upcoming events shortcode — [pcio_me_upcoming_events] renders a compact, month-grouped agenda list of the next events. Accepts months (how far ahead to look) and limit (maximum events) attributes.
• Added: Membership number — a new “Membership #” field on member records, sortable in the member list and editable from the member dialog. It lets shop subscriptions reference a specific member.
• Added: Event sign-up modes — each event can now choose how people respond: No sign-up (information only), Simple (join / interested / not joining), or Ticket sales when the Tickets extension is active. Choosing No sign-up hides the invitation box entirely on the public event page.
• Added: Rich description editor — the event description editor now supports text and background colour and an Edit HTML toggle for editing the raw source.
• Added: Week numbers — the calendar week view title now shows the ISO-8601 week number (e.g. “Uge 37”).
• Changed: Member deep links — /vis/members?q=… pre-filters the member list, so links (for example from shop subscriptions) can jump straight to a member.
• Changed: public event pages now inherit the active theme’s text colour, so titles and body text stay readable on any page-builder background (e.g. Divi).
• Changed: refreshed the Danish (da_DK) translation and updated the translation template (.pot).
• Fixed: event creation could fail on sites upgraded from older versions whose events table was missing newer columns; the schema now self-repairs on upgrade.
• Fixed: the calendar month title could appear blank or untranslated under Danish; the localised title now renders correctly and is capitalised.
• Fixed: the Edit button on the Calendar → Event Types and Resources tabs showed the wrong label in non-English languages.

1.3.0

• Added: Member sign-up — new [pcio_me_member_signup] shortcode renders a public registration form (name, email, phone, address). It creates the member record, provisions a WordPress account and, with no payment extension active, registers the member immediately. Extensions can inject extra fields and add a payment (checkout) step on submission.
• Added: Welcome email & notifications — a “member_welcome” system mail template is seeded under Vis → Mails and sent automatically to new members, with tag chips for {name}, {member_number}, {site_name} and a one-time set-password {login_url}. Extensions can add their own tags via filters.
• Added: Rolling texts — new [pcio_me_rolling_text] shortcode shows a scrolling banner built from time-scheduled entries. Manage them under Calendar → Rolling Texts, where each entry has a Roller ID and a start/stop window; multiple pages can show independent banners.
• Added: Shortcode reference — new admin page documenting every shortcode with its attributes, defaults, examples and welcome-email tags, including scroll-spy navigation.
• Added: Volunteers mail group and a Copy emails button on the member and workgroup lists for quick recipient selection.
• Fixed: text overlap and layout issues in the admin UI.
• Changed: refreshed the Danish (da_DK) translation and updated the translation template (.pot).

1.2.0

• Added: Event Types — color-coded categories for calendar events with configurable access level (Public, Members only, Volunteers only). Managed from the Calendar → Event Types tab.
• Added: Resources — bookable resources (rooms, equipment, etc.) that can be assigned to events. Conflict detection warns when a resource is already booked for an overlapping event. Managed from the Calendar → Resources tab.
• Added: Default resources per event type — define which resources are pre-selected when a new event of that type is created; defaults are applied automatically on event creation.
• Added: Workgroups — new page at /vis/workgroups/ for organizing volunteers into named working groups. Each workgroup can have one or more members flagged as chairman.
• Added: Volunteer role — members can be designated as volunteers (vis_volunteer capability), enabling volunteer-only event access and workgroup membership.
• Fixed: “Publish & share” heading was double-escaped and displayed as raw HTML entity in the event editor.

1.1.0

• Added: Statistics dashboard at /vis/statistics/ — grouped bar chart of members joining and leaving by year, front-page-view counter, login counter, and a sponsor link click table.
• Added: join_date and leave_date date fields on member records, editable from the member edit dialog and charted on the Statistics dashboard.
• Added: [pcio_me_member_count] shortcode — animated count-up number showing the current total membership. Each page render increments the front-page-view counter. Paste it into any page builder text or code module (e.g. Divi Text Module).
• Added: Sponsor link click tracking — add class="pcio-sponsor-link" to any anchor tag in your content. Click events are captured in the browser and stored; totals appear on the Statistics dashboard.
• Fixed: end date/time entered in the calendar create-event dialog was not saved to the event.
• Fixed: clicking a single all-day cell now correctly pre-fills the end date with the same date as the start date.
• Fixed: end-time field was not hidden when the “All day” checkbox was ticked.
• Fixed: member list was not refreshed in the browser after a member was successfully deleted.
• Fixed: document list shortcode displayed a bullet point before each document link.
• Changed: WP Role column removed from the member list; the WordPress account status is now shown only as a “Create WordPress login” button in the edit dialog when no account exists yet.
• Changed: the edit-member icon in the member list is now shown only to users with the vis_manage_users capability; plain members use the new profile shortcode instead.
• Added: [pcio_me_edit_profile] shortcode — lets a logged-in member edit their own name, email, phone, address and custom fields from any WordPress page.

1.0.0

• Initial release.
• Members register with custom member fields and roles.
• Event calendar with public sign-ups and per-event banner/thumbnail images.
• Member mailings and public newsletter archive.
• Document library grouped by type, backed by the WordPress media library.
• Finance journal.
• Capability-based access control with cumulative logical roles (Vis → Roles).
• Automatic public pages under /vis/ plus shortcodes for embedding in themes.