Mayo Events Manager
Pronounced “my-oh”. Referring to the Spanish word “mayo” which means “May” in English. Mayo Event Manager is a comprehensive WordPress plugin designed to facilitate the management of events with a focus on community…
Use with caution
Mayo Events Manager works, but test it on a staging site before relying on it in 2026. It runs on 50+ sites and was last updated 1 month ago, and scores 59/100 on our health check.
- Small user base (50+ active installs)
- Very few reviews so far
- Needs PHP 8.2 or newer
How does it stack up?
Side-by-side on installs, updates, ratings & support
Daily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Mayo Events Manager stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| bmlt | #12 |
| events | >100 |
| na | #72 |
| narcotics anonymous | #5 |
Version adoption
Share of active sites per release.
About Mayo Events Manager
From the official readme · v1.9.5Description
Pronounced “my-oh”. Referring to the Spanish word “mayo” which means “May” in English. Mayo Event Manager is a comprehensive WordPress plugin designed to facilitate the management of events with a focus on community engagement and administrative oversight. This plugin allows users to submit events for approval, supports recurring event schedules, and integrates seamlessly with WordPress’s native features like featured images and custom post types. Mayo is meant to be simple, and does not provide all the functionality of a typical event management system. It is designed to be used in conjunction with a BMLT server to provide a simple way to submit events for a specific service body. Also we will not be implementing a calendar view, but rather a list view. There are plenty of other plugins that provide calendar views, and you can make use of the calendar RSS to import the feeds you want.
Dependency on Pretty Permalinks: The REST API utilizes the same URL rewriting functionalities that pretty permalinks employ to map its human-readable routes (like /wp-json/wp/v2/posts) to the appropriate internal processes. If your site uses the “Plain” permalink setting (which is the default in some cases), the REST API endpoint may not function correctly, leading to 404 errors when attempting to access /wp-json/.
-
Event Submission and Approval:
- Users can submit events through a public-facing form.
- Submitted events are saved as pending, requiring admin approval before they are published.
- Admins receive email notifications upon new event submissions, ensuring timely review and approval.
-
Recurring Events:
- Supports daily, weekly, and monthly recurring event patterns.
- Users can specify recurrence intervals and end dates.
- Recurring events are automatically generated based on the specified pattern.
-
Event Details and Customization:
- Events can include detailed information such as event type, start and end dates, times, and location details.
- Supports the use of WordPress’s featured image functionality to visually represent events.
- Allows categorization and tagging of events for better organization and filtering.
-
Service Body Integration:
- Integrates with external service bodies, allowing users to associate events with specific service organizations.
- Fetches and displays service body information dynamically.
-
Email Notifications:
- Sends email notifications to the site admin when a new event is submitted.
- Ensures that admins are promptly informed of new submissions for review.
-
REST API Integration:
- Provides REST API endpoints for submitting events, retrieving event details, and managing settings.
- Facilitates integration with other systems and custom front-end applications.
-
User-Friendly Interface:
- Intuitive form interface for event submission, including validation for required fields like email.
- Admin interface for managing events, including viewing, editing, and approving submissions.
-
Event Announcements:
- Display event-based announcements as banners or modals to highlight important information.
- Use events to announce meeting closures, moves, new meetings, or promote upcoming events.
- Events show as announcements when today’s date falls between the event’s start and end dates.
- Supports filtering by categories and tags to control which events appear as announcements.
- Dismissable with 24-hour persistence – users can re-open via a bell icon.
Announcement Feature
The announcement feature allows you to display event-based announcements prominently on your site. This is useful for:
* Meeting closures or changes
* New meeting announcements
* Breaking news or important updates
* Promoting upcoming events
Shortcode Usage:
[mayo_announcement] - Display announcements with default settings (banner mode)
[mayo_announcement mode="modal"] - Display as a modal popup instead of banner
[mayo_announcement categories="announcements,alerts"] - Filter by category slugs
[mayo_announcement tags="urgent,featured"] - Filter by tag slugs
[mayo_announcement time_format="24hour"] - Use 24-hour time format
[mayo_announcement background_color="#ff6600" text_color="#ffffff"] - Custom colors
[mayo_announcement background_color="#dc3545" text_color="#fff" categories="alerts"] - Red alert style
Parameters:
* mode – “banner” (sticky top bar) or “modal” (popup). Default: “banner”
* categories – Comma-separated category slugs to filter events
* tags – Comma-separated tag slugs to filter events
* time_format – “12hour” or “24hour”. Default: “12hour”
* background_color – Custom background color (hex, e.g., “#ff6600”). Default: CSS default
* text_color – Custom text color (hex, e.g., “#ffffff”). Default: CSS default
Widget Usage:
For site-wide announcements without editing templates, use the “Mayo Event Announcements” widget:
1. Go to Appearance > Widgets
2. Add the “Mayo Event Announcements” widget to any widget area (footer recommended for site-wide display)
3. Configure the display mode, categories, tags, and time format
How It Works:
* Events appear as announcements when today’s date is between the event’s start_date and end_date
* Banner mode shows a fixed bar at the top of the viewport with carousel navigation for multiple events
* Modal mode shows a centered popup with a list of all matching events
* When dismissed, announcements stay hidden for 24 hours but can be re-opened via a bell icon in the bottom-right corner
Additional Information
Mayo WordPress Plugin
A WordPress plugin for managing and displaying events from a BMLT root server.
CSS Documentation
The plugin includes documentation for the dynamic CSS classes used in the Event Card component. This helps developers understand and customize the appearance of events on their site.
Important Note About Styling
This plugin does not include a built-in CSS editor. To style the event cards, you need to use another plugin like “Simple Custom CSS” or add CSS to your theme’s stylesheet. The documentation is provided to help you understand which CSS classes are available for styling.
Viewing the Documentation
The CSS documentation is available in the WordPress admin area under the Mayo menu. It includes:
- Dynamic classes generated based on event properties
- Examples of how to customize the appearance
Customization
You can customize the appearance of events by adding CSS rules to your theme or using a custom CSS plugin. The documentation provides examples of common customizations, such as:
- Styling specific categories or tags
- Customizing the appearance of different event types
- Adding styles for specific service bodies
Recommended CSS Plugins
- Simple Custom CSS (https://wordpress.org/plugins/simple-custom-css/)
- Custom CSS and JS (https://wordpress.org/plugins/custom-css-js/)
- Advanced Custom CSS (https://wordpress.org/plugins/advanced-custom-css/)
Development
Prerequisites
- Node.js (v14 or higher)
- npm (v6 or higher)
Installation
- Clone the repository
-
Install dependencies:
npm install
-
Build the plugin:
npm run build
Development Workflow
-
Start the development server:
npm run dev
-
Make changes to the code
- Rebuild the plugin as needed
License
This project is licensed under the GPL v2 or later.
Technical Details
- Custom Post Type: Utilizes a custom post type
mayo_eventto store and manage events. - JavaScript Components: Built with React and integrated into the WordPress admin and front-end using Gutenberg components.
- Email Handling: Uses WordPress’s
wp_mailfunction to send notifications. - Data Storage: Stores event metadata using WordPress’s post meta system, ensuring compatibility and scalability.
Installation
-
Installation:
- Upload the plugin files to the
/wp-content/plugins/mayo-event-managerdirectory. - Activate the plugin through the ‘Plugins’ menu in WordPress.
- Upload the plugin files to the
-
Configuration:
- Set up the BMLT root server URL in the plugin settings for service body integration.
- Configure email settings to ensure notifications are sent correctly.
-
Usage:
- Use the provided shortcode or block to display the event submission form on any page.
- Manage submitted events from the WordPress admin dashboard, where you can approve, edit, or delete events.
Changelog
1.9.5
- Fixed the event and announcement submission forms overflowing their container and clipping the Hour/Minute/AM-PM time dropdowns when the form is placed in a narrow column, such as a page with a fixed or sticky sidebar. The date and time controls now wrap to fit the space available and the dropdowns keep a legible minimum width, so the “Hour” and “Min” labels and selected values are no longer cut off. [#328]
1.9.4
- Fixed event submission form showing empty Categories or Tags section headers when
categories="none"ortags="none"is used in[mayo_event_form]. [#325] - Documented that category and tag names with spaces should use dashes in shortcode parameters (e.g., a category named “Cell Awareness” is specified as
cell-awarenessin[mayo_announcement_form]). [#321] - Fixed required start/end date and time fields on the announcement submission form not showing an asterisk (*) on their labels when marked required via
additional_required_fields. The optional “Leave empty to…” hints are now hidden when those fields are required. [#319] - Fixed the event filters resetting the calendar back to the current month: selecting a Service Body, Category, Tag, or Event Type filter now keeps the month you had navigated to instead of jumping back to today. [#251]
- Fixed the filter dropdown staying open after you pick a value; it now closes automatically so it no longer covers the first days of the calendar. [#251]
- Fixed external feed sources ignoring the Event Type filter: filtering on Service (or Activity) now actually hides the other types coming from external feeds, even when the remote runs an older version or isn’t a Mayo site. [#251]
1.9.3
- Fixed display filters not combining correctly across local and external event feeds: selecting a category or tag that exists only on an external source now hides all local events instead of showing every local match for the other facets. [#323]
- Fixed external feed events not being re-filtered locally for Service Body and Tag selections, which could let non-matching events leak through from older or non-Mayo remote sites. [#323]
- Added a “Relative to a monthly day” monthly recurrence option so committee meetings can be scheduled relative to a monthly anchor (e.g. the Monday before the 3rd Tuesday, or the Thursday after it). Available in the block-editor Event sidebar. [#312]
1.9.2
- Fixed the event and announcement submission forms overlapping the End Date/Time field on top of the Start Date/Time field, which happened after Start/End time became Hour/Minute/AM-PM dropdowns. [#310]
- Added date defaults to the event submission form: the Start Date now pre-fills to today’s date and the End Date automatically matches the Start Date (until you set a different end date), so single-day events need only one date entry. [#301]
- Added a JavaScript example (docs/rest-api-javascript-example.md) showing how to pull events from the REST API filtered by service body and tag, resolving the human-readable names to the id/slug the API expects via the facets endpoint. [#302]
- Fixed the event and announcement submission forms forcing 24-hour (“military”) time entry regardless of site settings. Start/End time now follow the WordPress “Time Format” setting (Settings → General), showing 12-hour Hour/Minute/AM-PM selects by default, and can be overridden per form with a new
time_format="12hour|24hour"shortcode option. [#300] - Fixed the calendar view showing an unnecessary scrollbar on every day cell. Day cells now only scroll internally when they actually contain more events than fit. [#298]
- Added event-type exclusion to the event list: prefix a type with “-” to hide it (e.g.
event_type="-Celebration"shows Service and Activity events), or list the types to keep (event_type="Service,Activity"). Exclusion is future-proof — any event types added later stay visible automatically. [#296] - Fixed external feed sources ignoring their configured category filter: a category set on an external source now actually narrows which events are imported, even when the remote site runs an older version, isn’t a Mayo site, or uses different category slugs. Previously an unmatched category was silently dropped and the source returned all of its events. Sources with no category configured are unaffected. [#292]
1.9.1
- Fixed the event list filter bar omitting event types that had no currently scheduled events; the Event Type filter now always offers the full set (Service, Activity, Celebration) regardless of what’s on the calendar. [#290]
- Fixed a race where toggling filters while the event list was still loading could leave the selection in an inconsistent state; the filter bar is now disabled (greyed out) while a request is in flight. [#290]
- Added an optional private phone-number contact field to the event and announcement submission forms. It is hidden by default and enabled per-form with the new
show_phoneshortcode option; addphonetoadditional_required_fieldsto make it mandatory. Like the contact email, the number is stored privately for organizers and is never displayed publicly. [#288] - Bumped declared WordPress compatibility to 7.0 (Tested up to) and added matching
Requires at leastandTested up toheaders to the main plugin file so the WordPress.org parser sees consistent values. [#286] - Updated the build-time axios dependency to resolve npm security advisories. The dependency is dev-only and never ships to site visitors. [#284]
- Added validation of the BMLT root server URL on save: malformed URLs and hosts that aren’t a reachable BMLT root server are now rejected with a clear error instead of being saved silently, plus a “Test connection” button in Settings to verify the server without saving. [#282]
- Fixed external feed sources ignoring the visitor’s event type and service body filters; user-selected filters now override each source’s admin-pinned defaults so a “Service” filter no longer surfaces “Activity” events pulled from a remote feed. [#279]
- Added a subscribable ICS calendar feed so Google Calendar, Apple Calendar, and Outlook keep syncing newly approved events automatically. The calendar icon on the event list now opens a Subscribe panel with the feed URL, a webcal:// quick-subscribe link, a one-time .ics download, and Google Calendar instructions. Recurring events now emit proper RRULE/EXDATE so series display as a single repeating event in subscribers’ calendars instead of one-shot duplicates, and each event’s original timezone is preserved via VTIMEZONE blocks. [#277]
1.9.0
- Added a filter bar above the event list and calendar. Visitors pick filters from compact dropdowns (event type, service body, category, tag); selected values appear as removable chips and combine with OR semantics within a facet and AND across facets. Options are populated from the actual events in scope, including service bodies surfaced by external feeds, and any filter pinned by a shortcode attribute stays locked. [#251]
- Fixed issue with long caching mechanisms like Cloudflare to avoid using nonces for readonly API calls [#271]
- Added multilingual support: the plugin now declares the
mayo-events-managertext domain, ships alanguages/mayo-events-manager.pottemplate, and loads PHP and JavaScript translations so events, announcements, forms, subscription pages, and admin labels can be translated into any locale. [#268] - Added pre-populated translation files for Spanish (es_ES), Portuguese-Brazil (pt_BR), and French (fr_FR) with best-guess translations for all 354 strings. [#268]
- Generate compiled translation files (
.mo, per-handle.json) at release time from.posources instead of committing them, keeping the repository free of derived artifacts. [#273]
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best Mayo Events Manager alternatives
All bmlt plugins →
FAQ
Mayo Events Manager: quick answers
Straight answers, pulled from live WordPress.org data.
Live data from WordPress.org · checked Sep 28, 2026
Is Mayo Events Manager free?
Yes. Mayo Events Manager is free to download and use from the official WordPress.org plugin directory.
Is Mayo Events Manager safe to use in 2026?
Mayo Events Manager works, but test it on a staging site before relying on it in 2026. It runs on 50+ sites and was last updated 1 month ago, and scores 59/100 on our health check.
How many websites use Mayo Events Manager?
Mayo Events Manager is active on 50+ WordPress websites and has been downloaded 4,060 times since it launched in March 2025. It was downloaded 145 times in the last 30 days.
Does Mayo Events Manager work with WordPress 7.1?
Mayo Events Manager is officially tested up to WordPress 7.0.6, while the latest release is 7.1.2. It may still work, but try it on a staging site first.
What PHP version does Mayo Events Manager need?
Mayo Events Manager requires PHP 8.2 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Mayo Events Manager last updated?
The latest version, 1.9.5, was released on August 19, 2026 (1 month ago).
Who makes Mayo Events Manager?
Mayo Events Manager is developed and maintained by bmltenabled.
What are the best alternatives to Mayo Events Manager?
The most popular alternatives to Mayo Events Manager are crouton (300+ installs), Bread (300+ installs) and Fetch Meditation (100+ installs).
Powered by PageForge
Want thousands of pages that rank like these? Build them in an afternoon.
This directory runs on the same engine as PageForge. Turn any spreadsheet, CSV or API into thousands of fast, SEO-ready WordPress pages — with schema, internal links and AI-written copy baked in.
- CSV, Google Sheets & API data sources
- AI content, schema & internal links per page
- Works with Elementor, Gutenberg, Yoast & Rank Math
- Free on WordPress.org — no credit card
