Repeater field export/import needs to convert parent_id and template_id to paths and names, respectively

[adrianbj]

Short description of the issue

Repeater field export/import needs to convert parent_id and template_id to paths and names, respectively

Expected behavior

I should be able to import a repeater field from one site into another

Actual behavior

Doesn't really work because page/template IDs don't match up

[Toutouwai]

Related: #156

[ryancramerdesign]

This is specific to the Field export/import from Setup > Fields, right? Just wanted to make sure we weren't talking about Page export/import (which does support repeaters). But repeaters aren't supported for "field" import. A repeater field definition involves not just a field, but templates, fieldgroups, pages and field/template contexts. They are quite a bit more complex than what Field export/import is built for. So FieldtypeRepeater would need to implement its own exportConfigData() and importConfigData() methods, that would have to do quite a bit of work. I've been meaning to implement these, so will give it another look this week.

[adrianbj]

This is specific to the Field export/import from Setup > Fields, right?

Yes!

A repeater field definition involves not just a field, but templates, fieldgroups, pages and field/template contexts. They are quite a bit more complex than what Field export/import is built for.

Yeah, I know - I had to deal with it in my migrator module, but it's not too hard :)

[ryancramerdesign]

Yeah, I know - I had to deal with it in my migrator module, but it's not too hard :)

Okay, you are right, it was easier than I thought. I've gone ahead and added support for this. Seems to be working well here, but definitely needs more testing.

[adrianbj]

Great - thank you!