-
-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Neo Support #30
Comments
+1 |
@aelvan has anyone ever looked at this or suggested a solution? |
I've never used Neo, so I have no idea if it works or not. I'm not sure why it wouldn't, since it's basically just a plain text field. I see on this page in the neo docs that it says that preparse field may cause neo blocks to disappear, I suspect that that's just due to some ill-behaving Twig not cloning element queries when accessing them. |
@aelvan - I haven't managed to get it to work with Neo (my preparse field just stays blank) but I'll try again! |
For anyone using Neo, I only have a single preparse field installed which aims to serialize all the content contained in the Neo blocks for search indexing and SEO. Even having this single field (it's completely separate to the Neo field), causes it to fail on-save. See spicywebau/craft-neo#398 for a video. I've had to disable the plugin altogether, otherwise my blocks disappear. |
@engram-design I'll take a look at this as soon as I can 👍 |
Any plans to add Neo support or a workaround for the described bug? We are using preparse-field on a section block (Neo field) to prerender a anchor id based on the title and now experienced the same loss of nesting of all neo block-children described here: craftcms/cms#13256 |
Thanks for the awesome plugin. Just wondering, does Preparse support Neo fields? I noticed in the README that you mentioned some custom templating for matrix fields but couldn't find anything online for Neo fields. Is Neo something you support? If so, how would I call a Neo sibling/field in my Preparse field?
Cc @benjamminf
The text was updated successfully, but these errors were encountered: