

The native Events overview with event dates, location, categories and status filters.
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.
[wpse_events], [wpse_calendar], [wpse_event_details] and [wpse_add_to_calendar].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.
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.
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.