For anyone developing in the WordPress space, you should be well aware by now that WordPress 5.0 is bringing with it some pretty significant changes. Here at Event Espresso, we’ve been working hard to keep up with those changes and prepare our products for the future brought with those changes. In this post, I want to give a bit of an overview of what those changes mean for Event Espresso and how that might affect you as a developer working with our products.
In the short term, it’s important to highlight that nothing specific needs to be done for any Event Espresso customizations:
- Currently, our editors are unaffected by the new WordPress editor. So any customizations in them (meta boxes, etc) will continue to work after the launch of WordPress 5.0
- All our shortcodes continue to work in both the classic and new editor. The new editor has a shortcode block that can be used with shortcodes. One distinction, however, is that shortcodes exist on their own block. In most cases, that shouldn’t affect Event Espresso shortcode users too much because EE shortcodes tended to be their own distinct content pieces anyways.
So, in the short term at least, you can have a moment of relief! However, we do think there are some things you should be planning for and accounting for in the future.
What does this mean for Event Espresso?
Extensibility (including shortcodes vs blocks )
An example where this will be happening in the short term is the introduction of Blocks in the new editor (vs. WordPress shortcodes). One of the significant features of the new WordPress editor is the introduction of the concept of Blocks. We’re “all-in” with this new feature which means:
- We will no longer be adding new features to any of our current shortcodes. We’ll still do any bug fixes that may be needed, but none of our shortcodes (or their related templates) will have additional feature development.
- We will keep existing shortcodes in our products for as long as WordPress supports them.
- We are not introducing 1:1 parity with our existing shortcodes when introducing new blocks with similar functionality. Blocks (such as the Event Attendees block) will exist entirely on their own and the layout, styling etc is not inherited from the equivalent shortcode.
Going forward, we’re iterating on and developing blocks for the new editor because we believe the user interface and experience is much greater than that of the WordPress shortcodes.
Practically, this means for you, the WordPress developer:
- If you are already using the extensibility in existing templates for the current shortcodes, you can continue to do so going forward (especially since the new editor does support WordPress shortcodes).
- With that said, we do have a PHP framework built for more easily registering new blocks PHP side (more on that in the documentation section).
As always, documentation is an ongoing effort and we appreciate any feedback you have to where we can improve.
In the coming year we currently have planned (among other things):
- Recurring Events Manager — an add-on which allows for easily managing recurring events which are predominately written in react.
- Releasing more blocks for the new editor.
- Beginning the work on refactoring our own editors to work similarly to the new WordPress editor except they’ll be more Event centric (vs. post-centric).