nexus2kswiss

+1 can’t create new charts with the latest version. Loading from Google Sheets using CSV import feature…

Well the Chart does get created but it doesn’t seem to update the preview of the chart at all.

• This reply was modified 1 year, 10 months ago by nexus2kswiss.

@mateithemeisle always happy to help. Thanks for your immediate fixing of the reported issues and your great plugin.

So I removed the block that was saying:
This block has encountered an error and cannot be previewed.

And pasted the Shortcode and saved the Page. When viewing the page outside the Editor the Chart does show up (but it also showed up before), but in the Editor it now just shows:

Shortcode:
[visualizer id="1027" lazy="no" class=""]

I do prefer the block behaviour over that where I can edit the chart and select the updated one that I’ve created before in the Visualizer library menu.

Did you maybe only fix the issues for Posts and not for Pages? EDIT: No it seems that wierdly enough inserting a Visualizer Chart block on a brand new Page/Post works w/o issues.

EDIT2: Ok the reproducible behavior is:
Create a new Post, add a Visualizer Block to it. Save the post.
Reload the Editor, the visualizer block now fails to display.

• This reply was modified 3 years, 5 months ago by nexus2kswiss.
• This reply was modified 3 years, 5 months ago by nexus2kswiss.
• This reply was modified 3 years, 5 months ago by nexus2kswiss.

Here’s the output of the Chrome console:

JQMIGRATE: Migrate is installed, version 3.3.2
w.js:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED
loader.js?ver=1.34.0:134  Attempting to load version 'current' of Google Charts, but the previously loaded '49' will be used instead.
Tc @ loader.js?ver=1.34.0:134
w.js:1 Failed to load resource: net::ERR_NAME_NOT_RESOLVED
jsapi_compiled_default_module.js:80 Uncaught TypeError: b.createScript is not a function
    at gvjs_Mf (jsapi_compiled_default_module.js:80)
    at jsapi_compiled_default_module.js:80
jsapi_compiled_default_module.js:82 Uncaught TypeError: b.createScriptURL is not a function
    at gvjs_Sf (jsapi_compiled_default_module.js:82)
    at jsapi_compiled_ui_module.js:294
2react-dom.min.js?ver=16.13.1:125 TypeError: b.vr is not a function
    at gvjs_Q.gvjs_4n (jsapi_compiled_default_module.js:464)
    at new gvjs_Q (jsapi_compiled_default_module.js:479)
    at t.componentDidMount (block.js?ver=3.5.1:64)
    at oj (react-dom.min.js?ver=16.13.1:127)
    at Aj (react-dom.min.js?ver=16.13.1:160)
    at unstable_runWithPriority (react.min.js?ver=16.13.1:25)
    at Da (react-dom.min.js?ver=16.13.1:60)
    at ab (react-dom.min.js?ver=16.13.1:154)
    at Te (react-dom.min.js?ver=16.13.1:146)
    at react-dom.min.js?ver=16.13.1:61

As said this happens when I’m logged in and try to use the Editor in WordPress to change an existing page/post which has a Visualizer block.

Visualizer: Version 3.5.1
SiteKit: Version 1.34.0

• This reply was modified 3 years, 5 months ago by nexus2kswiss.

I think this broke again. At least in the editor I can’t see the Visualizer block. When viewing the page it works. When editing it it turns to “this block caused an error”.
I see the same console log errors.

Google SiteKit also got upgraded to 1.33.0. When disabling it, it works.

Looks like the issue is caused by having the “Google Site Kit” Plugin installed, it does load it’s own version of charts/loader.js. Disabling it gives me back the ability to edit charts within the Post editor.

Looks like it’s fixed now. There was also a Yoast SEO update on 4th of March. So I assume that fixed the issue.

Visualizer Plugin: Version 3.4.11
Yoast SEO Plugin: Version 15.9.1

• This reply was modified 3 years, 8 months ago by nexus2kswiss.