• Resolved mradzikowski

    (@mradzikowski)


    An <<EOF string breaks the display, code ends there and HTML tags are left unclosed.

    
    cat <<EOF
    echo "123"
    EOF
    
Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Jeff Starr

    (@specialk)

    Thanks for reporting. Are you using Prism.js or Highlight.js? And which attributes are you adding the pre/code tags, so I can replicate the issue locally.

    Thread Starter mradzikowski

    (@mradzikowski)

    Prism.js, with enable numbers option. Class language-bash.
    Link to my page with issue: https://betterdev.blog/minimal-safe-bash-script-template/ (I modified the code so it does not break).

    Thank you!

    Plugin Author Jeff Starr

    (@specialk)

    Thanks, also is the line numbers option required to replicate the issue? I.e., does the issue persist even when line numbers are not enabled?

    Thread Starter mradzikowski

    (@mradzikowski)

    No, sorry, just wanted to list the config I have. So nothing special, I think everything else is set to defaults.

    Plugin Author Jeff Starr

    (@specialk)

    Alright thanks, will check it and try to resolve any issue for the next plugin update.

    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, @mradzikowski.

    Thread Starter mradzikowski

    (@mradzikowski)

    Thank you for such persistence to find and fix this!

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘2.8 breaks on <<EOF’ is closed to new replies.