Sorry to bother —
Whilst my existing blocks are now visible, Im not longer able to insert new blocks of existing types, with the error “Block X can;t be inserted”
@twansparant – can you confirm this the same for yourself?
Suspect similar updates may need to be applied to some js as console is reading
deprecated.js?ver=741e32edb0e7c2dd30da:115 wp.editPost.PluginBlockSettingsMenuItem is deprecated since version 6.6. Please use wp.editor.PluginBlockSettingsMenuItem instead.
deprecated @ deprecated.js?ver=741e32edb0e7c2dd30da:115Understand this warning
deprecated.js?ver=741e32edb0e7c2dd30da:115 wp.editPost.PluginDocumentSettingPanel is deprecated since version 6.6. Please use wp.editor.PluginDocumentSettingPanel instead.
+1 Confirmed works.
Thanks again
Holy cow chaps. Highly grateful for this action.
I promise my next project will be a fresh build based off acorn 3 and the latest sage.
Does anyone know of a recommended upgrade path to apply to existing acorn/sage projects ?
Or rather a recommended good form for building
I spent a fair bit of time constructing my personal boilerplate to kickstart a project & whilst I’m happy to reconstruct it (& accept theres always a benifit to a fresh start) – it would be great to approach it with a mindset of long term maintainability & adopt any new features bought by latter versions of acorn/sage.
I suppose theres not much way of being certain how the future itterations will be structured though.
Was hoping i could just override the compose() method in my class but no such luck
… Alas, an empty array tests false so presumbly we need to pop something in there?
Strangely – my Block class has public $parent = []; defined in it
– but this doesnt cut it
I would be under the assumption that this was considered “set” as therefore the the test $this->parent wouldn’t fail and return null.
LINE 274 of vendor/log1x/acf-composer/src/Block.php …
Changed ‘parent’ => $this->parent ?: null,
to
‘parent’ => $this->parent ?: [],
and everything works again.
Not ideal of course to go editing vendor files but I don’t know how to patch them “correctly”
Presume some script can be created in composer file to apply such a patch?
If anyone can advise, I’d appreciate it
Same here,
On Acorn 2.1 but the upgrade path looks shaky
Appreciate any insight
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!
We use cookies to offer you a better browsing experience, analyze site traffic and personalize content. Read about how we use cookies and how you can control them in our Privacy Policy. If you continue to use this site, you consent to our use of cookies.