-
Notifications
You must be signed in to change notification settings - Fork 2.4k
useUploadHandlers must be used within UploadHandlersProvider. @payloadcms/storage-s3 #11717
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Are all of your payload plugins on the latest version? 3.28.1? What does your package.json file say? |
I uninstalled the s3 plugin and deleted the associated code, yet I'm still encountering this problem on one instance. However, the newly created instance is functioning properly. |
I have the same problem. I'm just following the setup guide. "@payloadcms/db-mongodb": "^3.28.1",
"@payloadcms/next": "^3.28.1",
"@payloadcms/payload-cloud": "^3.28.1",
"@payloadcms/richtext-lexical": "^3.28.1",
"@payloadcms/storage-vercel-blob": "^3.28.1", My config: import { mongooseAdapter } from "@payloadcms/db-mongodb"
import { lexicalEditor } from "@payloadcms/richtext-lexical"
import { vercelBlobStorage } from "@payloadcms/storage-vercel-blob"
import path from "path"
import { buildConfig } from "payload"
import { fileURLToPath } from "url"
import sharp from "sharp"
import { Users } from "./collections/Users"
import { Media } from "./collections/Media"
const filename = fileURLToPath(import.meta.url)
const dirname = path.dirname(filename)
export default buildConfig({
admin: {
user: Users.slug,
importMap: {
baseDir: path.resolve(dirname),
},
},
collections: [Users, Media],
editor: lexicalEditor(),
secret: process.env.PAYLOAD_SECRET || "",
typescript: {
outputFile: path.resolve(dirname, "payload-types.ts"),
},
db: mongooseAdapter({
url: process.env.MONGODB_URI || "",
}),
sharp,
plugins: [
vercelBlobStorage({
collections: {
media: true,
},
token: process.env.BLOB_READ_WRITE_TOKEN || "",
}),
],
}) I'm also seeing TS errors in the payload.config:
|
I went with a separate clean setup and it seemed to work at first until today I run yarn and I see the error again in the clean next.js setup in a turbo repo. |
We were facing this issue but fixed it by downgrading the version number. After inspecting our lockfile, I saw that all of our payload dependencies were on version After setting the following versions manually in package.json, the problem went away:
|
Seems to be an issue when the package manager is |
Any news about this?
|
Try this: cleanup the importMap.js |
@smoothdvd just tried to clean it and regenerating it but sadly I still get the error. |
My package.json:
|
I created a reproduction case: https://github.com/okonet/payload-repro-storage
Most specifically it's this commit: okonet/payload-repro-storage@1d457b2 |
Fixed this issue by setting the identical versions for payload packages:
and adding
My config:
|
I solved this by pinning all payload packages. I had all pinned to |
Unfortunatly we tried to pin all payload packages versions but it did not fix the issue for us.
We use yarn workspaces and we manage our monorepo with turbo.
|
What helped me is to pin-point the dependencies that were deduped / hoisted. Try running Try using |
I had the same issue with Vercel Blob Storage and NPM. I really had to remove all of these:
And that finally did the trick 👍 |
Link to reproduction
No response
Describe the Bug
After a few days, nothing changes in the code that causes this error, but on a new instance on payload cloud s3, everything is operating as it should.
Visit this link and please check the issue
https://documentation-cms.payloadcms.app/admin/login
I have tried @payloadcms/storage-s3 different versions of this plugin.
Without using this plugin I can see my payload UI.
To Reproduce
After a few days just triggered a redeploy, nothing changes in the code that causes this error, but on a new instance on payload cloud s3, everything is operating as it should.
Payload Version
latest
Adapters and Plugins
@payloadcms/storage-s3
The text was updated successfully, but these errors were encountered: