Are you a GenerateCustomer?

Do you have an active GP Premium or GenerateBlocks Pro license key?

Create a GenerateSupport account for GeneratePress and GenerateBlocks support in one dedicated place.

Create an account
Already have a GenerateSupport account? Login

Just browsing?

Feel free to browse the forums. Support for our free versions is provided on WordPress.org (GeneratePress, GenerateBlocks).

Want to become a premium user? Learn more below.

New containers not appearing; block contains unexpected or invalid content

  • I seem to be having two related errors since the latest WP update. I have tried clearing all caches and deactivating all themes and plugins, but the issue persists with only GeneratePress and/or GenerateBlocks activated.

    The first issue is that I have been trying to copy and paste content blocks from working pages into other pages, and frequently get the following error: Block contains unexpected or invalid content. I have attempted recovery on each block and saved the page only to have it revert to the “Block contains unexpected or invalid content” on all the previously fixed blocks.

    A possible clue as to what may be happening lies in the second error. I copied the content of a known good page into a new page. The page has a container at the top with a custom class to float the container to the right. It does this correctly on the original page. After saving on the new page, when I look at the source code I don’t even see a container element at all. When I go back in to edit the new page, I see multiple “Block contains unexpected or invalid content” errors.

    I’ve tried creating a simple container block from scratch on a test page and it doesn’t show up in the source code, either.

    Containers DO render properly in all my older posts and pages. It seems only to affect new or copied containers.

  • Hi there,

    Would you be able to create a staging site based on the live site? We need to perform deeper troubleshooting, but doing it directly on the live site could be risky and may cause unintended issues.

  • Hi, I will work on this but it may take me a bit. Before I do, though, would it be worth my attempting to completely remove and reinstall GeneratePress and GenerateBlocks?

  • Removing/reinstalling the plugins would help only if the files are corrupted. You can give it a try.

    Since your site has lots of plugins and it is a live site, please create a staging site so we can do proper debugging.

    Thanks!

  • Staging site has been created and login credentials appended to the private info box. Thank you!

  • On the staging site, I have deactivated all plugins except GP Premium, GenerateBlocks, and GenerateBlocks Pro.

    On the /test2 page, I edited the content, saved the changes, and then checked it on the frontend. The Container is now displaying correctly as expected.

    This indicates that one of the plugins on your site is causing the conflict. You will need to reactivate the plugins one by one to identify which one is responsible for the issue.

  • I re-enabled all plugins on the test site and, like you, initially got no errors anywhere. BUT I kept copying and pasting blocks from known good pages into test pages (generally about 10-15 tries) and eventually the unexpected/invalid block error showed up again. The error persisted even after disabling all plugins besides GP/GB and pasting a known good block into an empty page. It was visible in a browser with no history, too, so it wasn’t a local caching issue.

    In my initial testing prior to contacting you, I disabled all plugins on the live site except for GeneratePress/Blocks and got unexpected/invalid block errors when copying from known good pages and pasting into new pages. I also tested it with the default WordPress theme and GB only. Same thing.

    Unfortunately it’s sporadic, so I can’t identify a particular event that precedes it.

  • Can you let me know which page is the “good page” so I can copy the content and paste to a test page?

  • The two ‘good’ pages that I’ve been using are:

    /join-ahvma/ and /journal/ldsv1224/

    Chosen only because those were the two I was using when I first encountered the issue.

  • With all other plugins deactivated, I copied all content from /join-ahvma/ and pasted it to /test3/, published the page, refreshed the page, and still don’t see the issue.

    I repeated the pasting process after enablling each of the plugins, and found out that the last plugin, named WP File Access Manager by ThemeNcode is the cause.

    Please check.

  • I tried to replicate the error with only GB/GP and WP File Access Manager by ThemeNcode enabled and was unable to do so.

    When I did my original test, I started at the bottom of the list of plugins and worked my way up (I suspect the reverse of what you did), and for a while thought that Code Snippets must surely be the culprit because that’s when I first saw the error. But I was unable to replicate it with just GB/GP and Code Snippets enabled. To make matters worse, the error sometimes persists for a while with ONLY GB/GP enabled… possibly due to some server side caching over which I have no control? I’m not sure.

    I’m at a loss as to how to nail down which plugin is causing the conflict, since it is so inconsistent and I also saw it happen with only GB/GP enabled. The only commonality I’m certain of is GB, since I saw it fail with the default WordPress theme, too. I think I will try completely uninstalling both GB/GP and then reinstalling, unless you have any other suggestions.

  • The only commonality I’m certain of is GB, since I saw it fail with the default WordPress theme, too

    It’s simply not possible.

    As if this issue is a GB issue, we would have received lots of reports already, and none of our team members can replicate the issue on our sites, so it has to be a local issue on your site only.

    Can you keep WP File Access Manager by ThemeNcode plugin disabled, and try to replicate this issue again?

    Let me know 🙂

  • That’s exactly my point, though, that there may be something wrong with my installation. Hence why I think completely removing and reinstalling it would be a good idea.

    And it failed with WP File Access Manager by ThemeNcode disabled.

  • I did see the issue when only the WP File Access Manager by ThemeNcode plugin disabled.

    As soon as I disabled all other plugins, I did not see the issue again.

    I can not replicate the issue when only GB, GB Pro and GP Premium are enabled. Can you make it happen again when only these 3 plugins are enabled? (you can keep the temp login plugin active for us to access the site).

    Let me know 🙂

  • Yes, I was able to replicate it with only those 3 plugins enabled. That’s what happened in my initial troubleshooting (see first message in thread), and I just saw it happen again.

  • I can not replicate it with only 3 plugins enabled. I tried many, many times.

    However, I checked the site health, and there is a critical issue.
    https://app.screencast.com/RiH4FhrZyDHio

    An autoload problem in wp_options can directly cause Gutenberg / block editor rendering failures.

    Can you check with your host to fix this issue first?

Viewing 16 posts - 1 through 16 (of 22 total)
  • You must be logged in to reply to this topic.