Disabled block editor on updating to 6.0.x

I got the very same problem since 6.0.1… Impossible to restore the block version.

Fixed by reverting the events migration + downgrading to 6.0.0.1 + migrate events again…

Hi @glycymeris,

Sorry to hear about that problem.

Can you tell us a bit more about the problem? Do you see any errors in the browser console when trying to edit an event with the block editor? In case you wonder how to see that, here’s a handy guide about it: https://theeventscalendar.com/knowledgebase/k/using-google-chrome-developer-tools/

Also, try enabling the debug mode on your site and let us know of any errors you see when the problem happens: https://theeventscalendar.com/knowledgebase/k/how-to-enable-debugging-in-wordpress/

Did you try the workaround mentioned by @ornanovitch? One thing you can try is reverting the migration and then deactivating all other plugins before running the migration again, just to make sure there are no conflicts happening during the migration.

Hope that helps

FYI, I ran the migration again after downgrading to 6.0.0.1, but I’m stuck with this version for now, because last time I tried to upgrade to 6.0.1 again, the bug reappeared.

And no error on my side (neither in the console, nor with WP debug)

• This reply was modified 2 years, 1 month ago by ornanovitch.

Hi @ornanovitch, sorry to hear about this. We’re still trying to identify any errors and we were not able to replicate the issue here with v6.0.1.

I suspect there’s a conflict that’s causing the issue here. Could you try deactivating all other plugins except for our plugins to see if that makes a difference? Moreover, could you switch to the default theme? Please read the Testing for Conflicts Article before doing anything. We’d recommend conducting these tests on a Staging Server. I’d suggest debugging it on a staging site and please do let us know about the findings.

Fo now I’d not recommend upgrading your main site to v6.0.1.

Let me know how it goes.

Best,
Abz

Same problem here. Just to share it is more widely spread.

First not able to even run the preview for running on php v8.1.x, next on php 7.4.x being able to migrate, not getting the block editor anymore. So undo the migration and going back to tec v6.0.1 and again migrating, and it seems to work, until upgrading the plugin again and no longer getting the block editor.

It makes me not trust the current version and I reset the system to an earlier state for now. For now I returned to an earlier version without the migration, so I both have the block editor and the tickets are shown properly again.

In php 8.1 I saw some fatals about the logging and DateTime receiving a null argument, what is deprecated.

That’s probably due to version 1.x of the monolog dependency, instead of version 2 or 3. Using dependencies that are not meant for php8, can been seen as a problematic choice. So why keep using them?

php 8 still also causes lots of deprecated log entries, by both WP and all kinds of mainstream and premium plugins, so that’s a shame, since using current php versions should be the preferred way.

In php 7.4 I didn’t see concrete clues in the error logs, but haven’t checked the console.log, so perhaps that would have given some info. It’s to complex for me.

For now I wait on a more stable and (production) tested version. To many moving parts to quickly problem solve this breaking upgrade. Hope someone more experienced will figure it out.

Hi @hanswitteprins, I’m really sorry, first of all, that our release with 6.0.x didn’t go smoothly for everyone, especially with the migration. We’ve introduced new features, compatibility with PHP8 and WP6, and retired a couple of functions all together in the v6 that might have caused various user issues. At the moment, we’re focusing our development resources on fixing these known issues and our goal is to make the v6 stable for everyone.

That being said, you could also test out the latest releases on a Staging Server. Please keep using the current working version for now and disable the auto-updates.

Again, thank you for your patience. Hang in there.

Best,
Abz

Hola, @abzlevelup:

The problems continues for me with the 6.0.4. version. I have instaled PHP 7.4.33 and everything is updated.

I can’t understand why I have everything with classic editor and the designs of events are broken.

Thanks

Hi again,

I leave a report of my site, in case it can hep you.

### wp-core ###

version: 6.1.1
site_language: es_ES
user_language: es_ES
timezone: Europe/Madrid
permalink: /%category%/%postname%/
https_status: true
multisite: false
user_registration: 0
blog_public: 1
default_comment_status: open
environment_type: production
user_count: 4
dotorg_communication: true

### wp-dropins (3) ###

advanced-cache.php: true
maintenance.php: true
object-cache.php: true

### wp-parent-theme ###

name: GeneratePress (generatepress)
version: 3.2.2
author: Tom Usborne
author_website: https://tomusborne.com
/generatepress
auto_update: Desactivado

### wp-mu-plugins (1) ###

Health Check Troubleshooting Mode: author: (undefined), version: 1.8.0

### wp-plugins-active (43) ###

AccessPress Social Icons: version: 1.8.5, author: AccessPress Themes, Actualizaciones automáticas desactivadas
Antispam Bee: version: 2.11.1, author: pluginkollektiv, Actualizaciones automáticas desactivadas
Banhammer: version: 3.1, author: Jeff Starr, Actualizaciones automáticas desactivadas
BBQ Pro: version: 3.5.1, author: Jeff Starr, Actualizaciones automáticas desactivadas
Block List Updater: version: 1.0.0, author: pluginkollektiv, Actualizaciones automáticas desactivadas
Bulk remove posts from category: version: 3.3, author: MasterNs, Actualizaciones automáticas desactivadas
Conditional Blocks: version: 3.0.1, author: Conditional Blocks, Actualizaciones automáticas desactivadas
Contact Form 7: version: 5.6.4, author: Takayuki Miyoshi, Actualizaciones automáticas desactivadas
Cool Timeline: version: 2.4.5, author: Cool Plugins, Actualizaciones automáticas desactivadas
Duplicator Pro: version: 4.5.4, author: Snap Creek, Actualizaciones automáticas desactivadas
Easy Forms for Mailchimp: version: 6.8.6, author: YIKES, Inc., Actualizaciones automáticas desactivadas
EditorsKit: version: 1.34.2, author: Munir Kamal, Actualizaciones automáticas desactivadas
Events Shortcodes For The Events Calendar: version: 2.2.4, author: Cool Plugins, Actualizaciones automáticas desactivadas
GDPR Cookie Compliance: version: 4.9.4, author: Moove Agency, Actualizaciones automáticas desactivadas
GenerateBlocks: version: 1.6.0, author: Tom Usborne, Actualizaciones automáticas desactivadas
GenerateBlocks Pro: version: 1.4.0, author: Tom Usborne, Actualizaciones automáticas desactivadas
Genesis Blocks: version: 1.5.3, author: StudioPress, Actualizaciones automáticas desactivadas
GP Premium: version: 2.2.1, author: Tom Usborne, Actualizaciones automáticas desactivadas
GTM4WP: version: 1.16.1, author: Thomas Geiger, Actualizaciones automáticas desactivadas
Gutentor - Gutenberg Blocks - Page Builder for Gutenberg Editor: version: 3.2.4, author: Gutentor, Actualizaciones automáticas desactivadas
Health Check & Troubleshooting: version: 1.5.1, author: The www.ads-software.com community, Actualizaciones automáticas desactivadas
Joinchat: version: 4.5.11, author: Creame, Actualizaciones automáticas desactivadas
Joinchat Support Agents: version: 3.7.3, author: Creame, Actualizaciones automáticas desactivadas
Login LockDown: version: 1.83, author: WebFactory Ltd, Actualizaciones automáticas desactivadas
LoginPress - Customizing the WordPress Login Screen.: version: 1.6.3, author: WPBrigade, Actualizaciones automáticas desactivadas
MainWP Child: version: 4.2.6, author: MainWP, Actualizaciones automáticas desactivadas
MainWP Child Reports: version: 2.0.8, author: MainWP, Actualizaciones automáticas desactivadas
Redirection: version: 5.3.5, author: John Godley, Actualizaciones automáticas desactivadas
Redis Object Cache: version: 2.2.2, author: Till Krüss, Actualizaciones automáticas desactivadas
Salt Shaker: version: 1.3.2, author: Nagdy, Actualizaciones automáticas desactivadas
Stream: version: 3.9.1, author: XWP, Actualizaciones automáticas desactivadas
The Events Calendar: version: 6.0.4, author: The Events Calendar, Actualizaciones automáticas desactivadas
The SEO Framework: version: 4.2.7.1, author: The SEO Framework Team, Actualizaciones automáticas desactivadas
The SEO Framework - Extension Manager: version: 2.6.0, author: The SEO Framework Team, Actualizaciones automáticas desactivadas
Ultimate Maps by Supsystic: version: 1.2.11, author: supsystic.com, Actualizaciones automáticas desactivadas
User Roles and Capabilities: version: 1.2.6, author: mahabub, Actualizaciones automáticas desactivadas
User Switching: version: 1.7.0, author: John Blackbourn & contributors, Actualizaciones automáticas desactivadas
WP Mail SMTP: version: 3.6.1, author: WPForms, Actualizaciones automáticas desactivadas
WP OPcache: version: 4.1.4, author: nierdz, Actualizaciones automáticas desactivadas
WP Rollback: version: 1.7.2, author: GiveWP.com, Actualizaciones automáticas desactivadas
WP Super Cache: version: 1.9.1, author: Automattic, Actualizaciones automáticas desactivadas
WPVulnerability: version: 1.1, author: closetechnology, Actualizaciones automáticas desactivadas
Yoast Duplicate Post: version: 4.5, author: Enrico Battocchi & Team Yoast, Actualizaciones automáticas desactivadas

