Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Craft 5 Version #72

Closed
CreateSean opened this issue Mar 26, 2024 · 3 comments
Closed

Craft 5 Version #72

CreateSean opened this issue Mar 26, 2024 · 3 comments

Comments

@CreateSean
Copy link

Do you have plans to release a craft 5 compatible version?

@mmikkel
Copy link
Member

mmikkel commented Mar 26, 2024

Honestly, still undecided – but I'm leaning strongly towards retiring the plugin for Craft 5.

The fact is that Craft 5.0 makes MatrixMate almost completely redundant:

  • Block tabs: natively supported via entry types
  • Hidden block types per section/category/etc: as entry types are decoupled in Craft 5, you achieve basically the same result by creating multiple Matrix fields and mix'n'match different entry types inside them
  • Hidden fields per block type: conditional support for inline Matrix fields should cover this.

To my mind, the only important feature in MatrixMate that isn't covered by Craft 5.0 is the ability to group block/entry types on a contextual basis. However, such a feature was discussed during the beta, so FWIW it's on P&T's radar and maybe we'll see something like it added in a 5.x release.

IMO, continuing to support features that are basically just different ways to do something that is now possible in core, is not a sensible way forward. So, if we did port MatrixMate to Craft 5, it'd necessarily be a very different plugin; basically all we'd keep is the grouping feature, and even that I would probably implement similarly to how P&T would likely implement this feature, i.e. "headings within the single disclosure menu". Not because that sounds like an objectively better UX vs. having distinct disclosure menus per type group, but because I think designing for redundancy is the most sensible approach for plugins like MatrixMate.

As far as existing sites go – I totally get that upgrading sites that are dependent on MatrixMate for wrangling huge mega-Matrixes, is probably not going to be fun 😬 The silver lining is that the new content architecture in Craft 5 should make it relatively simple to actually move Matrix entries (nee blocks) from one Matrix field to another – which paves the way for a migration path where bigger Matrix fields can be "split" into different, smaller Matrix fields, sharing (some of) the same entry types. I know that a potential CLI command for moving entries to a different section has been talked about, so it would make sense that something similar becomes available to Matrix entries in one way or another. However this shakes out, Craft 4 isn't EOL until April 2026, so I don't believe anyone should be in a huge rush to upgrade just yet (especially not anyone with massive mega-Matrixes 😅).

@mmikkel mmikkel pinned this issue Mar 26, 2024
@mmikkel
Copy link
Member

mmikkel commented May 30, 2024

Probably not a huge surprise, but I decided that MatrixMate is definitely not being updated to work on Craft 5.

At some point, I might (strong emphasis on might) look into creating some sort of utility/migration to help convert MatrixMate configs to discrete Matrix fields, with the proper distribution of entry types.

Big thanks for the interest in this little plugin over the years, all the PRs and bug reports ❤️

@mmikkel mmikkel closed this as completed May 30, 2024
@lindseydiloreto
Copy link

I fully respect that decision, we retired Spoon for the exact same reasons. 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants