• Alexandre Buffet

    (@alexandrebuffet)


    It had been years since I last used this plugin, so I decided to give it another try. I was genuinely hoping things had improved, but I came away quite disappointed.

    As a WordPress developer, I found the latest version unnecessarily complex and frustrating to work with. Simply activating it produced numerous PHP warnings in my development environment, which immediately raised concerns about code quality and attention to WordPress best practices.

    The biggest disappointment, however, is the Block Editor integration. Astonishingly, it’s not even enabled by default, you first have to find and enable an option to use it. In 2026, that’s hard to understand!

    Unfortunately, enabling it doesn’t improve the experience much. It doesn’t feel like a native WordPress experience at all. Event metadata is tightly coupled to the plugin’s blocks, so if you remove those blocks from a Single Event template, you also lose the ability to properly edit the event’s metadata. Rather than integrating with the Block Editor, the plugin forces you into its own awful editing model.

    The blocks themselves don’t behave like native, composable WordPress blocks. Their UI feels inconsistent with the rest of the editor, the icons are oversized and visually out of place, and the overall editing experience feels clunky rather than seamless.

    Overall, this plugin feels more like a large legacy framework layered on top of WordPress than a plugin that embraces Gutenberg conventions and philosophy. It offers many features, but at the cost of simplicity, consistency, and developer experience.

    I can’t recommend this plugin in its current state. I hope the team behind it takes this feedback seriously and rethinks its approach to WordPress integration.

Viewing 1 replies (of 1 total)
  • Plugin Support Darian

    (@d0153)

    Hi @alexandrebuffet

    Thank you for taking the time to share such detailed feedback. We truly appreciate you giving The Events Calendar another try after several years, and I’m sorry to hear that your experience didn’t meet your expectations.

    We understand your concerns regarding the PHP warnings, the Block Editor experience, and the overall developer workflow. Feedback like yours is valuable, especially from developers who work closely with WordPress and Gutenberg.

    Regarding the PHP warnings, those aren’t something we expect under a supported environment. In some cases, we’ve found that they can be caused by PHP version compatibility, custom code that inadvertently affects our plugin. Likewise, some Block Editor display issues can stem from themes or plugins that apply CSS globally, resulting in an editing experience that differs from what we intended.

    That said, we recognize that there is always room for improvement in how our plugin integrates with the WordPress editor, and we appreciate your candid comments about the current experience.

    If you’re still open to it, we’d be happy to investigate the specific issues you encountered. Please feel free to reach out to our Support Team and include details about your environment, such as your WordPress version, PHP version, active theme, and any relevant plugins.

    With that information, we’ll be able to determine whether the behavior is caused by an environmental conflict—such as a theme or plugin—or whether you’ve uncovered an issue on our side that we should address.

    Thank you again for your thoughtful feedback. We genuinely appreciate it, and we’ll be sure to share it with our product team as they continue improving the plugin and its WordPress integration.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this review.