Justin McGuire

Nick,

This is great news! Thanks for for taking a look and finding a fix so quickly!

a:2:{i:0;s:20:”__return_empty_array”;s:18:”individual-teacher”;a:2:{s:4:”name”;s:18:”Individual Teacher”;s:11:”description”;s:0:””;}}

Thanks this code does work when in my theme’s functions.php file. I have a plugin that is basically doing the same thing code wise but it stops working after activating WPS Hide Login so I’ll have to investigate a bit more.

Thanks for the follow up. When looking at the slider preview generated by the Gutenberg Block everything looks like it was contained in an iframe. After some digging in the plugin I found a filter which appears to be responsible for dropping the styling into the iframe.

add_filter('metaslider_preview_styles', array($this, 'preview_styles'));

Tapping into that has allowed me to add my custom styling to the preview iframe and allows the backend Gutenberg block to match the front end now. I think this should resolve my issue unless there is some reason to avoid using that filter.

While you’re bringing that issue to the team you might want to also bring their attention to the issue with the section Monochrome Title and Text Columns Dark not being removed using the genesis_blocks_unregister_layout_component() method. Below is the code I was using to find and unregister all the sections before adding in my custom ones but for some reason that one won’t unregister. The only thing I can notice that is unique about it is the key for that section has “(dark)” at the end and it’s the only section / layout that has parenthesis in the key.

// Remove sections
$sections = genesis_blocks_get_sections();
foreach ($sections as $value) {
     genesis_blocks_unregister_layout_component( 'section', $value['key'] );
}

Ahh thank you for clarifying. Hopefully the team can either expand it to include layouts or provide us with another filter specifically for layouts. Thank you!

This seems like it’ll work but I am running into an issue where I can seem to white list the custom layouts I’m loading.

This is what I’ve got in my functions.php file. The custom layouts load fine until I add the filter then poof they get pulled out too.

function vi_custom_layouts() {
		// Ensure a proper version of Genesis Blocks is active before continuing.
		if ( ! function_exists( 'genesis_blocks_register_layout_component' ) ) {
			return;
		}

		// Tango
		genesis_blocks_register_layout_component(
			[
				'type'       => 'layout',
				'key'        => 'vi_tango_home_layout',
				'name'       => 'Tango Homepage',
				'content'    => "", //Some blocks here
				'category'   => [
					'business',
				],
				'keywords'   => [
					'homepage',
					'home',
					'landing',
				],
				'image'      => '', // Image here
				'collection' => [
					'slug'  => 'tango-homepage',
					'label' => 'Tango Homepage',
				],
			]
		);

	}
	add_action( 'init', 'vi_custom_layouts', 12 );
	
	add_filter(
		'genesis_blocks_allowed_layout_components',
		function( $layouts ) {
			return [ 'vi_tango_home_layout' ];
		}
	);


		
	

Any chance someone else has seen this kind of behavior?

@modernnerd No worries, I’ve gone ahead and reverted to the older GC 0.9.9 and everything is working great now. I’ll just keep an eye out for Woo 3.3.x. Thanks!

I’ve had a similar error occur this morning while updating a site. I tried updating Woo first to the latest version then updating GC to 0.9.10 but I still received a fatal error on the Woo pages.

This custom post type is being created by a 3rd party plugin “AgentPress Listings” which is used in conjunction with a Genesis WordPress theme. I was expecting to see the full list of “listings” within the dashboard of the site.

I’ve removed the role managing plugin from the site as your post indicated it might be causing a conflict, but the user with the “SEO Manager” role is still unable to save any of the Dashboard Options pages.

In fact I’ve tried disabling all plugins (except Yoast) and activating a core theme and that user still receives the “Cheatin’ uh? Sorry, you are not allowed to manage these options.” error page when trying to save the Yoast Dashboard options page.

Should “SEO Mangaer” roles not be able to see the dashboard options pages at all is that the issue? (/wp-admin/admin.php?page=wpseo_dashboard)

Thanks, like the other user having this issue I restored to using the shortcodes to block the content since the plugin wouldn’t block it natively even after disabling all other plugins and using the base twentysixteen theme on my staging environment.

https://aveyronhomes.staging.wpengine.com/employees-only/

Thanks, like the other user having this issue I restored to using the shortcodes to block the content since the plugin wouldn’t block it natively even after disabling all other plugins and using the base twentysixteen theme on my staging environment.

https://aveyronhomes.staging.wpengine.com/employees-only/