Add support for Neo plugin #882
Replies: 8 comments
-
@jamielaughton Unfortunately, Neo support isn't ready for Feed Me, which would explain why you're seeing these specific results. We can't provide an ETA on this unfortunately, but it'll be done (along with other populate third-party fields and elements) before the end of beta - likely in 1-2 months. I should also mention - this would be for Feed Me 3. There are no plans to implement this functionality for Feed Me 2, which isn't going to implement new features - just fixes. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the reply, Good to hear it will be supported soon, I'll keep an eye out for the updates! |
Beta Was this translation helpful? Give feedback.
-
👍 for this feature. I'll trade a kidney |
Beta Was this translation helpful? Give feedback.
-
We need it too :| |
Beta Was this translation helpful? Give feedback.
-
Any progress on this, be an absolute life saver. |
Beta Was this translation helpful? Give feedback.
-
👍 would like to see this |
Beta Was this translation helpful? Give feedback.
-
I ran into this issue. Tried to export / import with feedme and I wondered why my neo fields wouldn't show as single items that I could map. I'm even using a combo of Neo + Super table 😢 |
Beta Was this translation helpful? Give feedback.
-
Feed Me support now included in Neo 3.5.0 - see the usage document for details. |
Beta Was this translation helpful? Give feedback.
-
Description
I have Neo fields in my entries which I want to be populated by a JSON feed pulled in through Feed Me, im using elementApi top create the JSON feed.
The Feed Me setup runs fine and there are no errors. My issue is that I'm un-able to map the Neo Fields when it comes to the configuration screen (where you select the Feed Element from your fields to map with the JSON fields), because I am only seeing the top-level of the Neo fields.
Any help would be greatly appreciated
Cheers,
Jamie
Additional info
Beta Was this translation helpful? Give feedback.
All reactions