Сүрөттөө

MiMe Simple Events and Calendar adds a native Events section to WordPress. It is designed for websites that need clear one-off and recurring event publishing without ticketing, interactive maps, visitor tracking or the overhead of a large event suite.

Create the event once, then show it through the native archive, a list or grid, a responsive calendar, Gutenberg, Elementor, Divi 5 or a shortcode. The plugin follows the website’s WordPress timezone and formatting settings and inherits theme typography and colors by default.

Event publishing

Create events in the familiar WordPress editor.
Add a start, optional end, all-day state, venue, address and external links.
Use separate event categories and tags without mixing them with blog posts.
Mark events as scheduled, postponed or cancelled independently of their WordPress publication status.
Keep each event’s original timezone when the website timezone changes.
Use WordPress revisions and a safe Duplicate event action.

Recurring events

Repeat events daily, on selected weekdays, monthly, yearly or on selected dates.
End a repeating schedule on a date, after a fixed number of occurrences, or keep it open-ended within the plugin’s safe projection window.
Review the exact impact before applying changes to the complete series or this and following occurrences.
Edit, move, postpone, cancel or restore only one occurrence without duplicating the complete event.
Convert a repeating series back to one deliberately selected event through a separate confirmation step.
Keep open-ended schedules lightweight through a bounded rolling public window that renews automatically.

Display options

Native single-event and event-archive pages for classic and block themes.
Responsive event list and grid with bounded card controls, modern optional category/tag filters and pagination.
Semantic checkbox filters with removable active choices, clear/restore actions, shareable URLs and a complete no-JavaScript fallback.
Month and list calendar views with optional category colors, event color choices, an accessible legend, an initial date and configurable toolbar groups.
An accessible upcoming-event fallback when JavaScript is unavailable or the calendar cannot load.
Three complete Gutenberg components, twelve dynamic individual event-field blocks, one Add to Calendar block and a single-event pattern.
Four complete shortcodes: [wpse_events], [wpse_calendar], [wpse_event_details] and [wpse_add_to_calendar].
One-way local ICS download with optional Google and Outlook compose actions.
Event JSON-LD on eligible single-event pages, with an administrator opt-out.

Optional Elementor integration

Elementor 3.35 or newer adds Event List / Grid, Event Calendar, configurable Event Details and Add to Calendar widgets, together with twelve individual event-field widgets. Elementor is optional: the event editor, shortcodes, Gutenberg blocks and native templates work without it.

Individual widgets can select a published event on an ordinary Elementor page. In a dynamic event template they can use the current event context. Elementor Pro is only required when the site owner wants to use Elementor’s Theme Builder; it is not required by this plugin.

Optional Divi 5 integration

Divi 5.11.1 or newer adds the same three complete components, twelve individual event-field modules and an Add to Calendar module. They work on ordinary Divi pages with an explicitly selected public event and in Divi Theme Builder templates with the current event or exact recurring occurrence.

The integration uses Divi’s native content, design, responsive and global-preset systems. Divi remains optional and no Divi theme code, licence data or updater credentials are included in this plugin.

Privacy by design

The plugin does not create visitor cookies, collect analytics or telemetry, load remote scripts, or send information to MiMe or another external service. Calendar requests stay on the same WordPress website.

Event content entered by site editors—including dates, venues, addresses and links—is stored in the website’s own WordPress database. Published event information can be visible in page HTML, Event JSON-LD, the WordPress REST API and the plugin’s bounded calendar feed. Do not publish private information as event content. Draft, private and password-protected event details are excluded from public plugin collections; protected event metadata is also removed from public core REST responses while the WordPress password is still required.

Recurring schedules remain canonical protected WordPress metadata. A local rebuildable occurrence index stores only the bounded dates, status, stable identity and parent event relationship needed for chronological queries. It contains no event body, password, taxonomy copy, visitor data or remote identifier.

External location and event links are contacted only when a visitor chooses them. They open in an isolated new tab without passing a referrer. The destination website has its own privacy practices.

Deactivation never deletes event data. Plugin deletion also preserves events and settings by default. An administrator can explicitly opt into permanent cleanup under Events > Settings; shared media remains untouched.

