Support » Plugin: Prismatic » Prismatic breaks with double less-than signs

  • Resolved DigitalFormula

    (@digitalformula)


    When using syntax like the example below, Prismatic fails. The symptom of the failure is everything up to the first “<” being rendered properly, but then everything after that failing, therefore breaking the rest of the page.

    
    cat <<EOF | kubectl apply -f -
      # something here
    EOF
    

    This renders as:

    
    cat <
    

    with everything after that jumbled and unreadable.

    Swapping << for &lt;&lt; doesn’t help. The only fix is to not use Prismatic and use the standard WP code block (ugly).

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

    (@specialk)

    Thanks for reporting, I will investigate and try to resolve for the next plugin update.

    Thread Starter DigitalFormula

    (@digitalformula)

    @specialk NP, thanks for acknowledging. Happy to test, if you need it.

    squeegily

    (@squeegily)

    I can’t seem to reproduce this with either Prism or HLJS:

    https://key-cicada.jurassic.ninja/2021/05/17/hello-world/

    Plugin Author Jeff Starr

    (@specialk)

    @squeegily that is useful thank you.

    Plugin Author Jeff Starr

    (@specialk)

    Update: after much investigation, I narrowed down the issue to one thing: the block editor force escapes left-angle brackets and other characters. I’ve tried many different things, ways of adding block elements and so forth, but so far nothing works.

    So, the plan is to ask for help from the WP community. I posted a forum topic here explaining the issue and asking for help. I’m not sure if it’s even possible to achieve. If it is, then Prismatic will continue to provide its own Gutenberg block. If not, then the block will be discontinued.

    If you or anyone 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.

    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 for reporting, @digitalformula.

    Thread Starter DigitalFormula

    (@digitalformula)

    @specialk Brilliant, thank you! I’m glad you got this fixed as losing the Gutenberg block would’ve been a death blow for the plugin (for our org anyway). Thanks again!

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.