• ResolvedPlugin Author Jeff Starr

    (@specialk)


    Hello!

    For anyone using the Prismatic block, there is a known bug in version 2.8 of the plugin. The bug affects only the Prismatic block and nothing else. So if you don’t use the Prismatic block, then you have nothing to worry about and can stop reading here.

    If you do use the Prismatic block, you can either roll back to Prismatic version 2.7, or just use the standard code block instead. When adding code snippets via the standard code block, you have to manually add the language class just FYI.

    At this time, I am not sure if there is a solution to the Prismatic block issue, due to how Gutenberg Block Editor always escapes any left-angled brackets and ampersands. I posted about this with more detail here for anyone interested and/or able to help.

    So at this time, the plan is to ask for help from the WP community. If a solution is found, then Prismatic will continue to provide its own Gutenberg block. If not, like if there is some intrinsic limitation to how code can be added via Gutenberg, then the block will be discontinued.

    Lastly, if anyone reading has insight on how to add code snippets *raw* unescaped into a block, please let me know. Check the above-linked support topic for more details. Thank you.

Viewing 1 replies (of 1 total)
  • Plugin Author Jeff Starr

    (@specialk)

    Update!

    Finally figured it out, it was an issue with the render callback function.

    So that means Prismatic will continue to provide the same blocks as before, only without the weird code-escaping bug.

    Thanks to everyone who shared ideas and feedback regarding this issue.

    Cheers!

Viewing 1 replies (of 1 total)
  • The topic ‘2.8 Bug – Please Read’ is closed to new replies.