The complete source, build instructions and security policy are available at https://github.com/MilanMiMeOnline/WP-Simple-Events.

New users can follow the task-based guide at https://github.com/MilanMiMeOnline/WP-Simple-Events/blob/main/docs/USER-GUIDE.md.

Скриншоттор

The native Events overview with event dates, location, categories and status filters.

The Event details panel in the familiar WordPress editor. — The native Events overview with event dates, location, categories and status filters.

Блоктор

This plugin provides 16 blocks.

Event Location Link Display the route or location link saved on an event.
Event Address Display the postal address of the current or selected event.
Event Details Display the complete details of the current or selected public event.
Event Status Display a cancelled or postponed event status.
External Event Action Display the external information or registration link saved on an event.
Add to Calendar Offer a calendar file and optional Google or Outlook actions for one event.
Event Categories Display linked categories for the current or selected event.
Event List / Grid Display a bounded list or grid of public events.
Event Content Display the main content of the current or selected event.
Event Title Display the title of the current or selected event.
Event Excerpt Display the excerpt of the current or selected event.
Event Venue Display the venue of the current or selected event.
Event Tags Display linked tags for the current or selected event.
Event Date & Time Display the localized date, time and optional timezone of an event.
Event Featured Image Display the featured image of the current or selected event.
Event Calendar Display the interactive public event calendar with a server-rendered fallback.

Орнотуу

Install the plugin from Plugins > Add New, or upload an official release zip through Plugins > Add New > Upload Plugin.
Activate the plugin.
Check the website timezone, date format and time format under Settings > General.
Go to Events > Add New, enter a valid start and publish the first event.
Add the Event Calendar or Event List / Grid block to a page. You can instead use [wpse_calendar], [wpse_events], Elementor or Divi 5.
Preview the event and events page as a logged-out visitor, including on a narrow screen.

The native archive is available at /events/ by default. The complete first-event guide is at https://github.com/MilanMiMeOnline/WP-Simple-Events/blob/main/docs/GETTING-STARTED.md.

FAQ.KG

How do recurring-event edits work?: Save the event with valid dates first. Choose the intended scope before changing it: Edit one occurrence, This and following, or Complete series. Broad changes show an impact preview before they can be applied. Individual occurrence changes remain sparse and reversible, so choosing Use series value restores inheritance instead of copying content.
Where should I start if I am new to the plugin?: Use the Getting started guide to check timezone settings, publish the first event and create an events page: https://github.com/MilanMiMeOnline/WP-Simple-Events/blob/main/docs/GETTING-STARTED.md. The user guide then links recurrence, display, builder, troubleshooting, privacy and update tasks.
Does it include maps, geocoding or ticket sales?: No. You can store an address and an HTTP or HTTPS location link, but the plugin does not load an interactive map, call a geocoding service or sell tickets.
Is Elementor required?: No. Elementor is an optional integration. Native templates, Gutenberg blocks and shortcodes provide the complete core experience.
Can Elementor Free use the event widgets?: Yes. The widgets can be placed on ordinary Elementor Free pages and can select a published event. Elementor Pro is only needed for Elementor’s own Theme Builder functionality.
Does it work with Divi 5?: Yes. Divi 5.11.1 or newer provides sixteen native MiMe event modules, including Event List / Grid, Event Calendar, Event Details, Add to Calendar and twelve individual event fields. Divi Theme Builder is part of Divi itself; the plugin never creates or changes Theme Builder assignments automatically.
How does Add to Calendar affect privacy?: The default ICS download is generated by your own WordPress website. Google and Outlook are optional template-author choices; the plugin does not contact them. When a visitor follows one of those links, the public event snapshot is sent to that provider in an isolated new tab. Imported events are snapshots and do not synchronize with later website changes.
Which timezone and time format are used?: New events capture the timezone configured under WordPress Settings > General. Existing events keep their saved timezone if that website setting changes. Public times follow the WordPress time-format setting. Events > Settings can optionally show the captured timezone and applicable UTC offset.
Can I color event categories or individual events?: Yes. An event category can have one optional color. An event can use its own color, an explicitly chosen assigned category, an unambiguous assigned category automatically, or the component’s existing fallback. If several assigned categories have different colors, the plugin never chooses one by incidental term order. Text, times, statuses and category names remain visible so color is not the only source of meaning.
How do I remove or reset visitor filters?: Visitors can remove an active category or tag choice individually, use Clear all, or use Restore defaults when the component has configured initial choices. Each list or calendar keeps its own shareable filter state and still works as a normal form without JavaScript.
Why is the header or footer missing on an event page?: The native plugin fallback retains the active theme header and footer. Check whether an Elementor or Divi Theme Builder condition or a theme event-template override deliberately replaces it. The builder guide includes a focused checklist: https://github.com/MilanMiMeOnline/WP-Simple-Events/blob/main/docs/BUILDERS-AND-TEMPLATES.md.
What happens to data when the plugin is removed?: Nothing is deleted on deactivation. Deleting the plugin also keeps events, event categories, event tags and settings unless an administrator first enables the clearly warned Delete plugin data option. Uploaded media is never deleted by that cleanup.
Does the plugin track visitors or contact external services?: No. There is no telemetry, analytics, advertising, remote asset loading or MiMe service connection. The calendar reads its public data from the same WordPress installation. A visitor can still choose an external location or event link, after which the destination’s own policies apply.
Where can I report a bug or security issue?: Ordinary bugs can be reported at https://github.com/MilanMiMeOnline/WP-Simple-Events/issues. Do not publish vulnerability details, secrets or personal data in an issue; follow the private process in the repository’s SECURITY.md file.

