Skip Navigation

[Resolved] Getting constantly errors in the editor side as "invalid Json"

This support ticket is created 2 years, 9 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Hong_Kong (GMT+08:00)

This topic contains 2 replies, has 2 voices.

Last updated by sergioC-13 2 years, 9 months ago.

Assisted by: Luo Yang.

Author
Posts
#2493463

Hello Luo Yang and tahks for your response.
I saw the test-site and as you made it, i know, should be the correct way to do what im doing on production. The problem is the theme in used and all the content uses Bakery and they have dissabled the bloxk editor. thats becouse i had to create a toolset-> content-template for each lang section in the pubblishing page.
The content-template i've created uses the editor blocks and then i call that template in a bakery text-editor block.
Yesterday i have a workaround for my issue and is simply create a template for each one without translation. Its odd but it works.
By the other hand im getting constantly errors in the editor side as "invalid Json":
(-- /wp-json/ToolsetBlocks/Rest/API/v1/ShortcodeRender?_locale=user:1 Failed to load resource: the server responded with a status of 520 () --).
I dont know if it has to do with my problem or not. If does not, you can close this ticket.
I really appreciate the time you have spent on this discussion.
Thank you

#2493503

Hello,

There is some known issue with latest version of WordPress 6.1, see our erratum:
https://toolset.com/errata/fields-and-text-block-broken-with-wordpress-6-1-update/
If you are using WP 6.1, please to downgrade to 6.0.3, and test again.

#2493731

My issue is resolved now. Thank you!