Skip to toolbar

Find answers, ask questions, and connect with our
community around the world.

Forums Forums Bug Reports HowTo schema errors

  • HowTo schema errors

     Jim updated 1 month ago 2 Members · 6 Posts
  • Jim

    August 13, 2020 at 3:38 am

    I tried adding a HowTo block and after testing it at Google’s Structured Data Tool I find it have schema errors. Google fails to recognize the schema due to this problem. I get:

    JSON-LD	   Missing '}' or object member name.

    I narrowed it down to the Required tools section. Without it, no errors. Once I add it and include one tool, it causes the error.

    I can add the tools section but without any tools, getting this in the output:

    "tool": []

    Once I add a tool, I get this:

    "tool": [{"@type": "HowToTool", "name": "Test",}]

    The problem is the surious comma after the last (and only) item. You see it after “Test” above.

    Unfortunately, this problem is pretty serious. If Google can’t parse the schema, it doesn’t make sense to bother trying to add it.

  • Alexis

    August 13, 2020 at 10:34 pm

    Hi @Jim ! Thanks for letting us know. We’re now working on fixing this issue. We’ll let you know when the fix is available.

  • Alexis

    August 18, 2020 at 12:47 pm

    Hi @Jim !

    We’ve released a fix for this issue in our latest update. Please upgrade to the latest version.

  • Jim

    August 18, 2020 at 3:40 pm

    I’m still getting errors. All I do is add one tool. Then test it at

    I get JSON errors.

    • Alexis

      August 19, 2020 at 9:05 am

      Sorry about that. We made another fix just for you that would hopefully resolve this issue.

      Please download this file and save it as “block.php”. Then, navigate to your site’s plugin folder, go to ultimate-blocks/src/blocks/how-to, rename the block.php file there (so that you could easily restore it in case this one fails), and copy the file you just downloaded.

      Please let us know how it goes. If you don’t experience further issues after going through the provided steps, we’ll include the fix in our next release.

  • Jim

    August 19, 2020 at 4:35 pm

    The new file has resolved the error.

Log in to reply.

Original Post
0 of 0 posts June 2018