You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
When you clone an existing matrix block, the matrix block gets cloned, but the fields inside the newly created matrix block won't get divided into their associated tabs (MatrixMate feature). This makes the matrix block messy and cluttered, and that's why we installed the MatrixMate plugin.
I think this is something that should be fixed in Smith, not in MatrixMate.
Most likely, the Smith plugin just needs to make sure that when it clones a block, the Matrix field's Craft.MatrixInput instance emits the same JavaScript event(s) that are emitted when blocks are added natively – specifically, the blockAdded event, which MatrixMate listens to in order to instantiate new blocks.
But looks like this was actually due to an underlying issue with rendering blocks, that hadn't been updated properly with Craft 3.5+ field layout changes.
Description
When you clone an existing matrix block, the matrix block gets cloned, but the fields inside the newly created matrix block won't get divided into their associated tabs (MatrixMate feature). This makes the matrix block messy and cluttered, and that's why we installed the MatrixMate plugin.
Screen.Recording.2021-05-28.at.15.31.50.mov
According to the MatrixMate developer, the problem most likely happens because Smith doesn't emit the same events as the native create function.
Steps to reproduce
Additional info
Additional context
The bug report on the MatrixMate repository: vaersaagod/matrixmate#32
The text was updated successfully, but these errors were encountered: