Ryan Kienstra

Thanks so much! It’s a big compliment you’re using Genesis Custom Blocks.

Hi @najram,

Sorry, we aren’t planning a change to this, though it definitely could be better.

There has to be some escaping of the template for security reasons.

We could loosen the escaping to help you.

But to be honest, we’re not focusing on this plugin. So unfortunately, we won’t have the developer time for that.

Sorry to not help you, as you raise a good point.

• This reply was modified 11 months, 1 week ago by Ryan Kienstra.
• This reply was modified 11 months, 1 week ago by Ryan Kienstra.

Hi @script2see,

Sorry for the long delay.

Yes, if you manually review the patterns files that Pattern Manager generates, it’s fine to use those pattern files in production.

Pattern Manager doesn’t have to be active in order to use the files it generates.

So its beta status shouldn’t be a blocker, as long as you manually review the files it generates.

Hi @andreslav,

Thanks, that is strange that you can still duplicate fields in Inner Blocks.

Unfortunately, we’re not planning on fixing that.

Hi @andreslav,

Thanks, that’s a good idea.

Unfortunately, we’re not adding new fields types to the plugin anymore.

Hi @andreslav,

Thanks for letting me know about that. Unfortunately, we don’t have plans to make relative URLs valid.

Making that URL field a text field will prevent it from being invalid, but maybe that’s not what you’d like.

Hi @reasondr,

Sorry for the long delay.

However, I can’t find any related metadata in the wp_postmeta table. It appears that none of the Genesis Custom Blocks store metadata in this table.

Where does Genesis Custom Blocks stores its metadata or any additional data related to the blocks?

GCB only stores block data in the custom post type of 'genesis_custom_block'. It doesn’t store post_meta.

• This reply was modified 11 months, 2 weeks ago by Ryan Kienstra.

Hi @najram,

Thanks for letting me know about that, you’re right that it’d be better if it’d work with the {{...}} syntax.

Hi @degas,

Yes, block_value() is the way to do that.

That will return the image ID, and from that, you can get a srcset for a different size.

Hi @themico,

Thanks for letting me know about that.

You’re right, the post field search doesn’t work well.

But unfortunately, we’re probably not going to fix that, as we’re not focusing on this plugin.

Hi @cvladan,

Yes, development on Pattern Manager has stopped.

Hi @reasondr,

Hm, it’s not what I thought. The blocks that are lost don’t exist at all on the back-end.

Have you ever lost other post types, like simple posts?

The GCB blocks are post types.

I’m not sure if I’ll be able to help.

Thanks!

All good, I’ve done that!

Hi @reasondr,

Thanks, I don’t think those warnings are errors are causing the problem. GCB doesn’t use jQuery, and the React errors are for rendering.

The block error on your site points to a deeper issue: that the block wasn’t registered (“Your site doesn’t include support for…”)

• This reply was modified 1 year, 1 month ago by Ryan Kienstra.