MiMe Simple Events and Calendar

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

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

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.

com/MilanMiMeOnline/WP-Simple-Events.

md.