LAPDI Events

By Let A Pro Do IT!

0+ active installationsVersion 1.7.3

Manage recurring public and member events, venues, and organizers, with calendar shortcodes and a The Events Calendar importer.

Description

LAPDI Events is a public and member-aware calendar plugin. It provides its own lapdi_event, lapdi_venue and lapdi_organizer administration types, reusable event categories/venues/organizers, one-time/daily/weekly/monthly recurrence, and List/Month/Day calendar views — with each event set to either Public or Members only visibility.

Features

  • Reusable event categories, venues and organizers
  • Event Series for grouping events, with a series filter on the calendar
  • One-time, daily, weekly and monthly recurrence with configurable intervals, weekly weekdays, monthly ordinal weekdays and end dates
  • Rolling planning window with the next four active meetings from each recurring series
  • Linked meeting customization for titles, agendas, images, schedules, logistics, visibility, capacity, internal staff notes and follow-up posts
  • Individual meeting cancellation without ending the parent series or deleting existing responses
  • Accessible List, Month and Day views, with search, an Event Series filter and responsive mobile layouts
  • Per-meeting Apple Calendar downloads and Google Calendar add-event links
  • Stable unique event codes with optional meeting-specific overrides
  • Locally generated event-website QR codes with SVG download
  • Platform-aware venue address links (Apple Maps on Apple devices, Google Maps elsewhere)
  • Per-event Public or Members only audience
  • Published blog-post follow-ups for event recaps, photos and video
  • Per-occurrence responses: Planning to attend or Unable to attend, plus Attended, which users can mark themselves on public events once they start and which members-only events set only by a staff door check-in
  • Closed response controls after a meeting ends, with each signed-in user’s final status
  • Per-event recording and photography notices with required attendee consent
  • RSVP confirmation emails for new or changed attending responses, with resolved event details
  • Branded HTML RSVP confirmation emails with a configurable logo and template
  • Optional per-occurrence meeting capacity with live seat availability and overbooking protection
  • Member-visible response lists with names and statuses, hidden from public viewers
  • Administrative attendee log with response removal and check-in times
  • Staff door check-in from a QR code in each RSVP confirmation email, generated on the site and valid only on the meeting day
  • Per-meeting multiple-choice topic polls with shareable links and optional anonymous suggestions
  • Event-grouped poll administration with rounded aggregate results and no voter identity display
  • [lapdi_events] List/Month/Day calendar shortcode, optionally limited to one series with series="slug"
  • [lapdi_events_preview] public home-page preview shortcode, also accepting series="slug"
  • [lapdi_next_events] compact, tokenized upcoming-event shortcode for landing pages
  • Capability-based administration through manage_lapdi_events
  • Members-only event visibility supports an optional membership access integration and otherwise remains limited to event administrators
  • Idempotent importer from The Events Calendar — safe to re-run without duplicating already-imported records
  • No public event archive, REST-exposed event details, or direct event permalinks
  • Attach volunteers, moderators and facilitators to an event and log their hours per meeting date and role, in a generic “Volunteer roles” setting with no roles chosen by default
  • A public function other plugins can call to log or update a person’s hours on an event date
  • Plain per-date totals tables for attendance, volunteer hours and feedback, which a reporting tool can add up by month

Required framework and optional member integration

LAPDI Events requires TSP Easy Dev to be installed and active. WordPress will block LAPDI Events activation until that dependency is available and active.

LAPDI Chapters is optional. When it is active, an organizer that is hosted by us can be assigned to National or one of its chapters, and sites can rename National with the lapdi_events_national_label filter. Without it, there is no chapter choice and the organizer itself is the host.

An optional compatible membership integration can provide the access decision for “Members only” events. Without a compatible membership integration active, only users with manage_lapdi_events see Members-only events.

Installation

  1. Install and activate TSP Easy Dev. Install LAPDI Chapters too if your organization has chapters.
  2. If migrating from The Events Calendar, keep it active during the initial import.
  3. Upload LAPDI Events under Plugins → Add New → Upload Plugin and activate it.
  4. Go to Events → Import Existing Events and run the importer if migrating existing data — it copies records without changing or deleting the originals, and is safe to re-run.
  5. Review the imported Events, Venues and Organizers.
  6. Add the [lapdi_events] shortcode to your events page (commonly at /events/).
  7. Review Who can see this event? on every event — new events default to Public.
  8. To collect discussion topics, select Add poll beside a meeting under Upcoming Meetings.
  9. Deactivate The Events Calendar only after the import and public page have been verified.

FAQ

Do I need The Events Calendar plugin?

No — it’s only used as a one-time data source if you’re migrating existing events into LAPDI Events with the built-in importer. It isn’t required afterward.

How do I limit an event to logged-in members?

Edit the event and set Who can see this event? to Members only. Users approved by a compatible membership integration can view it when one is active; otherwise, only users who can manage events will see it.

Can I show events on the front end without exposing a public archive?

Yes — event, venue and organizer post types are intentionally non-public with no REST exposure or direct permalinks. Use [lapdi_events] or [lapdi_events_preview] to display them.

Can visitors add a meeting to their calendar?

Yes. Every non-cancelled event card includes Apple Calendar and Google Calendar actions. Apple Calendar downloads a standard .ics file that can also be imported into other calendar applications. Google Calendar opens Google’s event composer in a new tab. Members-only calendar details remain protected by the same access rules as the event calendar.

Does the plugin connect to external services?

Only after a visitor intentionally selects an external link. The Google Calendar action sends the event title, dates, description, location and event-page URL to Google in order to prefill its event composer. Google Maps and Apple Maps links send the venue address to the selected map provider. The .ics calendar download is generated locally and does not contact Apple. Use of those external links is subject to the Google Privacy Policy, Google Terms of Service, Apple Privacy Policy and Apple Website Terms of Use.

Which recurrence patterns are supported?

Events can occur once or repeat daily, weekly or monthly at a configurable interval. Weekly events can use an explicitly selected weekday. Monthly events can repeat on the same calendar date or on the first, second, third, fourth or last selected weekday, such as the second Tuesday. The configured start date remains the first occurrence, and the recurrence pattern controls later occurrences.

The event editor enables only the recurrence controls used by the selected Repeats option. Switching recurrence types preserves inactive weekly and monthly choices so they are restored if that type is selected again.

How do I plan individual meetings in a recurring series?

Edit the parent event and use its Upcoming Meetings panel. The panel always provides the next four active meetings in the series. Select Customize to give one meeting its own title, agenda, image, date/time, venue, organizer, meeting location, website, cost, capacity, recording or photography notice, audience or follow-up post. Details you do not change continue inheriting the parent series. A customized meeting remains linked to the series, and rescheduling it does not detach its existing attendee responses.

The parent series and each customized meeting also provide an Internal staff note. Only signed-in staff and administrators with permission to manage LAPDI Events can see it; it is never included for ordinary members or public visitors.

Can I cancel one meeting without ending the series?

Yes. Customize that meeting and select Cancel this meeting. It remains visible with a Cancelled label so attendees can see what happened, preserves existing responses, stops accepting new responses and does not consume one of the next four active meeting slots. Reinstate it by clearing the cancellation setting.

How do I link directly to one event series or meeting?

Use the parent event’s WordPress slug in the lapdi_event query parameter, for example /events/?lapdi_event=weekly-training#lapdi-events-calendar. Add lapdi_date to select that series on an exact date: /events/?lapdi_event=weekly-training&lapdi_date=2026-09-24#lapdi-events-calendar. The Upcoming Meetings panel provides a ready-made View link for each meeting. Free-text search and calendar navigation preserve the series filter. Sites whose calendar is not at /events/ can customize the generated base URL with the lapdi_events_calendar_url filter.

How can I show the next event on a landing page?

Use [lapdi_next_events] for a compact, automatically updated public-event display. It accepts series (an Event Series slug), search (the calendar’s event-text search), or both. It only returns active public events: past, cancelled, private and members-only meetings are never included. limit accepts 1 to 4; display accepts line, list or cards; and link="none" removes the default link to the exact calendar date.

The default line is {day}, {date} * {location} * {start_time}–{end_time}. Use format to choose {title}, {day}, {date}, {location}, {start_time}, {end_time} or {time}; {time} handles all-day and multi-day events. date_format and time_format accept standard WordPress/PHP date formats, while empty supplies optional text when nothing matches. For example: [lapdi_next_events series="the-other-chair" format="{day}, {date} · {location} · {time}"].

How does door check-in work?

When a member chooses Planning to attend, their confirmation email includes a check-in QR code. The image is generated by your site as a PNG, so it does not use an external QR service. Staff signed in with permission to manage LAPDI Events scan the code with a phone camera, confirm the attendee’s first name on the check-in screen and select Check in. The response becomes Attended. On members-only events this is the only way a response is marked Attended; on public events, signed-in users can also mark themselves Attended any time after the event starts. Scanning the same code again shows Already checked in. A code works only on the day of its meeting and stops working if the response is cleared, removed or the meeting is cancelled. Anyone without that permission who opens the code sees only a message asking them to show it at the door. Attendees cannot clear a response after they have been checked in.

What event-response data is stored?

When a signed-in user responds, the plugin stores the WordPress user ID, event and occurrence identifiers, response status, and created/updated timestamps in the site’s database. A Planning to attend response also receives a random check-in code that contains no name or email address; the site stores only a one-way fingerprint of it and the time it was issued. A door check-in records the check-in time and the staff account that performed it. Event administrators can view and remove all responses. Approved members can see respondent names and response statuses, while public viewers cannot. Users can clear their own responses until they are checked in. Response data stays in the site database and is included in WordPress personal data exports and erasure requests. A site administrator may let an external reporting tool read the monthly totals view described below; it holds aggregate counts only, with no names, email addresses or account IDs.

How do recording and photography notices work?

While editing an event, select whether it will be recorded and whether photography will take place. These settings apply to every meeting in a recurring series unless a customized meeting overrides them. When either setting applies, attendees must explicitly agree to the notice before choosing Planning to attend. Anyone who does not agree should not register for the event.

For Public and Members-only events, a member receives a confirmation email after a new or changed attending response. It includes the title, date and time, location, cost when configured, calendar link, applicable media notice and, for Planning to attend, the door check-in QR code. The plugin does not store a separate record of this email. A transport failure is recorded in the server error log without including the recipient address.

How does meeting capacity work?

Set Meeting capacity while editing an event. The limit applies separately to each occurrence, including recurring events. Planning to attend and Attended each occupy one seat. Unable to attend, clearing a response, or administrator removal releases the seat. Leave capacity blank or set it to 0 for unlimited attendance.

Can I respond to a past event?

No. Responses close when the meeting ends. Signed-in users see their final response instead; if they never responded, the event shows Did not attend.

How do meeting topic polls work?

Edit an event and select Add poll beside a meeting under Upcoming Meetings (titled Meeting and Poll on one-time events). Polls can be added to recurring and one-time events until the meeting starts. Add the topic choices, selection limit and deadline, change the poll to Open, and copy its link into Meetup. Open polls also appear on full event cards and show a live countdown until voting closes. Public polls use a pseudonymous browser cookie; Members-only polls require the same member access as the event. Voters pick topics from large tappable choices, can revise their ballot until voting closes and see ranked, rounded aggregate results with their own picks marked after voting. Administrators see results and anonymous suggestions under Events → Polls, grouped by event and filterable by status, and can open or close voting from that screen.

How does after-meeting feedback work?

Select Add feedback beside a meeting under Upcoming Meetings or Recent meetings. Feedback opens when the meeting ends and stays open for 3 days by default (up to 30). Voters give a 1 to 5 star rating, may pick from optional choices and may leave a comment that only administrators see. Anyone with the link can rate a public meeting; members-only meetings accept feedback only from members checked in at the door. Topic and feedback polls each have a QR code that points to the poll, with a PNG download.

Can a reporting tool read attendance totals?

Yes, through totals you build from LAPDI Events’ tables. LAPDI Events keeps no database views of its own. It stores each event date’s door check-in count and typed head count in {prefix}lapdi_event_occurrence_totals, with the date’s month and public and hosted flags, alongside the volunteer hours and feedback tables, so a reporting tool or another plugin can add them up by month without reading serialized post meta. Head counts, check-in counts and volunteer hours already recorded stay in the totals after a personal data erasure. Only aggregate counts should ever be shown to an external tool, never names, email addresses or account IDs. Versions before 1.6.0 created three totals views; upgrading drops them.

How do volunteer, moderator and facilitator hours work?

Choose which WordPress roles can be attached to an event and have hours logged against them under Events → Volunteer Roles. Nothing is chosen by default. Anyone holding a chosen role can be attached to an event from its Volunteers row, and the Volunteer Hours box logs hours in quarter-hour steps for each attached person, date and role — shown on every event, since hours count whether or not the site organized the date. A chosen role’s own name becomes the hours column heading and the value saved on each row. Other plugins can call lapdi_events_log_volunteer_hours( $event_id, $occurrence_start, $user_id, $role, $hours ) to log or update hours directly; it validates the date and role and attaches the person automatically. Hours are personal data: they are included in WordPress personal data exports, and erasing a person’s data removes their account ID while keeping the hours themselves, so recorded totals do not drop.

What happens when I delete the plugin?

Deleting LAPDI Events permanently deletes all events, venues, organizers, event categories, event series, attendee responses, poll ballots, volunteer hours, attendance totals, the “Volunteer roles” setting, any reporting views left from earlier versions, and related plugin data. This cannot be undone; create a database backup before deleting the plugin. Ordinary deactivation does not remove data.

Changelog

1.7.3

  • Public events now let signed-in users mark themselves Attended any time after the event starts, including long after it ends. Someone who said Planning to attend can switch to Attended directly, and a self-reported attendance can be cleared. Members-only events still require a door check-in.

1.7.2

  • Add [lapdi_next_events] for a public landing-page-friendly view of the next one to four active events. Filter by Event Series (series) and/or event text (search), choose line, list, or cards output, and tailor the compact text with tokens such as {day}, {date}, {location}, {start_time}, {end_time}, {time}, and {title}. Past, cancelled, private, and members-only events are never displayed.

1.7.1

  • The calendar’s repeat badge and the admin Recurrence column now show the real cadence, such as “Every 6 weeks”, when a series repeats on an interval above 1. An interval of 1 still shows Daily, Weekly or Monthly.

1.7.0

  • Added Event Series. Create series under Events > Event Series, assign one or more to each event, and visitors can filter the calendar’s List, Month and Day views by series. [lapdi_events series="slug"] and [lapdi_events_preview series="slug"] show a single series. Uninstall removes the series terms.

1.6.2

  • Saving a recurring parent event repairs inherited end times for future linked meetings without shifting meeting dates or altering past meetings. Explicit meeting end-time overrides remain unchanged.

1.6.1

  • The upgrade now drops an old reporting view only when it still exists, instead of running a drop statement for all three every time. A drop statement commits any open database transaction, which broke the plugin’s own automated tests.

1.6.0

  • Remove the three totals views, {prefix}lapdi_events_impact_totals, {prefix}lapdi_events_category_totals and {prefix}lapdi_events_volunteer_hours_totals, and their admin notices. The upgrade drops the views and their options. The totals tables behind them (attendance per event date, door check-ins, volunteer hours and feedback) stay and keep updating, so a reporting tool can build its totals from them.
  • Permanently deleting an event now removes its head counts and check-in counts from the totals table, along with the volunteer hours and feedback already removed.
  • The upgrade deletes totals rows left behind by events or meetings that no longer exist, so events deleted on earlier versions stop counting.
  • Update the privacy policy guide to describe the totals tables instead of the views.

