Description
Automaize Event Calendar lets you create and manage events directly in the WordPress admin and display them anywhere on your site using a simple shortcode.
Key features:
- Responsive tile grid (1–4 columns, auto-adjusts on mobile)
- Events sorted chronologically — next event first
- Past events hidden automatically
- Recurring events: weekly, monthly by date, monthly by weekday (e.g. first Monday), or individual custom dates
- Configurable visibility window (how many days into the future) and maximum event count
- Per-event button text, subtitle, and time display
- Optional WooCommerce product link per event for ticket sales or booking
- REST API for a companion mobile app (public event browsing, plus an API-key-protected staff surface to manage events)
- Theme-overridable templates
- Fully translatable (ready for translation via GlotPress on WordPress.org)
Shortcode usage:
[amzec_events]
Optional attributes:
count– maximum number of events to show (default: 12)future_days– show events up to N days in the future; 0 = unlimited (default: 0)columns– number of tile columns 1–4 (default: 3)category– comma-separated category slugs to filter
Example: [amzec_events count="6" columns="2" future_days="90"]
Installation
- Upload the
automaize-event-calendarfolder to/wp-content/plugins/. - Activate the plugin via Plugins › Installed Plugins.
- Go to Events › Einstellungen to configure defaults.
- Create events under Events › Neu hinzufügen.
- Add the shortcode
[amzec_events]to any page or post.
FAQ
How do I display events in a different number of columns?
Use the columns attribute: [amzec_events columns="2"]. On tablets the grid automatically reduces to 2 columns, and on mobile to 1 column.
Can I show only a specific category?
Yes: [amzec_events category="workshop,seminar"]
How does WooCommerce integration work?
When editing an event, enter the ID of an existing WooCommerce product in the sidebar. An add-to-cart button will appear on the single event page.
Can themes override the templates?
Yes. Copy templates/partials/event-tile.php to amzec-event-tile.php in your theme root to override the tile, or templates/single-amzec_event.php to single-amzec_event.php in your theme root to override the single event page.
Will deleting the plugin remove my events?
Yes — uninstalling (deleting) the plugin removes all event posts, taxonomy terms, and plugin settings. Deactivating alone does not remove any data.
Changelog
1.7.1
- Tweak: the in-app ticket purchase flow’s error/status messages and the related REST messages are now in German instead of English – the event page itself was already German, this was a leftover from the ticket-purchase feature.
1.7.0
- New:
product_urlon the public event ticket info – the direct WooCommerce product permalink, usable standalone (e.g. for a flyer QR code aimed straight at ticket purchase) alongside the existing inline purchase widget. - New: “Tisch für dieses Event reservieren” button on the event page, linking to the Restaurant Reservation plugin’s new reservation page pre-scoped to this event – shown unless the event has a currently purchasable ticket (buying one already creates the table reservation automatically). “Im Shop kaufen” link added next to the existing inline ticket widget, shown regardless of stock so a printed flyer QR code stays valid.
- Fix: the event page’s own “Reservierungen” nav link pointed at a dead anchor (
/index.html#reservieren, which has never existed on the website) – now points at the Restaurant Reservation plugin’s reservation page. Also added the missing “Shop” nav item, matching the website’s own navigation.
1.6.3
- New:
GET/PUT /amzec/v1/staff/settingsexposes “Anzahl Events” and “Sichtbarkeit in die Zukunft” (from Events > Einstellungen) to the app, so staff can change how many events show without a trip to wp-admin.
1.6.2
- Fix:
GET /amzec/v1/events(used by the website’s homepage) ignored the “Anzahl Events” setting under Events > Einstellungen when the caller didn’t pass its owncount– it silently fell back to a hardcoded 12 instead. It now falls back to the configured setting, same as the[amzec_events]shortcode already did.
1.6.1
- Tweak: the event tile image (
[amzec_events]grid) is now a 1:1 square instead of 16:9 – a bigger, more prominent image at typical tile widths.
1.6.0
- New: “Tischbuchung an diesem Tag freischalten” (see AMZEC_Table_Booker_Integration) is now readable and writable through the REST API (
tablebooker_enabledon the public/staff event responses andPOST/PUT /staff/events), so the mobile app can expose it directly in the event form instead of requiring a separate trip to wp-admin.
1.5.1
- Fix: the single event page no longer relies on get_header()/get_footer() (i.e. on whatever theme/page builder happens to be active) – it’s now fully self-contained, with its own header/footer matching the Kerstins static site’s own branding/nav/footer directly (same styles.css, same logo). Diagnosed after a page builder (Breakdance) started silently swallowing ALL front-end WordPress output site-wide (confirmed via blank raw feeds/sitemap too, not just event pages) with no PHP error logged – deactivating it was the fix, so no more dependency on it for event pages either.
- Admin: the “Tischbuchung an diesem Tag freischalten” checkbox now shows a warning when an event’s own time falls outside the regular opening hours (or on an otherwise-closed day) and the box isn’t ticked – leaving it unchecked silently limits bookings to the normal hours instead of the event’s actual time, which was reported as confusing guests.
1.5.0
- New:
GET /amzec/v1/today-menu– resolves what a guest should see as “today’s menu”: today’s event’s menu (if one has a menu PDF), otherwise the standard menu. The standard menu is simple structured data (title/intro/sections/items/footer, not a PDF), stored via the newPOST /amzec/v1/staff/standard-menuand maintained in parallel with the website’s à la carte page – meant for native, inline display in the app rather than a PDF viewer.
1.4.0
- New: in-app ticket purchase for paid events.
POST /amzec/v1/events/{id}/ticket-ordercreates a pending WooCommerce order (guest, for the event’s linked product) and returns WooCommerce’s own guest checkout URL;GET /amzec/v1/events/{id}/ticket-order/{order_id}?key=reports payment/reservation status. Once WooCommerce marks the order paid, a matching table reservation is created automatically in the Restaurant Reservation plugin (if active). The public/events//events/{id}responses now include aticketobject (price, currency, stock) when an event has a linked product. The admin “Ticket-Produkt” field is now a real product dropdown instead of a raw numeric ID.
1.3.1
- Event editing now uses the classic (non-block) editor instead of Gutenberg. Event descriptions are always plain text anyway (both from wp-admin and the app), so this buys nothing functionally but meaningfully lowers peak memory on the event edit screen – helpful on hosts with a tight PHP memory_limit.
1.3.0
- New: menu PDF per event. Upload a PDF in the “Speisekarte (PDF)” box on the event edit screen (or via
POST/DELETE /staff/events/{id}/menufrom the app); guests get a “Speisekarte ansehen” button on the event page that opens it in an overlay instead of navigating away. The public/eventsand/events/{id}responses now includemenu_pdf_url.
1.2.0
- Added
GET /staff/media: a paginated listing of existing image attachments in the WordPress media library, so the app can offer “choose an existing image” alongside “upload a new one” when setting an event’s featured image.POST /staff/events/{id}/imagenow also accepts amedia_idof an existing attachment as an alternative to a file upload.
1.1.0
- New: REST API for the Kerstins mobile companion app (public event browsing plus an API-key-protected staff surface to create, edit, delete events and upload a featured image — including full recurrence support)
1.0.5
- New: Optional integration with Automaize Restaurant Table Booker — freischaltbare Tischbuchung an einzelnen Event-Tagen, auch außerhalb der regulären Öffnungszeiten oder während Betriebsferien
1.0.4
- Fix: Event tiles now align vertically across columns (CSS subgrid)
- Fix: “Mehr erfahren” button now displays correctly on Breakdance pages
1.0.3
- Fix: Column layout now works correctly on Breakdance pages (inline style beats page-builder CSS)
1.0.2
- New: Per-event display limit for recurring events (“Max. Anzeigen im Kalender”)
- Fix: CSS grid now loads correctly on Breakdance-built pages
1.0.1
- Fix: German admin labels (meta box and settings page title)
1.0.0
- Initial release