PCIO VIS Member Event

1.6.0

• Added: Personal calendar filter. A Filter button next to “+ New event” (both shown only on the Calendar tab) opens filter settings for date range, text (title, resume, description), crew member or open shifts, published on homepage, event types (with Internal/Public/Cafe quick picks) and crew roles. Each criterion can show or hide (exclude) its matches. Settings are stored per user in the new me_calendar_filters table (not tracked in the change history), the button turns green while a filter is in use, and Clear deletes the settings to return to the default view.
• Changed: The calendar list view uses the personal filter’s date interval when its date rule is active (instead of the current month), and its title shows that interval (e.g. “13 Oct – 17 Nov 2026”). An empty start means all past events and an empty end all future events, shown as “From …”, “Until …” or “All events”.
• Added: Previous («) and next (») buttons beside the date on the event page jump to the neighbouring event in time order. They follow the personal calendar filter when one is in use (all events otherwise) and keep the open tab.
• Changed: Google Calendar sync sends the event’s full description (up to 8,000 characters, with paragraph breaks kept) instead of only the first 160 characters on one line. When the description is longer than that, the shorter resume is used instead; without a resume the description is cut at a word boundary. Already-synced events are updated on the next run.
• Changed: The Mails section is now called Marketing, with a megaphone icon on the landing page. It still has the Mails and Newsletters tabs, and the page addresses are unchanged.
• Added: Crew shift reminders. A new daily sync job, “Crew shift reminders” (disabled by default), e-mails each volunteer assigned to a crew role on tomorrow’s shifts. The text is the editable crew_shift_reminder system mail with the tags {name}, {event_title}, {shift_start}, {shift_end}, {role_name} and {site_name}. A shift is reminded once, and again only if its member or times change.
• Changed: The event types list shows columns for name, scope, cafe opening hours (read-only checkbox), default resources and a colour swatch.
• Changed: Every event must have an event type. Creating or saving an event without a valid type is rejected (the editors require a choice instead of offering “None”), and an event type still used by events cannot be deleted.
• Added: Optional Get-in time (artist arrival) and Door opening time on events, edited on the event’s general-details tab and stored as get_in_datetime / door_opening_datetime. A time later than the start time is saved on the evening before the start date. Both must be on or before the start, follow the start when it is moved (e.g. by calendar drag), are copied to recurring series events, and are tracked in the change history. The public event page shows the door opening time.
• Added: Protected Cafe, Art and Holiday system event types and an editable in_cafe_time flag. Schema upgrades preserve existing type IDs and settings. Cafe-time warning suppression is reserved for a future change.
• Fixed: Section headers and browser titles remain Members on Workgroups, Mails on Newsletters, and Finance on Deliveries; the active tab identifies the current subsection.
• Fixed: Mails and Newsletters section tabs appear below the page header, matching the other Vis pages.
• Improved: Vis navigation groups Members, Calendar, Mails, Finance and Shop into accessible dropdowns with direct links to their page tabs. Newsletters belongs under Mails; Deliveries belongs under Finance; Statistics is a standalone menu item. The landing page uses a two-column tile layout (one column on mobile). Navigation, tabs and the WordPress admin bar share capability-aware section definitions. Existing page URLs remain supported.
• Added: Event publication approval on the Publish tab, visible to all members but editable only with vis_publish_events. Homepage approval controls public event tiles, sliders, agenda, newsletter event inclusion, direct public links, embeds and signup/ticket checkout. Existing events remain approved during upgrade; new events start unpublished. Poster and Facebook flags are stored for future use and do not trigger integrations. Unpublished public links return 404; event embeds show a not-published message. Internal event editors can still manage unpublished events.
• Changed: Event detail headers show a compact start/end date and time, updated after saving. The Delete event button is now on the general-details tab.
• Added: Mail and newsletter-template editors now offer inline font sizes and an HTML source mode. Unchanged source HTML is preserved when switching back to the visual editor; saves still use WordPress HTML sanitization.
• Fixed: Newsletter emails include upcoming events with full descriptions, dates, locations and main event images between the mail body and shared footer. Email output retains emojis and contains no PDF page breaks.
• Added: Shared Newsletter template system mail under Vis → Mails. Its header (organization title and media-library logo) and footer are reused by every newsletter email and PDF. The newsletter checkbox reveals read-only previews and an Edit newsletter template button; edit the shared template to update future sends and PDF generations. Existing newsletter-specific footers are retained in stored mail records but are replaced by the shared footer in output. Ordinary mails are unchanged.
• Changed: Each event starts on a new page in generated newsletter PDFs. Email content is unchanged.
• Fixed: Newsletter PDFs remove unsupported emojis and trailing empty editor lines. Event images are centered above the description and scaled to fit; long descriptions can continue across pages instead of being trapped in a single table row.
• Added: Change history with undo — all writes to Vis tables are logged in the new me_change_history table, with undo data in me_change_undo. A new Vis → History admin page lists every change with filters and an Undo button, guarded by the new vis_undo_changes capability (granted to System Admin).
• Added: History tab on the event page (/vis/events/{id}), listing the changes to that event, its sign-ups and resources.
• Added: Member detail page (/vis/members/{id}) with a Settings tab (edit fields, Vis role, delete) and a History tab. Rows in the members list now open this page. Extensions can add tabs with the pcio_me_member_tabs filter.
• Added: developer hooks pcio_me_history_tables, pcio_me_history_undo_retention_days and pcio_me_history_undone.
• Added: Google Calendar sync — new Vis → Google admin page (service-account key, default location, single-day event types, calendars with All/Public scope, connection test) and a “Sync Google Calendar” job under Vis → Sync Jobs, replacing the legacy /vis/sync_calendar.php endpoint. Event links are kept per calendar in the new me_google_calendars and me_google_event_map tables. Changed events are detected from a stored payload hash instead of a shared dirty flag, so failed updates are retried. Uses the WordPress HTTP API, without a Google client library.

1.5.0

• Fixed: Roles page membership display — shows the separately managed vis_member capability and explains why the default Member role has no additional capabilities, without changing permission grants.

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.