1.5.0

  • Add a generic “Volunteer roles” setting under Events → Volunteer Roles, with no roles chosen by default.
  • Add a Volunteers row to the event editor, listing users who hold a chosen role with that role shown beside their name, and a Volunteer Hours box that logs hours in quarter-hour steps per person, date and role on every event, hosted or not.
  • Add lapdi_events_log_volunteer_hours(), a public function other plugins can call to log or update a person’s hours on an event date and role, validating the date and role and attaching the person automatically.
  • Add volunteer hours to personal data exports, and an eraser that removes a person’s account ID from their hours rows while keeping the hours total intact.
  • Add volunteer_hours, volunteers_month, volunteers_ytd, feedback_average and feedback_responses to the {prefix}lapdi_events_impact_totals view, and change which months appear in it: a month now also qualifies from volunteer hours or feedback responses alone, with zero in the attendance columns, since neither is limited to dates the site organized.
  • Add two totals-only views, {prefix}lapdi_events_category_totals (events held by month and event category) and {prefix}lapdi_events_volunteer_hours_totals (hours and distinct people by month and role), since categories and volunteer roles are both defined per site rather than fixed columns.
  • Resolve and store each feedback ballot’s event, occurrence and month at the time it is cast, backfilled for ballots recorded before this release, so feedback totals can be read without a join back to posts.

1.4.1

  • Add a totals-only database view, {prefix}lapdi_events_impact_totals, with one row per month of events held, head counts, unique participants and repeat participants, so an external reporting tool can read attendance totals without access to any names, email addresses or account IDs.
  • Keep each event date’s head count and door check-in count in a plain totals table so the view can add them up, filled from existing head counts and check-ins on upgrade. Recorded totals stay after a personal data erasure.
  • Show an admin notice when the site’s database user cannot create the view.
  • Update the privacy policy guide and readme to say that only aggregate counts may be read by an external reporting tool.
  • Add after-meeting feedback polls. Each meeting can have a feedback poll next to its topic poll; it opens when the meeting ends and stays open for 3 days by default (1 to 30). Voters give a 1 to 5 star rating, optional choices and an optional comment that only administrators see. Members-only meetings accept feedback only from members checked in at the door.
  • Add feedback from the Upcoming Meetings panel or a new Recent meetings list covering the last 30 days, and show Share your feedback on past event cards to people allowed to give it. Member feedback is included in personal data exports and erasure requests, and uninstall removes it.
  • Redesign the public poll page with tappable topic choices, a picks counter, a live countdown, ranked animated results that mark the voter’s own picks, and a Change my vote option.
  • Redesign Events → Polls with totals, status filters, open, draft and closed views, results beside suggestions or comments, Open and Close voting actions and an average rating total.
  • Give every topic poll and feedback poll a QR code with a PNG download.
  • Fold the meeting editor’s schedule and details behind a one-line summary and show the topic poll and feedback poll in tabs with status badges.
  • Show events set to WordPress Private visibility on the calendar to users who can manage events, labeled Private and without RSVP controls, and let them preview those events’ polls.
  • Retitle the meetings panel on one-time events and explain when an event is already over.
  • List a meeting that is in progress once on the calendar instead of twice.
  • Keep the Excerpt box last and collapsed on event and meeting screens, even when a user has rearranged the boxes.

1.4.0

  • Add verified door check-in for members-only events: each Planning to attend response receives a random check-in code emailed as a QR image generated on the site, with no external QR service. Public events are open walk-up events, so their confirmation emails have no check-in QR code.
  • Add a staff-only check-in screen that marks the response Attended after staff confirm the attendee’s first name, with already-checked-in, wrong-day and invalid-code messages.
  • Accept check-in codes only on the day of their meeting and cancel them when a response is cleared, changed to Unable to attend or removed.
  • Show check-in times and the checking staff member in the administrative attendee log.
  • Make door check-in the only way a response becomes Attended, and prevent attendees from clearing a response after they are checked in.
  • Include check-in details in personal data exports and the privacy policy guide.
  • Slim down the event editor: start, end and all-day share one row, recurrence fields appear only when they apply, and event details are grouped into Basics, Location and Attendance with the internal note, event code and recap post under a collapsible More options section.
  • Add venues and organizers from a short popup on the event editor without leaving the page; the new item is selected in its dropdown right away.
  • Move the Excerpt box below the event fields on the event and meeting editors.
  • Add a Head Count box to events we host so staff can enter how many people came to each meeting, shown beside the number who planned to attend. On members-only events the head count defaults to the number of people checked in at the door until staff enter a different number.
  • Show head counts in a new column on the Events list, and add an organizer filter to that list.
  • Add a Hosted by us checkbox to organizers, with a chapter choice (including National) when LAPDI Chapters is active. Events whose organizer is not hosted by us skip capacity, media notice, event code, door check-in and head count.
  • Show the chapter choice only when LAPDI Chapters is active; without it the organizer itself is the host. Add the lapdi_events_national_label filter for renaming National.
  • Send the home-page preview’s View all events link and the RSVP fallback return link through the lapdi_events_calendar_url filter, and make the empty calendar message neutral.

