bmltenabled

radius314

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/.
<ol>
<li>
Event Submission and Approval:
<ul>
<li>Users can submit events through a public-facing form.</li>
<li>Submitted events are saved as pending, requiring admin approval before they are published.</li>
<li>Admins receive email notifications upon new event submissions, ensuring timely review and approval.</li>
</ul>
</li>
<li>
Recurring Events:
<ul>
<li>Supports daily, weekly, and monthly recurring event patterns.</li>
<li>Users can specify recurrence intervals and end dates.</li>
<li>Recurring events are automatically generated based on the specified pattern.</li>
</ul>
</li>
<li>
Event Details and Customization:
<ul>
<li>Events can include detailed information such as event type, start and end dates, times, and location details.</li>
<li>Supports the use of WordPress’s featured image functionality to visually represent events.</li>
<li>Allows categorization and tagging of events for better organization and filtering.</li>
</ul>
</li>
<li>
Service Body Integration:
<ul>
<li>Integrates with external service bodies, allowing users to associate events with specific service organizations.</li>
<li>Fetches and displays service body information dynamically.</li>
</ul>
</li>
<li>
Email Notifications:
<ul>
<li>Sends email notifications to the site admin when a new event is submitted.</li>
<li>Ensures that admins are promptly informed of new submissions for review.</li>
</ul>
</li>
<li>
REST API Integration:
<ul>
<li>Provides REST API endpoints for submitting events, retrieving event details, and managing settings.</li>
<li>Facilitates integration with other systems and custom front-end applications.</li>
</ul>
</li>
<li>
User-Friendly Interface:
<ul>
<li>Intuitive form interface for event submission, including validation for required fields like email.</li>
<li>Admin interface for managing events, including viewing, editing, and approving submissions.</li>
</ul>
</li>
<li>
Event Announcements:
<ul>
<li>Display event-based announcements as banners or modals to highlight important information.</li>
<li>Use events to announce meeting closures, moves, new meetings, or promote upcoming events.</li>
<li>Events show as announcements when today’s date falls between the event’s start and end dates.</li>
<li>Supports filtering by categories and tags to control which events appear as announcements.</li>
<li>Dismissable with 24-hour persistence – users can re-open via a bell icon.</li>
</ul>
</li>
</ol>
<h3>Announcement Feature</h3>
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:
<pre><code>[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
</code></pre>
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
<h3>Additional Information</h3>
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:
<ul>
<li>Dynamic classes generated based on event properties</li>
<li>Examples of how to customize the appearance</li>
</ul>
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:
<ul>
<li>Styling specific categories or tags</li>
<li>Customizing the appearance of different event types</li>
<li>Adding styles for specific service bodies</li>
</ul>
Recommended CSS Plugins
<ul>
<li>Simple Custom CSS (https://wordpress.org/plugins/simple-custom-css/)</li>
<li>Custom CSS and JS (https://wordpress.org/plugins/custom-css-js/)</li>
<li>Advanced Custom CSS (https://wordpress.org/plugins/advanced-custom-css/)</li>
</ul>
Development
Prerequisites
<ul>
<li>Node.js (v14 or higher)</li>
<li>npm (v6 or higher)</li>
</ul>
Installation
<ol>
<li>Clone the repository</li>
<li>
Install dependencies:
npm install
</li>
<li>
Build the plugin:
npm run build
</li>
</ol>
Development Workflow
<ol>
<li>
Start the development server:
npm run dev
</li>
<li>
Make changes to the code
</li>
<li>Rebuild the plugin as needed</li>
</ol>
License
This project is licensed under the GPL v2 or later.
<h3>Technical Details</h3>
<ul>
<li>Custom Post Type: Utilizes a custom post type <code>mayo_event</code> to store and manage events.</li>
<li>JavaScript Components: Built with React and integrated into the WordPress admin and front-end using Gutenberg components.</li>
<li>Email Handling: Uses WordPress’s <code>wp_mail</code> function to send notifications.</li>
<li>Data Storage: Stores event metadata using WordPress’s post meta system, ensuring compatibility and scalability.</li>
</ul>

Mayo Events Manager

Pronounced "my-oh".  Referring to the Spanish word "mayo" which means "May" in English.  Mayo Event Manager is a compreh …

pjaudiomv

Crumb is a lightweight WordPress plugin that embeds the <a href="https://crumb.bmlt.app/" rel="nofollow ugc">Crumb Widget</a> meeting finder on any page or post using a simple shortcode.
Features:
<ul>
<li>List and map views with real-time search and filters</li>
<li>Meeting detail with directions and virtual meeting join link</li>
<li>Multi-language support</li>
<li>Shareable per-meeting URLs</li>
</ul>
<h4>Usage</h4>
Add the shortcode to any page or post:
<pre><code>[crumb]
</code></pre>
Override settings per page:
<pre><code>[crumb server="https://your-server/main_server" service_body="42" format_ids="17,54" view="map" geolocation="true" geolocation_radius="30"]
</code></pre>
Shortcode attributes:
<ul>
<li><code>server</code> — BMLT server URL (overrides the value set in Settings → Crumb)</li>
<li><code>service_body</code> — Service body ID or comma-separated list; leave empty to show all meetings</li>
<li><code>format_ids</code> — Format ID or comma-separated list of BMLT format IDs to lock the widget to; leave empty to show all formats</li>
<li><code>view</code> — Default view when the widget loads: <code>list</code> (default), <code>map</code>, or <code>both</code> (map above list with no toggle); can also be overridden at runtime via the <code>?view=</code> query parameter</li>
<li><code>geolocation</code> — Enable or disable geolocation for this page: <code>true</code> or <code>false</code></li>
<li><code>geolocation_radius</code> — Geolocation search radius. Positive integer = fixed radius in miles (or km per server settings). Negative integer = BMLT auto-radius: the server expands the search until it finds roughly that many meetings (e.g. <code>-50</code> finds ~50 nearby meetings). Overrides the Geolocation Radius setting and Widget Configuration.</li>
<li><code>update_url</code> — URL template for the Update Meeting Info link shown at the bottom of the meeting detail panel. Supports tokens <code>{meeting_id}</code>, <code>{meeting_name}</code>, <code>{server_url}</code>, <code>{return_url}</code> (URL-encoded on substitution). Works with bmlt-workflow, hosted forms, or <code>mailto:</code> URLs.</li>
<li><code>columns</code> — Comma-separated list of columns to show in list view (e.g. <code>time,name,location,address,service_body</code>). Omit a name to hide that column. Leave unset to use the widget default.</li>
<li><code>language</code> — Force the widget UI language for this page (e.g. <code>en</code>, <code>es</code>, <code>fr</code>, <code>de</code>, <code>pt</code>, <code>it</code>, <code>sv</code>, <code>da</code>, <code>el</code>, <code>fa</code>, <code>pl</code>, <code>ru</code>, <code>ja</code>). Leave unset to auto-detect from the visitor’s browser.</li>
<li><code>query</code> — Raw BMLT query string passed through to the widget’s <code>rawQuery()</code> for filters the structured options can’t express (e.g. multi-value <code>meeting_key_value[]</code>). When set, this replaces the default load entirely — <code>service_body</code>, <code>format_ids</code>, and <code>?services</code> are ignored — and forces geolocation off (the widget can’t safely layer lat/long/geo_width on top of an arbitrary query). Encode brackets as <code>%5B</code> / <code>%5D</code> because WordPress shortcodes can’t contain literal <code>[</code> or <code>]</code>. Example: <code>[crumb query="meeting_key=location_nation&meeting_key_value%5B%5D=USA"]</code>. Shortcode-only; no admin setting.</li>
</ul>
<h4>Switching from Crouton</h4>
Crumb is an alternative to the <a href="https://wordpress.org/plugins/crouton/" rel="ugc">crouton</a> plugin and can drop in without page edits in most cases. Activating Crumb will:
<ul>
<li>Register the crouton shortcodes (<code>[bmlt_tabs]</code>, <code>[bmlt_map]</code>, <code>[crouton_tabs]</code>, <code>[crouton_map]</code>) and translate them to the Crumb widget. Map shortcodes render with <code>view="both"</code> (map + list) and tabs shortcodes render with <code>view="list"</code>. Shortcode attributes <code>root_server</code>, <code>service_body</code>, <code>service_body_1</code>, <code>formats</code>, <code>report_update_url</code>, and <code>query_string</code> are mapped to their Crumb equivalents (<code>query_string</code> becomes <code>data-query</code> and routes through the widget’s <code>rawQuery()</code>).</li>
<li>Reuse crouton’s saved settings as fallbacks when the corresponding Crumb option is empty (BMLT server URL, service bodies, format IDs, update URL). Open Settings → Crumb to confirm the inherited values and click Save Changes to persist them.</li>
</ul>
Crumb only handles those shortcodes when crouton is deactivated — if both plugins are active, crouton continues to handle its own shortcodes. To switch: install Crumb, then deactivate crouton. No page edits required.
<h4>Documentation</h4>
Full documentation at <a href="https://crumb.bmlt.app/" rel="nofollow ugc">crumb.bmlt.app</a>.
<h3>External services</h3>
This plugin relies on two external services. Both are part of the BMLT (Basic Meeting List Toolkit) ecosystem — free, open-source tools built for Narcotics Anonymous service bodies (https://bmlt.app).
1. Crumb Widget CDN
The widget JavaScript is loaded from a CDN operated by the BMLT project.
<ul>
<li>Service: cdn.aws.bmlt.app — delivers the Crumb Widget JavaScript file</li>
<li>Purpose: Provides the JavaScript component that renders the meeting list interface</li>
<li>Data sent: Standard HTTP request headers (IP address, browser user-agent, referring URL). No personal or meeting-search data is sent to the CDN.</li>
<li>When: The script is loaded once per page load on any page that contains the [crumb] shortcode</li>
<li>Privacy policy: https://crumb.bmlt.app/privacy.html</li>
<li>Terms of use / License: https://github.com/bmlt-enabled/crumb-widget/blob/main/LICENSE</li>
</ul>
2. BMLT Server (meeting data)
The widget fetches meeting data from a BMLT server whose URL you configure in Settings → Crumb. This server is typically operated by a regional NA service body and is not a service operated by the Crumb project.
<ul>
<li>Service: Your configured BMLT server (e.g. https://your-region.bmlt.app/main_server/)</li>
<li>Purpose: Retrieve NA meeting listings (names, times, locations, formats) to display in the widget</li>
<li>Data sent: Search query parameters (filters, keyword, selected formats). If geolocation is enabled and the user consents via a browser prompt, the user’s geographic coordinates are also sent to this server.</li>
<li>When: On each search or filter action within the widget</li>
<li>Privacy policy: Determined by the operator of your configured BMLT server. Learn more at https://bmlt.app.</li>
</ul>

Crumb

Embeds the Crumb Widget NA meeting finder on any page or post via a simple shortcode.

Mayo Events Manager vs Crumb