Open kmgdevelopment opened 3 months ago
Super Table and Table fields aren't compatible, so it might be a bit of a stretch to provide a migration for that. There's only a very small percentage of Super Table fields that are going to be migratable. It's something we could provide though, just in case (like in your scenario) a Super Table field is using only fields that a Table field supports like text, date, color, dropdown, etc. It'd probably just list only the Super Table fields that could be converted.
Oy, that's a pain. I know I'm not the only person who was using Super Table a lot for more robust tabular data, not necessarily for matrix-in-matrix support. Shame there isn't an in-between field that can be used.
I'd still like to keep this issue open as it's something we can look into! Like I said, not every Super Table field is going to be able to be converted to a Table field, but for the ones that are, we could provide an option for it.
What are you trying to do?
I've been using Super Table since Craft 3 when Craft's native table field didn't allow for robust cell types like dropdowns. So when Craft 4 and its enhanced table fields came along I didn't bother migrating because Super Table was working fine for me and hey who wants extra work right?
But now we've arrived at Craft 5 and Super Table is going away, and I find that for some of my fields I don't need to convert from Super Table to Matrix, but just Super Table to native table. Matrix works fine, but it's kind of overkill and the UI is a beast.
What's your proposed solution?
In the Super Table Craft 5 migration script, include the ability to choose whether to convert Super Table fields to matrix fields or to native table fields.
Additional context
No response