-
Notifications
You must be signed in to change notification settings - Fork 6
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
Payload 3.0 #250
Comments
hey @codercatdev , thanks for reaching out. |
When will support for v3 be available? Could you please expedite this process? Cloudinary is one of the most important cloud storage solutions for us. @finkinfridom |
Hey @MoYoussef05 payload 3.0 is still in a beta version and from what I can see from their releases, they have several bug fixes and breaking changes. Honestly, branching the current repository and keeping both the 2.x (still the official version) and the upcoming 3.x could be hard as I'm the only developer for this project. But, if you really need it feel free to create a pull request and I'll review it Thanks |
Could you please clarify if the current version of the plugin is functional with payload beta? Additionally, I would appreciate guidance on how to add the credentials, as the instructions provided are unclear. @finkinfridom |
Adding the credentials to .env as you normally would with the Cloudinary npm package is enough to set the credentials. |
fyi, I started working on the integration for payload 3.0.0-beta |
Looking forward to your update! @finkinfridom |
Is this compatible with payload 3.0 yet? |
As far as I know, none of the previous plugins I used with payload v2 works
on payload v3 especially due to some import related issues.
…On Fri, 6 Dec 2024 at 09:57, Amit Sarker ***@***.***> wrote:
Is this compatible with payload 3.0 yet?
—
Reply to this email directly, view it on GitHub
<#250 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALPQKIAF35KT4DYK3ZU25SD2EFRIJAVCNFSM6AAAAABIDVBXKWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRSGU2TINJYG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
it's working from my side in v3 |
Great! I might find some time to check it out. |
Add support
The text was updated successfully, but these errors were encountered: