Collection field support is released in the current master. For this to work you'll need to add the "[_c]" marker into the key name. eg:
namespace: custom_fields key name: some-key[_c] value: your value
The marker will be hidden from the client side so it does not look as ugly.
A small updates has been made to resolve this issue. When you next run the tool you should be seeing the new version.
Really great plugin. I appreciate your effort and dedication. One question for you—are you able to easily make the inputs for the custom fields <textarea>'s instead of text type inputs? Or an option to do as such? My end hope is to implement a rich text editor for these fields as they are able to maintain any HTML put it them.
It would be easy enough to make them text areas or add a marker to set them as such (or auto switch them). Still early days on this tool with plenty of work still needing to be done but I agree 100% that it needs text areas. People are starting to show some more interest in it, so I'll pull my finger out and do the same.
As for your hope - that pretty easy. I did add a second (and third) RTE for a customised version so it's quite possible should you feel that way inclined. Image inserts and such are flaky, but generally editing is fine.
Thanks for your reply Jason. Can you point me in the right direction on how to implement this as a custom feature? Text input is all I need, image inserts aren't necessary for the store I'm building.
I'd be able to host the customized version on my end, but don't want to go outside your comfort zone with that.
|41 seconds ago|
|2 hours ago|