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>
</ol>
<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

Temporary Closures BMLT is a plugin that displays a list of all meetings that have temporary closures. It can be used 
to view published or unpublished meetings.
SHORTCODE 
Basic: [temporary_closures] 
Attributes: root_server, services, recursive, display_type, custom_query, sortby
— Shortcode parameters can be combined
<h3>Usage</h3>
A minimum of root_server, and services attributes are required.
Ex. [temporary_closures root_server="https://www.domain.org/main_server" services="50"]
recursive to recurse service bodies add recursive="1" 
Ex. [temporary_closures root_server="https://www.domain.org/main_server" services="50" recursive="1"]
services to add multiple service bodies just separate by a comma. 
Ex. [temporary_closures root_server="https://www.domain.org/main_server" services="50,37,26"]
display_type To change the display type add display_type="table" there are three different types table, block, datatables 
Ex. [temporary_closures root_server="https://www.domain.org/main_server" display_type="table"]
custom_query You can add a custom query from semantic api to filter results, for ex by format <code>&formats=54</code>. 
Ex. [temporary_closures root_server="https://www.domain.org/main_server" custom_query="&formats=54"]
sortby Allows you to use custom sort keys, the default is <code>location_municipality,weekday_tinyint,start_time</code>. 
Ex. [temporary_closures root_server="https://www.domain.org/main_server" sortby="weekday_tinyint,location_municipality,start_time"]
<h3>EXAMPLES</h3>
<a href="https://sca.charlestonna.org/temporary-closures-bmlt/" rel="nofollow ugc">https://sca.charlestonna.org/temporary-closures-bmlt/</a>
<h3>MORE INFORMATION</h3>
<a href="https://github.com/bmlt-enabled/temporary-closures-bmlt" rel="nofollow ugc">https://github.com/bmlt-enabled/temporary-closures-bmlt</a>

Temporary Closures BMLT

Temporary Closures BMLT is a plugin that displays a list of all meetings that have temporary closures. It can be used

Mayo Events Manager vs Temporary Closures BMLT