- Issue created by @nginex
- First commit to issue fork.
- 🇮🇳India Supreetam09 Kolkata
This is something we also needed. In our project, there are some content, for which the dependency tree is so huge that the Export page throws 500 PHP out-of-memory error, even with setting memory_limit to -1
We implemented the code from the MR. It introduces a new settings key which will be used to identify entity types that will be omitted from the export list for referenced entities. We had to exclude all node entity type references from content (other entity reference dependencies are still there) - and Export page started opening fine.
Its now exporting importing partially and with the settings, we can control it.
Although I understand that this is not perfect. We can further fine tune the control. Currently its entity level control - but I can think of more ways like bundle level control or hierarchy level control (like 1st child node reference will be exported but another node referenced to the 1st child i.e. child's child won't be exported).
For now, I am adding a starting point.
Let me know your thoughts!
- 🇺🇦Ukraine nginex
Thanks for the patch, I will check and test it when I get some time. Meanwhile you can also test similar issue but with different solution here
https://www.drupal.org/project/single_content_sync/issues/3511539#commen... 🐛 Recursion takes too much memory compared to earlier versions (1.4.6 or earlier) Active
- 🇮🇳India Supreetam09 Kolkata
Unfortunately the patch from MR does not apply on current stable version 1.4.10 as there's been too many changes in 1.4.x. I am adding a patch only for 1.4.10 release.
Consider the MR for the dev branch. - 🇺🇦Ukraine nginex
I'm planning to create 1.4.11 during a week, so already merged a few issues