Skip to content
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

Non-blocking Error shown in console when uploading images to galleries #1318

Closed
4 tasks
chriskmnds opened this issue Jan 30, 2020 · 3 comments
Closed
4 tasks
Labels
[Status] Needs Info Tracking issues with follow-up required in order to be actionable

Comments

@chriskmnds
Copy link
Contributor

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:

  1. Insert a new Gallery (Offset, Masonry, or Stacked).
  2. Click on "Upload" at the bottom - should upload image as expected.
  3. See error in console.

Screenshots
If applicable, add screenshots to help explain your problem.

Kapture 2020-01-30 at 13 05 02

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

@EvanHerman
Copy link
Contributor

I am not seeing this issue running CoBlocks 1.2.0 in Chrome. Can someone else test and confirm this is a bug in CoBlocks?

@richtabor richtabor added the [Status] Needs Info Tracking issues with follow-up required in order to be actionable label Feb 10, 2020
@richtabor
Copy link
Contributor

I'm also unable to replicate this - @chriskmnds are you still seeing the issue?

@AnthonyLedesma
Copy link
Member

This issue is no longer present in CoBlocks 2.9.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Status] Needs Info Tracking issues with follow-up required in order to be actionable
Projects
None yet
Development

No branches or pull requests

4 participants