| 1 | | Yes, I'm having the exact same issue. SCF or ACF with Guttenberg enabled. Same JS error. Only way around it is to enable Delay Initialization on the field in ACF/SCF. WP 6.8.1 This is happening to me in Chrome too. Rolled back to 6.6.2 |
| | 1 | Yes, I'm having the exact same issue. SCF or ACF with Guttenberg enabled. Same JS error. Only way around it is to enable Delay Initialization on the field in ACF/SCF. WP 6.8.1 This is happening to me in Chrome too. Rolled back to 6.6.2 |
| | 2 | |
| | 3 | ---- |
| | 4 | |
| | 5 | The TinyMCE editor fails to initialise properly when using a combination of Gutenberg, and SCF/ACF WYSIWYG fields. On page load the Visual Tab is empty, if you switch back from Text to Visual the JS console produces the following error: |
| | 6 | |
| | 7 | {{{ |
| | 8 | wp-tinymce.js?ver=49110-20201110:3 Uncaught TypeError: Cannot read properties of null (reading 'setBaseAndExtent') |
| | 9 | at i (wp-tinymce.js?ver=49110-20201110:3:291936) |
| | 10 | at Object.each (wp-tinymce.js?ver=49110-20201110:3:1346) |
| | 11 | at Object.select (wp-tinymce.js?ver=49110-20201110:3:293163) |
| | 12 | at _ (editor.min.js?ver=6.8.1:2:5063) |
| | 13 | at n (editor.min.js?ver=6.8.1:2:1731) |
| | 14 | at HTMLDocument.<anonymous> (editor.min.js?ver=6.8.1:2:248) |
| | 15 | at C (wp-tinymce.js?ver=49110-20201110:3:10800) |
| | 16 | at HTMLDocument.d (wp-tinymce.js?ver=49110-20201110:3:10946) |
| | 17 | i @ wp-tinymce.js?ver=49110-20201110:3 |
| | 18 | each @ wp-tinymce.js?ver=49110-20201110:3 |
| | 19 | select @ wp-tinymce.js?ver=49110-20201110:3 |
| | 20 | _ @ editor.min.js?ver=6.8.1:2 |
| | 21 | n @ editor.min.js?ver=6.8.1:2 |
| | 22 | (anonymous) @ editor.min.js?ver=6.8.1:2 |
| | 23 | C @ wp-tinymce.js?ver=49110-20201110:3 |
| | 24 | d @ wp-tinymce.js?ver=49110-20201110:3Understand this error |
| | 25 | }}} |
| | 26 | |
| | 27 | Rolling back to 6.6.2 resolves the issue, as does using ClassicEditor plugin. |