Kevin Antonio Rateni Iatauro

I can confirm this on 4.3.2. Looks like the values are properly set in the database, but the service is not returning them to the admin panel. Setting both `category`...

Requests with the `email` parameter set to `null` or with a payload that does not contain `email` at all work as expected. Do you think there are any advantages in...

> While I understand what you were intending to do, I think this as is would be a breaking change and instead all providers simply should have the verifysize function...

Moving the check to the `provider` service is okay with me. The only thing I'd like to point out is that we still need to decouple the parameter from the...

Cool, I'll wait for Pierre's feedback then and integrate all the changes at once. Thank you very much for the help Marc!

Instead of changing the `init` method of every provider, what if I turned this: https://github.com/strapi/strapi/blob/840391f541f442e09260e7a2972a6953a7857571/packages/core/upload/server/register.js#L45 Into this: ```js const providerInstance = provider.init(_.omit(providerOptions, 'sizeLimit')); ``` This way, we'd be sure we...

Made the changes, let me know what you think!

I tested with S3, Cloudinary and [Aliyun OSS](https://market.strapi.io/providers/strapi-provider-upload-oss) and all three seem to be okay with unsupported keys being passed in the config object. Any other provider we should test?

Hey @alexandrebodin! - Is there a way to define register/bootstrap functions for providers like you would do for a plugin? If so, we could simply inject a default value for...

Maybe instead of removing the README.md file we could simply rework it so that it no longer references the extensions system? Also, not super high prio, but I think the...