Benjamin Turner

This came up in the Local Community forums:

– https://localwp.com/community/t/where-is-the-5-8-full-site-editing-feature/26860?u=ben.turner

The main reply I gave there was to double check that a FSE compatible theme is installed. The twentytwentyone theme that ships with WP core doesn’t have this, but the tt1-blocks theme does.

Following the steps outlined in the Make Handbook for FSE editing:

https://make.www.ads-software.com/test/handbook/full-site-editing-outreach-experiment/how-to-test-fse/#individual-process

That process can be done easily with WPCLI:

1. Create new site somewhere for testing. (I used https://localwp.com but others would work)

2. Within a site shell, use wpcli to install Gutenberg and the tt1-blocks theme:

wp theme install tt1-blocks --activate
wp plugin install gutenberg --activate

3. Log into the WP admin and notice the “Site Editor (beta)” link in the admin menu.

Here’s a screenshot to help visualize: https://i.getf.ly/E0uj5rmo

Yes, I have tried deactivating and re-activating the plugin. This does not solve the problem.

I can confirm that the solution found in the above link does allow me to install a current version of ‘Events Manager’.

I ended up dropping all tables that had ‘dbem_’ in them, and removing items in wp_options that had a value ‘dbem_’ in it.

I won’t say that this is a viable solution seeing as how I now do not have any of the events. But luckily I’m doing this on a dev site, so now I’m going to try and zero in on what setting in the DB was really causing the problems that I’m seeing.

I am experiencing this ‘upgrade to version’ cycle as well.

There is another answer on the forums that seems to be what might fix things for me. I haven’t tried this yet, but I do have both the stated plugins:

‘Events Manager’ and ‘Events Manager Extended’

https://www.ads-software.com/support/topic/plugin-events-manager-installation-problems-any-version