You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An Unhandled Promise Rejection Error is shown in the console when uploading images to the Offset, Masonry, and Stacked galleries. This happens on CoBlocks version 1.20.1.
This is a non-blocking error, since the images are uploaded as expected. The Error is shown only on the first upload - it seems to be cleared on consecutive ones.
Tested in Chrome & Safari.
To Reproduce
Steps to reproduce the behavior:
Insert a new Gallery (Offset, Masonry, or Stacked).
Click on "Upload" at the bottom - should upload image as expected.
See error in console.
Screenshots
If applicable, add screenshots to help explain your problem.
Isolating the problem:
Mark completed items with an [x].
This bug happens with no other plugins activated
This bug happens with a default WordPress theme active
This bug happens without the Gutenberg plugin active
I can reproduce this bug consistently using the steps above
WordPress Version
What version of WordPress are you using?
5.4 Gutenberg Version
What version of the Gutenberg plugin are you using? (If any)
7.3.0
The text was updated successfully, but these errors were encountered:
Describe the bug
An Unhandled Promise Rejection Error is shown in the console when uploading images to the Offset, Masonry, and Stacked galleries. This happens on CoBlocks version
1.20.1
.This is a non-blocking error, since the images are uploaded as expected. The Error is shown only on the first upload - it seems to be cleared on consecutive ones.
Tested in Chrome & Safari.
To Reproduce
Steps to reproduce the behavior:
Screenshots
If applicable, add screenshots to help explain your problem.
Isolating the problem:
Mark completed items with an [x].
WordPress Version
What version of WordPress are you using?
5.4
Gutenberg Version
What version of the Gutenberg plugin are you using? (If any)
7.3.0
The text was updated successfully, but these errors were encountered: