Posted: May 1, 2020 at 5:09 pm
This is a fork of the last pre-Gutenberg WordPress.
For those of us who loathe Gutenberg, it’s very tempting, especially for a pure booking system website that doesn’t need the the bloat and the series of security issues Gutenberg has brought.
They want to be compatible with WP 4.9x plugins, but is there anything they could do that would accidentally make EE4 not work on it?
From the other side, are you planning to have something that relies on editor blocks existing in future?
While I’ve not used ClassicPress or loaded it onto a site to try it, I would imagine the current version of EE4 would work, because EE4 currently doesn’t require WordPress 5.x.
EE4 currently does not offer many new features that are WordPress 5.x only. The one feature that’s been added is the Attendee block that can be used instead of the Attendee shortcode. This is subject to change because we are working on new features that will require React and GraphQL (not the same as Gutenberg). These newer technologies will only work with WordPress 5+. So moving forward, the new features being developed for Event Espresso 4 like the new ticket/datetime editor, questions per ticket, recurring events, and new blocks we plan on adding will all require WordPress 5+.