Ticketing is where event plugins accumulate their worst problems

Look at the support forums for the ticketing add-ons in this category and the pattern is consistent: payment gateway setups that end in a 404, security advisories, orders that do not reconcile, and refund flows that need manual intervention. Ticketing is a payments product wearing a calendar's clothes, and payments products are hard in ways that calendars are not.

None of that is an argument against ticketing plugins in general. It is an argument against installing one when you do not need it — because the code ships whether you use it or not, and so do its vulnerabilities.

What you get by leaving it out

A calendar without commerce has no cart, no session handling, no order tables, no payment credentials stored in your database, and nothing running on your checkout page. It does not need to hook into WooCommerce. It has fewer database tables — this one has none at all in the free version — and a much smaller surface for something to go wrong on.

It also loads less. The heavyweight plugins in this category ship a bundled HTTP client, a logger, a date library and a large chunk of a PHP framework, largely to support the commerce side. A calendar that only shows dates needs none of it.

What to do if you do sell tickets

Sell them where you already sell them. Most venues and studios already have a ticketing platform, a booking system or a box office, and those systems are better at it than any WordPress plugin. Put the link on the event. A “Book tickets” button pointing at the system that actually holds your inventory is more reliable than a second inventory inside WordPress that has to be kept in step with the first.

Better still: many of those systems publish an .ics feed of what is on sale. Point the calendar at that feed and your website schedule follows your box office automatically, without either system pretending to be the other.

Deliberately out of scope here

This plugin does not sell tickets, take bookings, hold a cart or touch payments, and it will not in a future version either. That is a scope decision rather than a roadmap gap. It shows dates, correctly, and links to wherever you handle the money.