Luke Carbis

@durmonski That is concerning! It looks like there’s a typo in the include path you pasted in your error message. I checked out code repo, even the history of the file in question, and that type has never existed in our codebase!

Can you past lines 73—78 of the file genesis-blocks/lib/BlockLoader/ManualRequire.php here please?

The error message you pasted has the word “excepthons” which should be “exceptions”. Changing this should fix the problem, but I wanted to also check nothing else was effected.

Hi @personalchemist –?thanks for getting in touch!

The columns in Genesis Blocks (when using three columns) are designed to show up side-by-side up until the browser width is 600px wide. At that point, they responsively reorganise to be stacked, instead.

Unfortunately, on your site, the content at 800px wide, is very squashed due to the sidebar there! The theme that you’re using (“enfold”) is setup to move the sidebar out of the way at 767px, which frees up some room for column content.

So…?the best way of solving this issue on tablet devices would be to either:

– Change the breakpoint of Genesis Blocks columns so that they stack much wider
– Change the breakpoint of the theme’s sidebar so that it moves at wider browser widths

My personal opinion is that you should go with the second option… the sidebar looks pretty squished at smaller widths. Your theme might have a setting for this…?in which case, use that! I suggest 989px (this is when your theme changes the menu navigation to a hamburger menu).

Otherwise, you could achieve this with some custom CSS.

As you can probably tell…?every theme works a little differently, and unfortunately it’s not really possible to make sure Genesis Blocks works perfectly in every situation.

I hope some of this is helpful!

Luke

@stinkykong Thanks for bringing this up! Often times matching between the editor view and the frontend view can be quite hard, difficult to debug, and often simply out of our hands. Here’s why:

When you load the editor, the theme has the option of loading “editor styles”, styles which the theme chooses to match the frontend. Some themes do this well (see Twenty Nineteen) and others don’t.

Container widths are often one of the styles that don’t get properly included by the theme in editor styles, since the theme will often focus more on typography and colours.

Additionally, themes can sometimes override the Genesis styles on the frontend (or even in the editor), causing a mismatch between the editor and preview.

If you’re noticing this as a specific replicable problem across multiple themes, then I can action this further. My next step would be to try to replicate the issue –?so I would need the steps that you went through to create the specific blocks, included (as you helpfully included above) the expected result and the actual result.

Thanks!

@tussharctg I wrote that it’s in the wrong directory because the error you pasted specified:
home3/slippysl/public_html/wp-contnet/plugins/genesis-block

When it should be:
home3/slippysl/public_html/<strong>wp-content</strong>/plugins/genesis-block<strong>s</strong>.

Version 1.2.1 is the latest and either PHP 7 or 7.4 should work fine.

It’s a very strange error that you’re receiving as it indicates a code problem that I haven’t seen elsewhere, and should be effecting everyone.

Could you please try the following?

Open the following file:
/home3/slippysl/public_html/wp-content/plugins/genesis-blocks/lib/BlockLoader/Module.php

In that file at the top (line 14) is a line that reads:
declare(strict_types=1);

Could you try deleting that?

Additionally, could you please paste your Site Info from Tools > Site Health in your WP Admin?

I see that hand. ??

Just wanted to add that I’ve just submitted a fix for this issue (it was only a small change), so once we get it through code review, you should see this fixed in the next Genesis Blocks release. Thanks again!

Ah! That is absolutely a bug. I’ll report it to the team, and try to get a fix in the next release. Thank you!

@jimwalczak Is Genesis Blocks active on all sites on the multisite? Or is it only active on one, and you’re still seeing FA enqueued on all other sites?

@tussharctg Where did you get your copy of Genesis Blocks? From www.remarpro.com? Could you try uninstalling it and reinstalling the latest version, as it looks like it’s installed in the wrong directory.

@brody182 Genesis Blocks doesn’t include a block that can do this, sorry.

You’re welcome!

Hi @jonhenshaw –?those top two block templates look good to me. However, block_field doesn’t work inside of single.php, or any theme template (even if you’re inside of the loop, as I presume you are in the example).

The main reason is because there’s no way for block_field to know which block you’re referring to. Even if there were a parameter for block_field to define the particular block template you’re trying to get (e.g. block_field( 'name', true, 'newsletter' )), it’s still possible you might have inserted multiple copies of that block in your post / page.

The only way of using block_field() or block_value() is inside the block template, which will be output when you use get_the_content() or the_content() in your single.php template.

I hope that all makes sense!

@jonhenshaw Could you please post your template code?

Hey @masselyn and @stinkykong –?this is a known bug in Gutenberg right now. It’s being tracked over here: https://github.com/WordPress/gutenberg/issues/26421

@la_ri_za Right now, the Atomic Block Theme is being maintained for security vulnerabilities and critical bugs, but we’re not currently planning any major updates or new features.

Genesis Blocks works great with the Atomic Block Theme –?you can feel free to migrate. Please remember to take a backup first or running the process on staging before your production site.