Not so much of a bug but a heads up for others that may encounter this issue, and maybe one for @patrick to comment on…?
We had an issue for a while that was really hard to figure out using the S3 Provider, specificlly the naming of the Provider, see below (example name):
dave_files
Resulted in all types of problems whereby the S3 Connector would show as an unknown module after saving, testing, getting an unknown or non existent directory or module error…
An hour or two of playing around and we got to renaming the S3 Provider to (example name):
davefiles
And miraculously all errors disappeared, and when we went back to the Server Action the S3 Provider stopped producing the unknown module error…
So it appears using _ in your S3 Provider name is a NO NO!
Weird one and as I mentioned a terrible one for debugging the perpetrator! So I hope this may help anybody else who gets a weird error or their S3 Provider goes Pete Tong in their Server Action.
