Bug report Wordpress plugin: Disabling support for full site editor has side effects
SOLVE
In update 11.0.55 (2024-04-12) of the Wordpress plugin, in registerFormBlock.tsx (line 47) a condition has been added to disable the Hubspot blocks in the full site editor.
Unfortunately, this condition breaks the blocks in the previous gutenberg editor as well (see screenshot 1). Fortunately, due to the shortcode still being rendered, pages in production are not affected.
Bug report Wordpress plugin: Disabling support for full site editor has side effects
SOLVE
It appears that the condition added in registerFormBlock.tsx (line 47) in update 11.0.55 (2024-04-12) has inadvertently disabled HubSpot blocks not only in the full site editor but also in the previous Gutenberg editor. This issue likely stems from the condition not differentiating between the two editors.
Suggested Solution:
Modify the Condition: Update the condition in registerFormBlock.tsx to check specifically if the full site editor is being used. You can do this by inspecting the editor context before disabling the blocks.
if (isFullSiteEditor) { // Disable HubSpot blocks only in the full site editor }
Testing: Once the condition is adjusted, test the HubSpot blocks in both the full site editor and the Gutenberg editor to ensure they function correctly in both environments.
This should restore the functionality in the Gutenberg editor while keeping the intended behavior for the full site editor.