Сын-пикирлер

There are no reviews for this plugin.

Contributors & Developers

“MiMe Simple Events and Calendar” is open source software. The following people have contributed to this plugin.

mimeonline

Translate “MiMe Simple Events and Calendar” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Өзгөртүүлөр

0.9.0

Freeze the documented public shortcodes, blocks, REST routes, metadata, occurrence identities and builder component contracts for the future 1.x line.
Make recurring-event collections substantially more efficient by priming event, metadata and taxonomy data once per bounded result set.
Strengthen clean-install, historical-upgrade, derived-data repair, deactivation and both uninstall-retention paths.
Improve keyboard, focus, text-spacing, forced-colors and 320-pixel reflow behaviour across visitor filters, calendars, pagination and recurrence controls.
Keep repeated event collections accessible with unique heading references and prevent mobile calendar-list tables from causing horizontal page overflow.
Add a complete task-based guide for first events, recurrence scopes, filters and colors, Gutenberg, Elementor, Divi 5, privacy, ownership and troubleshooting.
Re-audit permissions, REST and calendar exports, dependencies, privacy boundaries and release packaging without adding telemetry, cookies or remote runtime services.

0.7.0

Add an optional local ICS download for one public one-off event or one exact recurring occurrence.
Add opt-in Google Calendar and Outlook compose actions with isolated external links and clear snapshot semantics.
Add an atomic Add to Calendar shortcode, Gutenberg block, Elementor widget and native Divi 5 module over one shared renderer.
Add an off-by-default native single-event action that never overrides Elementor or Divi Theme Builder ownership.
Preserve captured timezones, exclusive all-day ends, stable occurrence identities and RFC 5545 text escaping and folding.
Keep exports public-only and fail closed for drafts, private, password-protected, cancelled, stale or ambiguous event contexts.
Return local calendar files through a same-origin no-store endpoint without visitor cookies, remote assets or background provider requests.

0.6.0

Replace modifier-key multiple selects with semantic category/tag checkboxes, removable choices and clear or restore-default actions.
Add component-responsive filter disclosures, bounded option search, shareable isolated state and complete no-JavaScript operation.
Add optional category and deterministic event colors with accessible text contrast, filter swatches and an Auto/Show/Hide calendar legend.
Show resolved colors as compact dots beside ordinary timed month events while keeping all-day and spanning events as readable solid blocks.
Add shared filter content and design controls across Gutenberg, Elementor and Divi while preserving existing saved defaults and shortcode output.
Fix event taxonomy archive headings that could expose WordPress’ decorative span markup as visible text.
Keep queries bounded, color metadata cache-primed and existing events visually unchanged until a new color or presentation setting is chosen.

0.5.1

