Skip to content

Releases: unclecheese/silverstripe-dropzone

1.4.6: Merge pull request #65 from navidonskis/master

01 Dec 06:50
Compare
Choose a tag to compare

1.4.5: Merge pull request #64 from navidonskis/master

29 Nov 20:19
Compare
Choose a tag to compare
this fix now handling files from client side

1.4.4: Merge pull request #63 from digitall-it/master

16 Nov 21:02
Compare
Choose a tag to compare

1.4.3

28 Sep 20:36
Compare
Choose a tag to compare
BUGFIX: Use implode() instead of explode() on array

1.4.2: Merge pull request #57 from SilbinaryWolf/fix-filesecurity

21 Sep 05:15
Compare
Choose a tag to compare
fix(Security): Previous commit broke general CMS use cases

1.4.1: Merge pull request #37 from nimeso/patch-2

20 Sep 11:22
Compare
Choose a tag to compare

1.4.0: Merge pull request #56 from SilbinaryWolf/fix-filesecurity

20 Sep 11:19
Compare
Choose a tag to compare
fix(Security): Store uploaded files in a 'validFileIDs' session and ensure that when the user submits the form, that they uploaded the files and aren't trying to induce quirky behaviour.

1.3.0: Merge pull request #55 from sanderha/maxfilenumber-dropzone-api

08 Sep 00:24
Compare
Choose a tag to compare

1.2.4: BUGFIX: saveInto() was not working as expected for UnsavedRelationList

05 Sep 07:09
Compare
Choose a tag to compare
Most commonly seen in frontend forms -- if the form was not bound to a record (e.g. `loadDataFrom()`), the `getRelation()` method was returning false no matter what, because it relied on `$form->getRecord()`. In the `saveInto($record)` method, it is critical that `getRelation()` is explicitly passed the record it is checking, rather than relying on the precondition of the form being bound to a record.

1.2.3

31 May 01:48
Compare
Choose a tag to compare
BUGFIX: is_array returning false negative for empty sets