Thread

Hey everyone,

This change to SafeCracker’s code was intentional, and it was necessary to fix a bug where SafeCracker File validation didn’t behave as expected. Pixel & Tonic will need to update Matrix to work with the changes made to SafeCracker in order for Matrix to remain compatible. There’s already an open support case concerning this at their support site, so you’ll want to follow that discussion there until P&T is able to roll-out an update.

Anything else we can help with?

Hi Kevin,

Thanks for sharing the background of this issue. That is very relevant information for me since it narrows down things while searching for a fix or workaround (I need a working site!).

Will continue the discussion on the P&T support pages then, but for those reading this thread:
I’m working on a form with manually-coded Matrix fields and I’ve found that using ‘field_id_DD’ for your input names instead of ‘short_field_name’ makes all work ‘out of the box’ (so that’s with the most recent versions and no modifications).

Thanks for posting a workaround, Joost.

Since this is something P&T will need to address in an update to Matrix, I’m going to close this thread up. Let me again recommend everyone follow along in the discussion at P&T’s support site.