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

Geo chart throws error only in Gutenberg Editor #770

Closed
irinelenache opened this issue Sep 30, 2020 · 2 comments · Fixed by #1081
Closed

Geo chart throws error only in Gutenberg Editor #770

irinelenache opened this issue Sep 30, 2020 · 2 comments · Fixed by #1081
Assignees
Labels
bug This label could be used to identify issues that are caused by a defect in the product. large (1-2d) - This label is used for issues that can be completed within 2 days or less. Priority-Low Expected resolution time - up to 3 months.

Comments

@irinelenache
Copy link

Description:

Geo chart throws an error in gutenberg editor, before and after selecting it to be added, but it works fine in front-end.
May be related to #675

How to reproduce:

  1. Create a Geo chart.
  2. Add it on a post.
  3. Check changes in editor and front-end.

Expected behaviour:

The chart should load in editor.

Current behaviour:

The chart works only on front-end.

Reference:

https://www.loom.com/share/09ee8550cfac4b5fa3d908f6d01473d0

Technical info

  • WordPress version: 5.5.1
  • Plugin version: 3.4.8
@mghenciu
Copy link
Contributor

mghenciu commented Feb 8, 2024

There is still an issue with the Geo Chart with the latest versions, @vytisbulkevicius , when used with Gutenberg.

In the example below:

  • I've create the Default Geo chart
  • added it to a Post and Page via the shortcode
  • using the shortcode works for the Pages, but not for the Posts
  • using the Visualizer Block won't work in both Pages & Posts
Screen.Recording.2024-02-08.at.10.26.31.mov

Visualizer Free 3.10.7
Visuzalier Pro 1.13.3
WP 6.4.3

@vytisbulkevicius vytisbulkevicius added bug This label could be used to identify issues that are caused by a defect in the product. Priority-Low Expected resolution time - up to 3 months. labels Feb 8, 2024
@vytisbulkevicius
Copy link
Contributor

Thanks @mghenciu, the thing that it doesn't work on Posts looks to be an isolated case for TasteWP instances. On other servers it works added to Posts as well (using both ways), the only issue that exists is that it throws the error when added via Gutenberg editor.

@Soare-Robert-Daniel Soare-Robert-Daniel added the large (1-2d) - This label is used for issues that can be completed within 2 days or less. label Feb 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This label could be used to identify issues that are caused by a defect in the product. large (1-2d) - This label is used for issues that can be completed within 2 days or less. Priority-Low Expected resolution time - up to 3 months.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants