For some time now (I don't remember for which version of Toolset Blocks the problem started appearing) the HTML view of the Fields and Text Block no longer works correctly.
Code selection and modifications in the code are made almost impossible.
I'm experiencing the issue in both Chrome and Firefox browser.
On my own test site (with the latest plugin versions and WordPress 6) I don't experience any such issues, which leads me to think there is something else interfering on the page with your site.
Can you check for any conflicts before going any further?
Disable all plugins except Toolset, and switch theme to twentytwentyone. Then try editing the content of a Fields and Text block again. If the problem no longer appears then you should be able to determine the source of any conflict that triggers the problem by a process of elimination.
Sorry, I don't have any news yet, I just wanted to point out, ahead of the weekend, that you can use the Custom HTML block as an alternative to the Fields and Text block. You do have to enter the shortcodes manually, but if you go to Toolset > Settings and enable the Toolset Shortcodes link in the admin toolbar you can use that to generate the shortcodes and then paste them into the Custom HTML block as required.
I managed to isolate the cause of the problem: the GeneratePress theme injects CSS styles which break the formatting of the codemirror instance used to provide the code editor of the Fields and Text block.
I've escalated this to the developers—hopefully they can produce a permanent fix—but in the meantime as a workaround you can add a little code snippet that adds some inline styling in the document head to override the relevant GeneratePress style declaration.
You can add the following code as a snippet at Toolset > Settings > Custom Code:
function ts_gp_style_override() {
echo '<style>.editor-styles-wrapper .block-editor-block-list__layout pre {margin-bottom: 0!important; padding: 0 4px!important}</style>';
}
add_action( 'admin_head', 'ts_gp_style_override', 11 );
I suggest we close here, and you can subscribe to the comments in the erratum about this issue for further updates:
