Support » Plugin: Kadence Blocks – Gutenberg Page Builder Toolkit » Row Layout invalid content errors

  • Rick

    (@murlyn)


    When I create Row Layout blocks, I then save, then when I come back to edit the page I get this error “This block contains unexpected or invalid content.” and the only options I have are “Resolve” and “Convert to HTML” and then I have to redo everything. I can click on the three dots and convert to classic block and things seem to be ok, but same thing again when I refresh the edit page. The block content starts with a shortcode.. so Im not sure if that is causing issues.

Viewing 8 replies - 1 through 8 (of 8 total)
  • Aveias

    (@aveias)

    I have exactly the same issue, my content is in several blocks in a row layout. When I go on the edit page, all blocks are hided, only one block is showing β€œThis block contains unexpected or invalid content.”, and if I do anything (resolve, convert to HTML or classic), I lose all my blocks and get only the last one, containing a shortcode.
    In looking at the revisions, I saw that the “uniqueID” seems to change when the bloc show this errors.

    [EDIT] After a few investigations, this error seems to appear repeatedly when adding a shortcode in a classic block. In using a shortcode block, it seems to be OK (for now).

    • This reply was modified 1 year ago by Aveias.
    Rick

    (@murlyn)

    What is the proper way of using a shortcode, especially one that has a start and end block, like [box][/box] with HTML and formatting in between that shortcode? The regular shortcode block doesn’t allow for formatting and if the classic block and the row layout is having issues with it.. how do you get around it?

    Plugin Author Ben Ritner – Kadence WP

    (@britner)

    Hey,
    Thanks for posting, I’m not having this happen to me when I test. Could you tell me what version of WordPress and Kadence Blocks you are using? Any other variables I should know about to recreate?

    I tried with one and multiple shortcodes in the classic editor block.

    Ben

    Kevin

    (@jx-3p)

    Can you share exactly what you’re placing within the shortcode block so that I can test on my site?

    -Kevin

    Rick

    (@murlyn)

    It’s a theme specific shortcode, but here you go:

    [box]Just a whole bunch of stuff[/box]

    Now I think I might see the problem and it might not be a row layout issue. I looked at the code and there will be improperly nested code:

    <div kadence inner column><p>[box]Just a whole bunch of stuff</p><p>another test[/box]</p></div>

    so basically parsed

    <div kadence inner-col><p><div box>whole bunch of stuff</p><p>more stuff</div></p></div>

    So hmm.. yeah it looks like it’s not going to like this at all… and from what I can tell it’s a theme shortcode issue not really made for this new version of WordPress. I was converting the page to use blocks, which was fine and then row layout is just what highlighted that there was an issue.. Im not going to close this issue as resolved since there are other people having similar problems.. might even be the same.. Ill continue monitoring though πŸ™‚

    Plugin Author Ben Ritner – Kadence WP

    (@britner)

    Thanks for posting,

    If your shortcode is adding posts using something like the_excerpt then it’s a known issue: https://github.com/WordPress/gutenberg/issues/12530

    Let me know if you discover anything further.

    Ben

    Rick

    (@murlyn)

    No nothing like that, it just adds a div around the content:

    [box]This is the shortcode[/box]
    <div class="box shortcode-box">This is the parsed shortcode</div>

    So if the content is this:

    [box]This is the shortcode
    
    Yep this is what it is.[/box]

    Then it renders as this:

    <p><div class="box shortcode-box">This is the shortcode</p>
    
    <p>Yep this is what it is.</div></p>

    Which isn’t nested correctly.. this is my running theory at this point πŸ™‚

    Plugin Author Ben Ritner – Kadence WP

    (@britner)

    yeah, it’s possible that shortcode is running autowrap on the content which in Gutenberg would break things.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Row Layout invalid content errors’ is closed to new replies.