Closed sleithart closed 3 months ago
Thanks for reporting this - should be fixed now for the next release. In the meantime, you can get the fix by setting your composer.json file's spicyweb/craft-neo
requirement to 4.x-dev as 4.0.8
and running composer update
.
Worked great, thanks for the quick fix!
On March 25, 2024, "height[bot]" @.***> wrote:
Thanks for reporting this - should be fixed now for the next release. In the meantime, you can get the fix by setting your composer.json file's spicyweb/craft-neo requirement to 4.x-dev as 4.0.8 and running composer update.
— Reply to this email directly, view it on GitHub https://github.com/spicywebau/craft-neo/issues/868#issuecomment- 2019201061, or unsubscribe https://github.com/notifications/unsubscribe- auth/AAIOXBNJXEWS4TZFYIDWRP3Y2DCHTAVCNFSM6AAAAABFHZHFZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJZGIYDCMBWGE. You are receiving this because you authored the thread.Message ID: @.***>
Bug Description
I switched a client over from an English-only to multiple sites—one English, one Spanish. When I update the Neo field I'm using as a page builder, I encounter this error on the Craft Queue.
I'm not entirely sure if this is a blocker to pushing out my changes, or if I need to wait until it's resolved to move forward? Is this something I can ignore? If not, can I take steps to resolve it, or do I need to wait for a plugin update?
Steps to reproduce
Expected behaviour
I would expect this to propagate properly
Neo version
4.0.8
Craft CMS version
4.8.4
What is the affected Neo field's propagation method?
I changed it, which threw the error (see above)
Does this issue involve templating, and if so, is eager-loading used?
This is not a templating issue