Closed aaronclimbs closed 2 years ago
Sorry, yeah the versioning isn't converged with strapi, I upgraded to v4.0.0 because of changes for the AWS SDK used. I haven't found the time to experiment with strapi v4 properly yet, what I've seen from it is that they changed their entire API regarding plugins without providing stable documentation (at least this was the case 2 weeks ago).
Thank you for the pull request, will merge this as soon as I have created a strapi v4 playground.
No problem - I just wanted you to know that it worked with the current code without going through their plugin migration guide tutorial using codemods and lots of manual checks. The only changes I needed to get it working are those listed in the PR. Hopefully that makes it easier once you get that playground set up.
Thanks for your work on this!
I will go ahead and bump the package version as soon as your changes make it to the main branch 👍
I can't tell from the README/versioning if this is expected to work with the most recent version of Strapi, but when I've set this up as below, it doesn't seem as though Strapi is even recognizing the plugin:
I've changed the env variables to ones that do not exist and no errors are thrown, which leads me to believe that the config itself is not being read by strapi.
When I added a
config: {... }
wrapper around everything within theupload
block, so that I could putenabled: true
in the upper blockit did throw the below: