[Bug] Cannot open Signed UploadWidget #158
Labels
Kommentare
|
hey thanks for the bug report. turns out it wasn't quite a bug, i was missing my api key on the docs deployment 🤦 that said i did have an optional chaining fix to the right spot to avoid the error you were seeing and added a warning for people like me who forgot to add that :) not sure if you're just reporting this from the docs or from your own usage but that should address the issue, let me know if you're seeing anything else after it's merged/deployed |
colbyfayock
added a commit
that referenced
this issue
Mar 22, 2023
# Description Minor changes to help avoid errors with the Signed upload widget: * fixed optional chaining to make sense for method invocation on a ref * Added a warning for missing API Key ## Issue Ticket Number Fixes #158 <!-- Specify above which issue this fixes by referencing the issue number (`#<ISSUE_NUMBER>`) or issue URL. --> <!-- Example: Fixes https://github.com/colbyfayock/next-cloudinary/issues/<ISSUE_NUMBER> --> ## Type of change <!-- Please select all options that are applicable. --> - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] Fix or improve the documentation - [ ] This change requires a documentation update # Checklist <!-- These must all be followed and checked. --> - [ ] I have followed the contributing guidelines of this project as mentioned in [CONTRIBUTING.md](/CONTRIBUTING.md) - [ ] I have created an [issue](https://github.com/colbyfayock/next-cloudinary/issues) ticket for this PR - [ ] I have checked to ensure there aren't other open [Pull Requests](https://github.com/colbyfayock/next-cloudinary/pulls) for the same update/change? - [ ] I have performed a self-review of my own code - [ ] I have run tests locally to ensure they all pass - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes needed to the documentation
|
🎉 This issue has been resolved in version 4.0.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This issue has been resolved in version 4.0.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
cham74
added a commit
to cham74/next-image-delivery
that referenced
this issue
Dec 23, 2023
## [4.0.1](cloudinary-community/next-cloudinary@v4.0.0...v4.0.1) (2023-03-22) ### Bug Fixes * Help reduce Signed Upload errors ([#160](cloudinary-community/next-cloudinary#160)) ([d323e33](cloudinary-community/next-cloudinary@d323e33)), closes [#158](cloudinary-community/next-cloudinary#158)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Describe the bug
When clicking on the button to open the UploadWidget, nothing happens and an error triggers :
p.current.open is not a functionIs this a regression?
I don't know, this is my first time using this package
Steps To Reproduce the error
<CldUploadWidget />component, just like mentioned in the documentationExpected behaviour
CodeSandbox or Live Example of Bug
The bug is actually present on the official documentation page :
https://next-cloudinary.spacejelly.dev/components/clduploadwidget/examples
Screenshot or Video Recording
Your environment
The text was updated successfully, but these errors were encountered: