Phil Johnston

My apologies for the lack of update on this. All team members assigned to this project have all been re-assigned to other projects, so the Pattern Manager project is likely to be ended. It just didn’t see the growth required to keep it as a project at WP Engine. I’m sorry about that, and the lack of communication.

We have decided to revert this change for now. An update will be going out later today. Thanks for the feedback all!

The main reason for the update here is because CURL has a vulnerability with the lower bundled versions of PHP, and we want to not recommend people use insecure versions of PHP. If you prefer to keep using an old version of PHP, you can also continue using an old version of Genesis Blocks. WordPress will block the update until your PHP version is updated.

I understand it’s confusing to have a minimum PHP version bump with no functional changes in our plugin. Ideally, I agree with what you are saying.

But this change is less about about functional changes in Genesis Blocks, and more about being compliant with security upgrades. My apologies for any frustration.

Can you try adding a TextDomain to your theme’s style.css file?

To do this, open the style.css file, and in the theme header, add a TextDomain, something like this:

Text Domain: frost

Then try creating a pattern with a custom category again. I think that should fix this for you.

This plugin does not handle anything related to synced patterns. It only helps you create non-synced patterns, which live inside your theme files.

Apologies for the confusion here, likely caused by core’s re-naming of reusable blocks!

Thanks Robert, we’ll make sure to fix this in the next release.

Thanks Tim,

It looks like this might be an actual bug in Pattern Manager for themes with no TextDomain. We’ll work on getting a fix out for this.

In the meantime, can you try adding a TextDomain to your theme’s style.css file?

To do this, open the style.css file, and in the theme header, add a TextDomain, something like this:

Text Domain: frost

Then try creating a pattern with a custom category again. I think that should fix this for you.

Thanks for all the helpful links and screenshots!

Hey Derek,

Sorry to hear this is happening! Just to double check, those errors typically appear if the plugin gets deactivated. Sometimes (though rarely) this can happen as part of an update in WordPress. Can we rule that out?

I’ve just tested this on a fresh installation with no other plugins, and I’m not seeing these errors.

Thank you for sending those steps! My first thought is that this might be a plugin conflict, as we aren’t seeing any other reports of this. If you’re able to try it with all other plugins disabled, that would help us narrow this down.

If that doesn’t help, in order for WordPress to show the contents of that error (like the line number of the file causing the problem), you’d have to enable WP_DEBUG mode for your WordPress install. You can do this by manually editing the wp-config.php, and setting WP_DEBUG to “true”. Here’s a guide on that:

https://www.ads-software.com/documentation/article/debugging-in-wordpress/

Hey Tim,

Sorry to hear! Do you happen to know what the fatal error message was?

@zerocore Would you be able to paste the block code that you’re using in this situation? We can then test it on our end to make sure it shows correctly in the previews.

Thank you for the report @marleenschonewille87

We will make sure this is fixed in the next update to Genesis Blocks

• This reply was modified 1 year, 9 months ago by Phil Johnston.

@craftsman Sorry to hear this happened for you. We attempted to replicate this issue but we aren’t seeing the same thing happen with PHP8.

If you happen to have it, can you paste any errors that might have appeared in your server PHP log?

Hey @mamafermenta,

The postgrid block doesn’t have any pagination support at this time. One way you could still achieve this is by adding a button below the grid and linking to your site’s blog page, or a specific category. Those get rendered by your theme itself and should support pagination.

Thanks @dpknauss! We have a fix that will go out for this in the next release nest week.