I confirm, it’s broken.
[Error] TypeError: null is not an object (evaluating 'getBlock(clientId).innerBlocks')
TemplateBuilder
je — react-dom.min.js:1983
ph — react-dom.min.js:5856
lh — react-dom.min.js:3325
O — react-dom.min.js:3194
O
ze — react-dom.min.js:3061
ze
(anonimowa funkcja) — react-dom.min.js:1332
unstable_runWithPriority — react.min.js:26:342
mg — react-dom.min.js:1328
V — react-dom.min.js:1320
Be — react-dom.min.js:3102
xi — react-dom.min.js:890
xi
ve (react-dom.min.js:103:493)
(anonimowa funkcja) (react-dom.min.js:114:499)
yg (react-dom.min.js:62)
xg (react-dom.min.js:61:354)
Ti (react-dom.min.js:148:366)
Ti
unstable_runWithPriority (react.min.js:26:342)
Ia (react-dom.min.js:140:410)
Ia
ze (react-dom.min.js:118)
ze
(anonimowa funkcja) (react-dom.min.js:53)
unstable_runWithPriority (react.min.js:26:342)
mg (react-dom.min.js:52:499)
V (react-dom.min.js:52:434)
Be (react-dom.min.js:119)
xi (react-dom.min.js:39:176)
xi
[Error] TypeError: getBlockParents is not a function. (In 'getBlockParents(clientId)', 'getBlockParents' is undefined)
getRootMessages
(anonimowa funkcja)
Vb — react-dom.min.js:2639
Xi — react-dom.min.js:4060
Xi
unstable_runWithPriority — react.min.js:26:342
O — react-dom.min.js:3165
O
ze — react-dom.min.js:3061
ze
(anonimowa funkcja) — react-dom.min.js:1332
unstable_runWithPriority — react.min.js:26:342
mg — react-dom.min.js:1328
V — react-dom.min.js:1320
Be — react-dom.min.js:3102
xi — react-dom.min.js:890
xi
ve (react-dom.min.js:103:493)
(anonimowa funkcja) (react-dom.min.js:114:499)
yg (react-dom.min.js:62)
xg (react-dom.min.js:61:302)
Ti (react-dom.min.js:148:366)
Ti
unstable_runWithPriority (react.min.js:26:342)
Ia (react-dom.min.js:140:410)
Ia
ze (react-dom.min.js:118)
ze
(anonimowa funkcja) (react-dom.min.js:53)
unstable_runWithPriority (react.min.js:26:342)
mg (react-dom.min.js:52:499)
V (react-dom.min.js:52:434)
Be (react-dom.min.js:119)
xi (react-dom.min.js:39:176)
xi
Thanks for the feedback, @emmek. I’m watching this plugin closely for the day it’s stable. Looks so promising. Thanks.
Really glad to see this error resolved in the latest push, @emmek.