### wp-plugins-inactive (5) ###

Banhammer Pro: version: 2.6, author: Jeff Starr, Actualizaciones automáticas desactivadas
Find My Blocks!: version: 3.5.4, author: Eddy Sims, Actualizaciones automáticas desactivadas
Loco Translate: version: 2.6.3, author: Tim Whitlock, Actualizaciones automáticas desactivadas
Rank Math SEO: version: 1.0.102, author: Rank Math, Actualizaciones automáticas desactivadas
Rank Math SEO PRO: version: 3.0.19, author: Rank Math, Actualizaciones automáticas desactivadas

### wp-media ###

image_editor: WP_Image_Editor_GD
imagick_module_version: 1808
imagemagick_version: ImageMagick 7.1.0-48 Q16-HDRI x86_64 c1ca24765:20220910 https://imagemagick.org
imagick_version: @PACKAGE_VERSION@
file_uploads: File uploads is turned off
post_max_size: 128M
upload_max_filesize: 128M
max_effective_size: 128 MB
max_file_uploads: 20
gd_version: 2.3.3
gd_formats: GIF, JPEG, PNG, WebP, BMP, XPM
ghostscript_version: 9.50

### wp-server ###

server_architecture: Linux 5.4.0-131-generic x86_64
httpd_software: nginx/1.22.1
php_version: 7.4.33 64bit
php_sapi: fpm-fcgi
max_input_variables: 1500
time_limit: 300
memory_limit: 256M
max_input_time: 300
upload_max_filesize: 128M
php_post_max_size: 128M
curl_version: 7.68.0 OpenSSL/1.1.1f
suhosin: false
imagick_availability: true
pretty_permalinks: true
htaccess_extra_rules: true

### wp-database ###

extension: mysqli
server_version: 10.6.11-MariaDB-1:10.6.11+maria~ubu2004-log
client_version: mysqlnd 7.4.33
max_allowed_packet: 134217728
max_connections: 1024

### wp-constants ###

WP_MEMORY_LIMIT: 128M
WP_MAX_MEMORY_LIMIT: 256M
WP_DEBUG: false
WP_DEBUG_DISPLAY: true
WP_DEBUG_LOG: false
SCRIPT_DEBUG: false
WP_CACHE: true
CONCATENATE_SCRIPTS: false
COMPRESS_SCRIPTS: true
COMPRESS_CSS: true
WP_ENVIRONMENT_TYPE: production
DB_CHARSET: utf8mb4
DB_COLLATE: utf8mb4_general_ci

### wp-filesystem ###

wordpress: writable
wp-content: writable
uploads: writable
plugins: writable
themes: writable
mu-plugins: writable

### wp_mail_smtp ###

version: 3.6.1
license_key_type: lite
debug: No se han encontrado avisos de depuración.
lite_install_date: Sep 9, 2020 @ 11:27am

