Andrea Gandino

Hello folks, sorry for the delay of this response, but the notification system didn’t properly notify us of your message.

At the moment, the Free version of Advanced Columns works with two Media Query breakpoints.

The Pro version of the plugin, on the contrary, does not have this specific limitation, and you can add multiple Media Query breakpoints.

Hello there, sorry for the delay of this response, but the notification system didn’t properly notify us of your message.

The error has now been resolved. You can test this by updating the plugin to the latest version.

Thanks again for your patience!

Hi there, I believe that’s the default behavior for blocks that are server-side rendered and that contain inner blocks at the same time.

We’ve tested your use case in a different context, without Grids, and found out that what happens is the same: the renderedHtml field for such blocks already contains the whole rendered HTML, comprising inner blocks’ markup as well.

My advice is to handle the frontend rendering of grids/area blocks differently, only outputting the renderedHtml value, and not recursively parse their inner blocks.

Hope this helps!

Hi @fotoduda,

we’ve just released version 1.3.5, that should fix the issue.

Ah, now we see!

We’ll release an update to the plugin later today, and bring the value back to auto also in the Block Editor screen.

Thanks for your feedback!

• This reply was modified 2 years, 9 months ago by Andrea Gandino.

Hi @fotoduda,

what browser are you using? Also, have you tried clearing the browser’s cache?

Let me know!

Hi there,

we have released a new update this morning, version 1.3.3. Would you mind trying out that version, and see if the error persists?

Thankyou!

Hi @fotoduda & @k3ob,

we have reverted a change introduced in version 1.3.0; please update to version 1.3.1, in order to have the display of the grid restored back to its previous appearance.

Hi Jaime,

thank you for using Grids!

We’ve just released an update to Grids (version 1.2.28) that allows developers to change the units being used in size controls in Sections and Areas through a filter in your plugin or theme.

For example:

add_filter( 'grids/config', function( $config ) {
	$config[ 'general' ][ 'size_units' ] = array(
		array( 'label' => 'em', 'value' => 'em' ),
		array( 'label' => 'px', 'value' => 'px' ),
		array( 'label' => '%', 'value' => '%' ),
		array( 'label' => 'rem', 'value' => 'rem' ),
		array( 'label' => 'vh', 'value' => 'vh' ),
		array( 'label' => 'vw', 'value' => 'vw' ),
	);
    
	return $config;
} )

Putting the ems array as first item in the configuration array will make it the default one when creating a new section with Grids.

Please refer to the config.php file in the main folder of Grids to get a list of available configuration options.

Sorry about the log to console, we’ll fix that!

In regard to not saving the gutter value, that’s a meta field for the post type, so you’ll need to make sure that your Custom Post Type has support for custom-fields.

Hey @gdalrymple,

we have just released an update to the plugin that should fix the issue you reported. Can you confirm that?

Thanks,

Andrea

Hey @strarsis,

we have just released an update to the plugin that should fix the issue your reported. Can you confirm that?

Thanks,

Andrea

Hi @hazynite,

thanks for trying out Grids!

Unfortunately, we haven’t tested Grids with the Toolset Blocks. How are you building the AJAX slider exactly, using the tools provided by Toolset Blocks?

Hi there @philsener,

we were able to replicate the issue on our development machines; we’ll definitely include a fix for this in the next update of the plugin!

Thank you for reporting this issue!

Hi @alexsmacd,

thank you for trying Grids out!

We have been able to replicate the issue on our local installs, and we’ll likely add a fix for it in the next update to the plugin!