Phil Johnston

I think you might be able to do that using this plugin:

https://www.ads-software.com/plugins/find-my-blocks/

Hey there,

Yes Font Awesome was removed in Genesis Blocks. If you need them, I would recommend installing this plugin:

https://www.ads-software.com/plugins/font-awesome/

Hey @bytammi

Try installing the Classic Widgets plugin to disable the new widgets screen in 5.8, and revert back to the original Widgets screen. It might fix your issues:
https://www.ads-software.com/plugins/classic-widgets/

I was in a lot of the conversations about this change, and the Core development team from Automattic was aware there were backwards compatibility bugs with this screen, and pushed it as an opt-out anyway. I pushed hard for them to make it opt-in, but didn’t have any success.

It’d probably be good for them to hear from real users who were impacted negatively by this. There’s a dedicated slack channel for this feature here:
https://wordpress.slack.com/archives/C01D71823PB

I definitely understand your concern about core updates, since breaking backwards compatibility is now a precedent. Moves like this fracture community trust in WordPress, and I hate to see it happen.

I’m glad to hear this plugin worked for you, and so sorry you had to install it at all.

Completely agree. I pushed hard for this to be opt-in before 5.8 was released, but the core development team from Automattic didn’t see it that way.

See conversations on Slack:
https://wordpress.slack.com/archives/C01D71823PB/p1624463727305700

I get that, not wanting to leave people behind. But I’m sure you can appreciate the subtle difference between “not leaving people behind” vs “thrusting a not-yet-wanted feature on someone without their consent”, especially if it has the potential to break things, as this change does.
Therefore, I really feel this should be an opt-in feature. That way, nobody is left behind, and nobody is forced into something when they aren’t ready. When you’re ready, opt-in! Easy.
The block editor has generally been regarded as a great thing (I agree that it is!), but with a terrible rollout that fractured the community, and broke trust.
I think it’s wise to learn from those mistakes, and make massive changes like this opt-in.

Unfortunately, I was not able to have any success with those conversations.

So sorry you had to spend time on this, and I’m glad to hear this plugin helped you.

@joetawfik Glad to hear it helped you! I’m sorry you had to deal with this.

You may want to check out the Classic Widgets plugin, which removes the new Widgets screen in WordPress, and puts things back the way they were before the 5.8 update. That will likely resolve the issue for you.

You can find that here:
https://www.ads-software.com/plugins/classic-widgets/

WordPress core knowingly broke a lot of backwards compatibility with the new widgets screen. For example, if any widget uses any admin function, it will fatal. That’s only one of many backwards compatibility breaks in this version of WordPress.

It’s unfortunate and frustrating that you had a working site, updated WordPress core, and now it’s broken. But that’s the reality. Unfortunately, it’s now your job to identify which plugin was broken by this core update, and contact the (likely small business) running that plugin that WP core broke, and hope they have the humanpower and resources available to fix what WordPress core broke.

@iberezansky That’s a good point. It looks like that documentation is out of date.

But yeah, you can just do this to enqueue react:

wp_enqueue_script( 'react' );

Genesis Blocks doesn’t use a custom version of react. Rather, it uses the one bundled with WordPress itself, which is currently 16.13.1. See that here:

https://core.trac.www.ads-software.com/browser/tags/5.7.2/package.json#L147

It’s best practice for WordPress plugins to use the bundled version to prevent these conflicts. This goes for any bundled library in WP core.

@douglasferraz89 The fix for this has been more difficult to completely nail down than it first seemed. However it is still on our list and we have code being actively written for it.

Hey Gary,

Just curious if the latest update resolved this for you.

Try this,

Add all 800 of your posts into a new category called “Blog”. Then, go to “Dashboard” > “Posts” > “Categories”. You should see that “blog” category listed there. When you hover over it, there should be a link to “view” the category.

Click on that.

That will give you the URL to view the category, and you can add that to your menu, or make a link on your homepage to it.

• This reply was modified 3 years, 5 months ago by Phil Johnston.

Hey Jeff,

Like I mentioned though, that would absolutely destroy your Google ranking, to load 800 posts on a single page load.

Another good approach might be to link to your theme’s blog page at the bottom of the grid, and only show about 10 posts/pages in the grid.

It looks like you actually already have an infinite scroll solution set up there. For example:

https://staging.homesecuritystore.com/category/home-safety

Where it says “Load more posts” at the bottom. That’s the type of solution I recommend here. So perhaps just add a link on your homepage below the postgrid, linking to a page like that, but that shows all of your posts, perhaps all in a single category.

• This reply was modified 3 years, 5 months ago by Phil Johnston.