Hi @glycymeris, sorry to hear about this. This is definitely weird, were you able to do the testing for conflicts? Thanks for providing your setup information this is really helpful.

I’m really curious about this. I suspect that it could be a conflict with GeneratePress or their Add-ons. It would be good to test for conflicts. Could you follow the following steps?

1. Deactivate all other plugins except for The Events Calendar Plugins.
2. Switching to the Default theme.

Please read the Testing for Conflicts Article before doing anything.

To be safe, we’d recommend conducting tests and updates on a Staging Server. Also, please keep a working backup of your website.

Let me know how it goes.

Best,
Abz

Hi @glycymeris,

We haven’t heard from you in a while, so I’m going to mark this as resolved. Feel free to start a new thread if you have any more questions.

Hi @abzlevelup,

sorry for the delay in my answer. Too much projects.

I did the test of conflicts and everything remained the same. Nonetheless, I made a duplication of the web in local (Local by Flywheel). Here everything works ok.

I don’t have any clue about what could be happening in the production version of the web.

I have done the copy with the same version of PHP and SQL, with nginx (the same in both servers), etc.

Do you know what could it happening?

Thanks.

The key here, I think, is that this events have to be edited with classic editor.

The thing is that the WordPress editor works well in the rest of the web. Only The events Calendar shows the classic editor.

Could it be a problem of database?

Thanks again.

Hi,

Always disappointing when support has no solution and then tries to close a thread without one. Helas not the first time this happens. The last advice I got here was to wait updating untill the problems where solved, but they aren’t solved and the thread is now marked as such. I don’t understand that.

I’ve done some digging on my own and found at least a thread of the problem in the code. I don’t understand it is not traceable when more people have the problem and I myself have it on different implementations on different hosts.

Trying to trace it using var_dumps I end up in the method Tribe__Events__Editor__Compatibility::is_blocks_editor_toggled_on().

The first statements are:

$cache     = tribe( 'cache' );
$cache_key = 'tec_editor_compatibility_' . static::$blocks_editor_key;

$is_on = $cache->get( $cache_key, '', null );
if ( $is_on !== null ) {
	return tribe_is_truthy( $is_on );
}

A var_dump() on $cache shows:

object(Tribe__Cache)#19401 (1) {
  ["non_persistent_keys":protected]=>
  array(1) {
    ["is_divi"]=>
    string(7) "is_divi"
  }
}

And $cache_key contains ‘tec_editor_compatibility_toggle_blocks_editor’.

Then $cache->get( $cache_key, '', null ); returns ” (an empty string) what makes $is_on !== null true
and makes tribe_is_truthy( $is_on ) return the value false.

So if I understand it correctly the key does not exist in the cache and so the function returns false and the legacy editor is shown instead of the block editor.

The problem that needs solving then is why doesn’t the cache contain a value for the key “tec_editor_compatibility_toggle_blocks_editor”?

In settings the option for using the block editor is checked, so it should return true.

Is that of any help or do I need to dig further?

regards, Hans

Alright, I looked somewhat further and notice that the difference between a local setup that does open the block editor and my production/staging system that doesn’t happens the first time Tribe__Events__Editor__Compatibility::is_blocks_editor_toggled() is executed.

In the system that shows the block editor correctly the first time that method is executed it first checks the cache value and when it is null it will continue to the end where it sets the cache value to null too and returns the null value to Tribe__Events__Editor__Compatibility::is_blocks_editor_toggled() that then continues and sets the value to boolean true.

The system that doesn’t show the block editor follows the same logic, but bails out early when an empty string is returned instead of null. So in that system the logic that should set the cache with the true-value is never executed.

When I check Tribe__Cache::get() it calls wp_cache_get( $this->get_id( $id, $expiration_trigger ), $group ); but that call returns a different value on both systems.

In the system that opens the block editor wp_cache_get() returns the boolean value false and in the other system wp_cache_get() returns an empty string and that causes the problem further on.

I don’t know why there is a difference in response of wp_cache_get(), but that is where the problem originates.