atomicblocks

Hey Jon,

1. I’ll have to look further into this. What’s happening is that the container is added, and immediately it’s selecting the paragraph block which is the default. The paragraph doesn’t get a focus box around it by default or when you are typing. Only when selecting it or interacting with it. So it’s acting how it should in that regard. I see your concern, but it will take some further thought about what the default state of the container should be.

2. I just noticed that wide/full toggle trick as well. That’s probably the best we can do here. I tried a few different ways to trigger the fix with CSS, but the toolbars are rendered outside of the block markup, so you can’t reliably target them. Nor would deprecating the block work or transitioning it.

Hi Doug,

We just released an update to the Post/Page Grid that might be a good use. Create each portfolio item as a page with featured images and text. Then, use the Post/Page Grid and select the Page post type, and then select the portfolio pages you want to display on the grid.

Just a heads up that we fixed the issue where toolbars are off-screen on full width containers, but the fix only works on newly created containers. There was no way to safely update those old containers unfortunately. Hope this helps!

Hi there,

Thanks for the suggestion! We’re currently improving the page grid feature of this block, adding the option to select specific pages for the grid.

I’ll add this feature request to the backlog and we’ll definitely consider it in the next post grid update!

Yep, it can take a little to show up, but it should be live shortly if you don’t already see it.

2.7.1 is also live now for those who need it. Thanks for your patience and sorry for the mishap!

Hey folks, thanks for the request! I’ve added this to our Github issues board as an enhancement. We’ll see about adding this in one of the next few updates!

Hey folks,

We’ve got a fix for this issue in the latest Atomic Blocks, 2.5.2! Go ahead and install the update and let us know if you see anything else. Thanks for all of your feedback and patience while we worked out a fix.

Hey folks,

We’ve got a fix for this issue in the latest Atomic Blocks, 2.5.2! Go ahead and install the update and let us know if you see anything else. Thanks for all of your feedback and patience while we worked out a fix.

Hey folks,

We’ve got a fix for this issue in the latest Atomic Blocks, 2.5.2! Go ahead and install the update and let us know if you see anything else. Thanks for all of your feedback and patience while we worked out a fix.

Hey folks, we’re still looking at this. It’s unfortunate that Polylang isn’t providing any support on the forums.

@tommnorm Would you be willing to share a login with us so we can diagnose further? If so, you can send to mike.mcalister at wpengine.com and I’ll take a look this morning!

@outcats85 You’d be surprised how many of the language switching plugins can break other plugins and themes.

Howdy folks,

Here is the code used to load styles in the Atomic Blocks plugin. Polylang seems to be preventing our styles from being output on the front end.

Yes you can revert back now. Thanks so much for letting us experiment on your site! We’ll keep you updated on the progress.

@jsoko @andreaborin @radimdolezal @tele0

We were able to get the styles back by disabling the Polylang plugin. It looks like this plugin is used on the sites mentioned here.

While we are still looking at possible solutions, it should be noted that we don’t do anything particularly unique with our loading of styles. We recently changed it to match the way the core block editor is loading styles.

You’ll want to reach out to Polylang and point them to this thread to see if they have any insights. We’ll be happy to share whatever info we have with them to expedite a fix.

@jsoko Thanks for being such a help! Mind if I temporarily deactivate a couple plugins to test?