Uncaught (in promise) Error

Hi @polyfade,

Sorry to hear you’re having that problem.

Can you please clarify in which page you’re seeing that error? Is it when editing an event with the block editor?

Have you ever used (or currently using) the classic editor plugin by any chance?

Thanks,
Victor

When I try to create a new event, I get the error.

BTW, I deleted all of my pre-existing events and venues.

I’m using Gutenberg instead of the classic editor, and have the checkbox ticked in the Events Calendar settings to “Enable the Gutenberg block editor interface for creating events”

I disabled, “Enable WordPress Custom Fields on events in the classic editor.” However, I never used custom fields.

Under Display tab settings, I am using the Default Events Template with Tribe Event styles. Although, I tried with Skeleton styles too.

I have “Enable updated designs for all calendar views” enabled.

If I revert back to classic and all classic-related settings, I don’t have the issue.

Using WP 5.8 and The Events Calendar 5.8.1. Although, I discovered the issue in WP 5.7.2

• This reply was modified 3 years, 7 months ago by polyfade.

Hi!

Thanks for clarifying that.

I think the problem you’re having could be due to an existing conflict with our plugin and the Classic Editor plugin.

Is it possible that you are using that plugin or ever used it before? We found out that the conflict occurs even if you used the plugin in the past and then deactivated/deleted it.

Can you confirm this is the case for you?

Victor, Yes I have used the Classic Editor in the past.
Even though I removed all events that were once created by the classic editor, the issue persists.

Any way around that?

Hi @polyfade,

Thanks for confirming that.

We found a workaround you can try. While logged in as an admin, navigate to yoursite.com/wp-admin/options.php

You should be able to see an option called classic-editor-replace that was added by the classic editor plugin. That option is likely set to either ‘replace’ or ‘classic’. Try changing that to block and save the changes.

You should be careful not to change any of the other option as it can create breaking changes. We recommend that you perform a full backup of your site before doing any changes to /wp-admin/options.php

That said, I will link this thread to our internal report so we can let you know here when we release a permanent fix for this issue.

Best,
Victor

Internal Ref: TEC-4016

Thanks a bunch Victor. That fixed it.

Here’s that change as a wp-cli command:

wp option set classic-editor-replace block

I encountered this bug on a system where Classic Editor had been installed at one point in time, but was no longer active or installed. Its option values were still present in the DB.

It would be nice if TEC provided a notice next to the setting Dashboard > Events > Settings > General > General Settings > “Activate Block Editor for Events” if there appears to be a setting in another plugin which TEC is interpreting to override that checkbox.