Ever since the WordPress version 5.0 of WordPress, Gutenberg editor became the default editor of WordPress. Prior to this, WordPress used simplistic classic editor but based on the survey from 2017, it became apparent that WordPress users needed a paradigm shift in creating and editing content on their website. And while the introduction of Gutenberg as default WordPress content editor was met with the mixed feedback, primarily by developers, over the time both users and developers accepted it as a new standard and adapted to it.
How Tickera fits into this?
The same feeling was shared in Tickera camp, especially given that Tickera was heavily relying on its shortcode builder and all of its content was displayed using vast number of shortcodes many of which contained several arguments. But, back in the 2018 with Tickera update 3.9.2.9, we have introduced Tickera specific Gutenberg blocks that allowed users to display any Tickera related content. Essentially, these blocks were and still are a direct reflection of its shortcodes and serve the same purpose but instead of having long shortcodes in the content area, you were now able to simply add the block and set its attributes in tbe block editor.
What about events?
Users that are familiar with Tickera will know that creating events serves two purposes: functional and presentational. As functional purpose, events are basically a cornerstone in Tickera hierarchy and everything starts with creating an event. On the other side, there's a presentational part of the event as each event created in Tickera can be used as the event page where you can display to your customers any valuable information regarding the event. And while the functional part of events have evolved quite a bit over the years with many new features being introduced regularly, the presentational part remained pretty much the same, with the same, classic, content editor with the look and feel of the event pages being directly dependant on the styling of a theme currently active on user's website.
The modern WordPress user wants more and doesn't like the idea of being locked to one layout for their events.
Of course, there are ways to affect this by creating custom event page templates but this requires solid familiarity with the inner workings of WordPress and some developer skills. Alternatively, there is possibility to use Elementor plugin to create event page templates as we have discussed here. However, as the number of users relying on WordPress' own Gutenberg editor grew constantly and Gutenberg itself became quite a mature content editing tool, we couldn't ignore its existence anymore which is why we have now officially introduced Gutenberg as official editor of Tickera events.
The old/new way of handling event pages
In the 3.5.1.2 update of Tickera, the content of the event pages is now handled by Gutenberg editor. It works the same way as Gutenberg works on any other page or post: click a plus icon to add a block, select a block to add to the content, modify it the way you see fit and that's it. And, if you want to know more about using Gutenberg editor, we suggest you check their documentation here. However, at the same time, we have preserved all the options important for the functional part of the event such as start date/time, event location, event logo, etc. and this information is also conveniently presented each as a separate Gutenberg block so that you can use it on the event page or anywhere else on your website. Also, the option Show tickets automatically which, if checked, displays a table with all the tickets associated to that event, is still present.
I don't quite like this and I want things like they used to be
Of course, we completely understand that Gutenberg is not everyone's cup of tea which is completely legitimate. There are quite a few Tickera users deeply set in the old ways and don't want any changes in the way they create and edit events. If you find yourself in this side of the spectrum, you can still get the old, classic way of creating and editing events by using Classic Editor plugin. If you install it and set as default WordPress editor, everything will work just the way you're used to. However, there are some "hybrid" users who like the idea of using Gutenberg as editor for their regular pages and posts but want to use classic editor for Tickera events. This is also completely legitimate and easily doable. When Classic Editor plugin is installed, you can navigate to its settings and find option Allow users to switch editors and set it to Yes. In this case, you will be able to select which editor you want to use for each and every post or page which also includes Tickera's event pages.
When this option is enabled, you will find an extra meta box on the right when creating new or editing existing event, that will make it possible to select which editor you will be using. So, if you're currently using Classic Editor but want to switch to Gutenberg, then the option will be on the right as shown on the screenshot below:
However, if you're currently using Gutenberg and want to switch to the Classic Editor, you should first click the three dots in the upper right corner and then select the option Switch to classic editor:
