Closed chrispenny closed 1 year ago
Just for the sake of clarity, I'm assuming this is with a has_one
relationship?
Did you set any additional config (either globally or per instance) for the upload field or validator?
Thanks, @GuySartorelli. Correct, it's a has_one
(added to the description).
The project is also running KFC and Fluent, but KFC doesn't impact anything until after a write is performed, and for Fluent this field is not localised.
I can definitely reproduce this, but I can't figure out what's causing it. I can see that the number of files that our react components are aware of is correct all throughout the process. I've also console logged the files array from the underlying dropzone instance and that seems to always be correct as well. So I'm not sure what's causing it to think we've hit the limit.
PR merged
@chrispenny You can use 2.0.x-dev
as a dependency constraint for now if you need to, but we're intending to launch CMS 5 stable pretty soon.
Thanks, team!!
I'm still getting a seemingly related "You can not upload any more files." bug in 5 stable.
To reproduce:
Result: "You can not upload any more files."
If I reload the page, then it will let me upload as expected.
Should I open a new issue for this?
@purplespider I can confirm the same behaviour in my project as well.
My set up is (roughly):
has_many
relationship to a Versioned
DataObject
("Items").has_one
relationship to Image
.GridField
.Result: "You can not upload any more files."
I will leave it to @GuySartorelli to determine if this should be a new Issue?
Please create a new issue and link back to this one
Setup
Description
UploadField
UploadField
Result: "You cannot upload any more files"
https://user-images.githubusercontent.com/505788/233233955-ea414c81-2c88-428e-95f1-098cff40191f.mov
v1
Tested the same behaviour in a Silverstripe 4 project, and did not experience this behaviour.
Acceptance criteria
PRs