Lots of potential, a lot to be desired

Hi @jwrhodes2008 – I’d like to try to better understand what you mean by:

The biggest problem is the new theme setup removes menu editing from the admin bar. This also means the menu links can no longer be set as conditional (i.e. membership only access, logged vs logged out).

Could you tell me a little more about how you were editing your menus before that isn’t possible with Full-Site Editing FSE in Twenty Twenty-Two? I can then take a look and see if there’s already an enhancement on the radar.

Another major problem is frequent errors from excessive resource usage during editing. While editing the site, I will often get smacked with ‘blocks can not load, check resources’ notification or something to that nature.

Not ideal indeed. ?? Do you recall more details about what specific action you’re taking when this happens? Adding a specific block? Editing a specific template? Adding a new template?

Are you also able to look in the browser console when this happens and tell me if you see any errors there?

Thank you!

Could you tell me a little more about how you were editing your menus before that isn’t possible with Full-Site Editing FSE in Twenty Twenty-Two? I can then take a look and see if there’s already an enhancement on the radar.

The biggest problem is the new theme setup removes menu editing from the admin bar. This also means the menu links can no longer be set as conditional (i.e. membership only access, logged vs logged out).

So I found this issue to actually be two separate things. The first problem was actually the twenty twenty two theme incompatibility issue with three plugins: Master Study (an LMS plugin), the Buddypress plugin, and the Paid Membership Pro plugin. I believe BP and PMPro fixed these problems.

The second problem is really just a UI problem. Finding the way to restrict access to specific elements of the navigation by status, capability, etc. was still difficult to find from a UI perspective. In the new FSE structure, we no longer have menu editing that appears on the admin bar. So, this makes editing the menu much less intuitive as you have to bounce between 4 areas to make a single edit: 1)’selected navigation block’ on the template and its block setting, 2)the individual ‘navigation block’ nestled within the ‘selected navigation block’ and that specific block setting, 3) the navigation plugin or the list view editor to edit the navigation architecture, and then 4) hidden at the bottom of the block editor is the advance editor that sometimes has ‘display condition’ but sometimes does not.

Could you tell me a little more about how you were editing your menus before that isn’t possible with Full-Site Editing FSE in Twenty Twenty-Two? I can then take a look and see if there’s already an enhancement on the radar.

Another major problem is frequent errors from excessive resource usage during editing. While editing the site, I will often get smacked with ‘blocks can not load, check resources’ notification or something to that nature.

I have not actually seen this issue in the past 2 weeks. But when it did occur, it happened when I was making edits to a page not a template and the blocks were usually 1)a divider block, 2)a spacer block, 3) or a media upload block. Then it would happen when I loaded a long page or it would happen right after pressing save. This was also inconsistent as sometimes half the page would load with only some of those elements having the error while sections of the page with the same elements loaded fine.

So I found this issue to actually be two separate things. The first problem was actually the twenty twenty two theme incompatibility issue with three plugins: Master Study (an LMS plugin), the Buddypress plugin, and the Paid Membership Pro plugin. I believe BP and PMPro fixed these problems.

Ah, glad two of the three plugin compatibility issues have been resolved.

The second problem is really just a UI problem. Finding the way to restrict access to specific elements of the navigation by status, capability, etc. was still difficult to find from a UI perspective.

Gotcha, I hear what you’re saying. I wonder if the plugin you’re using to restrict access to certain menu items by role will be made more FSE-compatible in the future so the process becomes more streamlined. You may want to ask the plugin developers if that’s something on their radar.

I have not actually seen this issue in the past 2 weeks. But when it did occur, it happened when I was making edits to a page not a template and the blocks were usually 1)a divider block, 2)a spacer block, 3) or a media upload block.

Thanks for sharing those details. If it happens again, you could try opening the browser console and taking a screenshot of any errors there. Then, make a post in the theme’s support forum and folks could try to help troubleshoot further.