-
Notifications
You must be signed in to change notification settings - Fork 139
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
Table doesn't import deeply nested data #464
Comments
I have the same issue here. Here is my test data.
Feed Me version: 3.1.15 |
Same issue over here. Any news @brandonkelly? |
Same issue with product variant table feeds being ignored. I thought it might be Hash::get($fieldInfo, 'field') within craft\feedme\services\Process But it is not unless go further into seeing how it keeps processing and matching up fields. So I thought its lines 345-348 with the foreach loop of:
Of course I am probably completely wrong as Im just starting to look through but yeh it comes back empty If i find a quick fix I'll post later |
I replaced the table with a matrix field. That worked well with very little adoption in the template. |
That I might do then! But Im in the middle of stepping through it all so will update if I find a resolution. Otherwise admit defeat and go matrix! |
A few months ago I also dug through the code. I was able to isolate the issue but wasn’t able to fix it. |
Oh it sounds like then I am doomed to the same fate. Or the format of the table data nested just doesn't get picked up in variants array |
Oh hang on, its the CommerceProduct class itself in elements. I've got to the ComplexFields and their is a check for matrix field. Did you get similar, wondering if just mush in a check for table? |
Yes |
@paulweareframework |
Is this ever going to get fixed? We ran into this problem for one of our sites. |
This is resolved for the next v4 and v5 releases via #1268 |
Description
Importing deeply nested data into a table or supertable field does not work.
This works:
This doesn't:
Steps to reproduce
Additional info
The text was updated successfully, but these errors were encountered: