modmore
Parent
Parent ID must be a resource already set to be a container, otherwise new resources created in parallel, not below.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
That shouldnt be a problem - the MODX side of the script should handle that perfectly..
What version of MODX are you using? Op 13 jan. 2012 07:15 schreef "Nic Boyde" < [email protected]> het volgende:
Parent ID must be a resource already set to be a container, otherwise new resources created in parallel, not below.
Reply to this email directly or view it on GitHub: https://github.com/Mark-H/importX/issues/31
In this instance, Revo 2.1.2.
I created a resource to be the target parent, and made it use the template I wished the future children to adopt, one with lots of custom TVs.
A test import of one record was created at the same level as the parent, and none of the TVs were picked up.
And the child had the default template, not the one I wanted.
I first changed the target parent to be a container and repeated the test. This time the new resource was in the right place, but still with the wrong template. I changed the new child resource to the correct template, but the TVs had not been populated.
I then changed the site's default template to the one I wished the new imported children to use, then everything went through smoothly. 220 records, each with 20 fields, one of which was a "tags" tv. 10 seconds. Good program!
I deleted each imported record and target parent and created new ones for each of the tests.
It is possible there are some non-standard system parameters in my configuration - I use the site concerned to test new ideas before trying them out on live sites, so it might well be full of rubbish. If you can't reproduce my finding, and it's important, let me know and I'll send you my set-up in full if you want it.