Visualizer charts not showing when logged in to WordPress

@nswm ,

Looks like they have fixed the conflict but wouldn’t know until they do an official release. I would wait until there is a formal update released.

Thanks, @dshakya. Will do. Let’s hope so.

Looks like good news. Site Kit updated to 1.33.0 and Visualizer to 3.5.1 today. It seems that the latter (or combination of both updates) has resolved this issue.

I left the SiteKit to 1.32.0 and updated the Visualizer to 3.5.1. The chart shows when logged in as well. So yes, it works with the update. Thanks Devs!! Updated Sitekit and it still works!

• This reply was modified 3 years, 6 months ago by dshakya.

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.

Hello @nexus2kswiss ,

Thank you for using our products!

I have tried installing google site kit and visualizer on my machine to replicate the error but for me it worked correctly, which makes me think there might be a particular case here.

Would you mind sharing the URL affected by this issue and provide some screenshots of the way the situation is looking on your end so we can further investigate?

Thank you and have an amazing day!

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.

Hello @nexus2kswiss ,

We are sorry for the delayed response.

Seems like the conflict appeared again based on the log you posted here.

We are investigating the issue and will let you know as soon as we have an answer for it!

Thank you for your understanding!

Hello @nexus2kswiss ,

I hope you are having a good day!

We are still investigating but I wanted to ask you if you can add the chart through shortcode instead of the block option. In my test instance, this worked.

To do this you need to go to Dashboard -> Visualizer Chart Library -> Click the small scissors in the bottom left corner of the Chart to copy the shortcode.
https://d.pr/yn5esL

Then go to the page you want to display it -> Edit Page and Paste the shortcode there -> Update and see if it appears.

Please let us know if this worked for you!

Thank you and have an amazing day!

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.

Hello @nexus2kswiss ,

Thank you for doing such a great job in detailing your specific issue. It helped us replicate it thus our developer team managed to fix it.

This fix will be coming with the next update along with other fixes too, thus please stay tuned!

Thank you again for your contribution and for helping us improve our products so that ultimately our users enjoy the best experience!

Have an amazing day!

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