whywaitwebs

Hi,
I have that option enabled already I’m afraid

It actually seems to be something I did in my theme. Very odd, especially given that it only happens when those particular blocks are present…

Anyway, sorry to bug you here about what turns out to be a theme issue.

Edit: It had to do with using the “true” argument for strip_teaser in the_content (the_content(null, true)).

• This reply was modified 5 years, 7 months ago by whywaitwebs.

Hi there, thanks for your response!
So for starters, yes there was no HTML generated and there were no JS errors, just a few warnings.

I uncovered that this happens with the default latest post block as well, so it’s probably not your issue.

Also found out it only happens on pages with a more or page break block existing on the page.

Reality deniers gonna deny

It has been released into the public on the most used web platform in the world. It deserves the rating it earns *now* not one based on its theoretical potential. If it has such potential, why didn’t they wait until it reached it? By releasing, they claimed it was ready. It clearly is not ready for any production use.

It’s a joke that there isn’t a basic container block as a part of Gutenberg. I’m just… I don’t understand how a project this big is this bad. Surely you guys see all the dire, ridiculous, absurd maintainability issues with ALL of the suggested solutions here.

• This reply was modified 5 years, 7 months ago by whywaitwebs.

What are you talking about? You can import and export sites. You can 100% use it for migrating without paying as long as your site is not too big (and even then they provide instructions to raise your own limits manually if you don’t want to pay for the pro plugin).

• This reply was modified 5 years, 7 months ago by whywaitwebs.

I haven’t encountered that limitation at all. I have been moving things up and down from local domains to live domains on the free version with no issues.