Make open-ended recurrence previews explain their rolling public projection and hide rule-only end controls for one-off and selected-date schedules.
Add a concise recurrence summary to the native Events overview and clearer source, taxonomy and typography labels in Elementor.
Label timed multi-day calendar-list segments as starting, continuing or ending while preserving all-day wording.
Add bounded previous-date, next-date and canonical-series navigation to native exact-occurrence pages.
Keep calendar feed requests on the active site origin so equivalent host aliases and reverse proxies cannot cause false cross-origin failures.

0.5.0

Add fifteen native Divi 5 modules with ordinary-page, Theme Builder, responsive-device and global-preset support.
Resolve the current one-off event or exact recurring occurrence in Divi Theme Builder while keeping explicit selections public and password-free.
Add a bounded authenticated Divi composite-preview endpoint with exact document capabilities and generic fail-closed empty states.
Keep mounted calendars synchronized with Divi device-preview breakpoint changes and namespace dynamic preview IDs per module instance.
Harden permanent recurring-event deletion against projection races and repair bounded orphan occurrence rows.
Preserve plugin operation when Divi is absent, inactive or unsupported, and exclude all licensed Divi code and credentials from the release.

0.4.0

Add bounded recurring events for daily, weekly, monthly, yearly and selected-date schedules.
Add explicit Complete series, Only this occurrence and This and following edit scopes with review-before-apply confirmations.
Add reversible cancellations and sparse per-occurrence date, status, title, image, venue and action overrides.
Make lists, calendars, feeds, archives, Gutenberg blocks, Elementor widgets, REST, canonical URLs and Event JSON-LD occurrence-aware.
Add fail-closed occurrence indexing, health checks, bounded repair and renewal, Core sitemap discovery and conservative no-store leaf caching.
Preserve one-off event behaviour, established public component identifiers and theme/Elementor template ownership.

0.3.0

Add native Event List / Grid, Event Calendar and complete Event Details blocks for Gutenberg.
Add practical, opt-in presentation controls across Elementor, Gutenberg and shared public components.
Make event category and tag archives use event chronology while preserving the active theme shell.
Improve Elementor calendar previews, visitor filter reset behaviour, responsive grids and accessible component semantics.
Preserve existing event data, shortcodes, block names, Elementor widget identifiers and visual defaults.

0.2.5

Support PHP 8.2 while continuing to support PHP 8.3, 8.4 and 8.5.
Test the complete PHP quality suite and packaged WordPress compatibility journeys against the new minimum.
Refresh development dependencies to patched releases; these tools are not shipped with the plugin.

0.2.4

Preserve the active theme or Elementor header and footer on event archives and individual events in classic themes that also contain theme.json.
Keep full block-theme templates and explicit PHP or block-template overrides working through a tested template hierarchy.
Add a real WordPress compatibility matrix covering classic, hybrid and full block themes plus both override mechanisms.

0.2.3

Rename the pre-approval public identity to MiMe Simple Events and Calendar with the mime-simple-events-calendar slug.
Preserve existing event data, shortcodes, Gutenberg blocks and Elementor widget identifiers across the rename.
Update the WordPress.org banners, translations, release package and development dependencies.

0.2.2

Protect password-locked event metadata in the public WordPress REST API while preserving authorized editor access.
Add professional WordPress.org documentation, privacy guidance, icons, banners and product screenshots.
Pin continuous-integration actions to reviewed immutable revisions.

0.2.1

Establish the initial pre-approval distribution identity while preserving all event storage and content identifiers.
Open location and external event actions safely in a new tab.
Expose Edit with Elementor for individual Events on compatible Elementor installations.

Сүрөттөө

Event publishing

Recurring events

Display options

Optional Elementor integration

Optional Divi 5 integration

Privacy by design

Скриншоттор

Блоктор

Орнотуу

FAQ.KG

How do recurring-event edits work?

Where should I start if I am new to the plugin?

Does it include maps, geocoding or ticket sales?

Is Elementor required?

Can Elementor Free use the event widgets?

Does it work with Divi 5?

How does Add to Calendar affect privacy?

Which timezone and time format are used?

Can I color event categories or individual events?

How do I remove or reset visitor filters?

Why is the header or footer missing on an event page?

What happens to data when the plugin is removed?

Does the plugin track visitors or contact external services?

Where can I report a bug or security issue?