1.3.3

  • Add independent recording and photography notices with required consent before an attendee registers, including inherited overrides for customized recurring meetings.
  • Send an RSVP confirmation email for a new or changed attending response, for both Public and Members-only events, and record a server error when delivery fails.
  • Persist accepted media consent with each RSVP, retain it until the response is cleared, and lock an attending response from further edits.
  • Close RSVP controls after a meeting ends and show each signed-in user’s final response or Did not attend.
  • Add an Email Settings page (Events → Email Settings) with a logo and an HTML template for RSVP confirmation emails; emails now send as HTML, with the media-consent section hidden entirely when no restriction applies.
  • Queue the RSVP attendance confirmation email for 2 minutes instead of sending it immediately, so a response cleared within that window sends no email at all.
  • Send a separate Event Cancellation email, using a second independently editable template selectable from a dropdown on the Email Settings page, when a response is cleared after its attendance confirmation already went out.
  • Fix attendee removal from the event editor by avoiding a nested form that sent administrators to the posts list.

1.3.2

  • Add a bounded public API for dependent plugins to search dated meeting identities without reading LAPDI Events metadata directly.

1.3.1

  • Restore the complete, self-contained event poll presentation in the public release.
  • Present topic voting as a clear event-card button and place calendar labels above their buttons.
  • Improve standalone poll typography, spacing, choices, forms, notices, results and responsive behavior without depending on an active theme.

1.3.0

  • Add unique event codes with linked-meeting inheritance and overrides.
  • Add locally generated event-destination QR previews and SVG downloads.
  • Expose bounded event identity functions for optional consumers without adding plugin dependencies.
  • Add per-meeting multiple-choice topic polls with opaque share links and calendar actions.
  • Add revisable anonymous or member ballots, optional topic suggestions and deadline enforcement.
  • Add event-grouped administration with rounded aggregate results and no voter identity display.

1.2.0

  • Add per-occurrence Apple Calendar .ics downloads and Google Calendar event links.
  • Export customized recurring-meeting titles, schedules, descriptions, venues and meeting locations.
  • Ensure Google Calendar receives a non-empty event title before optional event details.
  • Protect members-only calendar downloads with the existing event visibility checks.

1.1.0

  • Add optional per-occurrence meeting capacity and available-seat display.
  • Prevent new attending responses when an occurrence is full, including simultaneous final-seat requests.
  • Release seats when users become unable to attend, clear their response, or have their response removed.
  • Add an explicit weekday selector for weekly recurrence.
  • Add first, second, third, fourth and last weekday patterns for monthly recurrence.
  • Preserve existing monthly same-date behavior and existing event schedules by default.
  • Add a rolling four-meeting planning window for every recurring series.
  • Add linked per-meeting detail overrides with field-level inheritance from the parent series.
  • Preserve RSVP and capacity identity when an individual meeting is rescheduled.
  • Add individual meeting cancellation and reinstatement while retaining response history.
  • Add inheritable per-meeting internal notes visible only to event staff and administrators.
  • Add exact event-series URL filtering, optional date intersection and ready-made meeting links.
  • Enable only recurrence fields relevant to the selected repeat pattern while preserving inactive settings.

1.0.0

  • Initial public release.
  • Manage recurring public and member events, venues, organizers and categories.
  • Display accessible List, Month, Day and preview calendars.
  • Import existing records idempotently from The Events Calendar.
  • Record per-occurrence member responses and provide an administrative attendee log.
  • Support WordPress personal-data exports, erasure requests and privacy-policy guidance.
  • Attach published blog-post follow-ups to events for recaps, photos and video.
  • Require TSP Easy Dev using WordPress’s dependency header and path-independent runtime detection.
  • Provide the Events information page under LAPDI Plugins.
  • Remove all LAPDI Events content and plugin-owned data safely after an administrator confirms permanent plugin deletion.