Legacy WordPress customiser now appearing in FSE based websites

Bug
1

Hi Team,

I noticed with one of the recent mainWP child plugin updates that it’s automatically adding the legacy/classic WordPress ‘Customiser’ option to the WP admin appearance menu and also the front end of the website.

Re-introducing legacy WP features is confusing for my clients, who all use custom FSE builds where the customer is no longer relevant and is removed by default on all FSE-based websites by WP core. I am unsure why this has been reintroduced. Can I ask why this was reintroduced and what it is for?

Thanks,
Tony

2

Hey @Tecology

Thanks for reporting this. We checked this on our side and the MainWP Child plugin is not intentionally adding the legacy Customizer menu as a feature.

What is happening is that our Network Activity logging hooks into WordPress’ Customizer events so it can detect and log changes made to menus/site settings when those changes are saved through the Customizer.

WordPress core treats the presence of that Customizer hook as a signal that the Customizer is still in use, so on FSE/block-theme sites it can cause the “Customize” option to appear again in Appearance and in the front-end admin toolbar.

That is not the intended user-facing behavior, especially for FSE sites where the Customizer is normally hidden.

We’ll review this and look into adjusting the implementation in a future release so MainWP can continue tracking relevant activity without unnecessarily exposing the legacy Customizer UI.

3

Thanks for the response @bojan and it would be great if the implementation was adjusted for this. I will go ahead and add a script to hide the customiser on all active production websites as a short-term fix to this.

4

Hey @Tecology

A fix for this issue was included in version 6.0.11. of the MainWP Child plugin.

Thanks again for reporting this to us.

5

Cheers @bojan - just updated all sites and the fix is working perfectly!