JiveDig

FWIW, here is the code I’m currently using to remove the scripts.

/**
 * Remove scripts and styles.
 *
 * @return void
 */
add_action( 'wp_print_styles', function() {
	$scripts = [];
	$styles  = [];

	// Single posts/pages/cpts.
	if ( is_singular() ) {
		$post = get_post();

		if ( ! has_block( 'icgb/image-compare', $post ) ) {
			$scripts[] = 'icgb__image-compare-viewer-js';
			$scripts[] = 'icgb__plugin-js';
		}
	}

	if ( $scripts ) {
		foreach ( $scripts as $handle ) {
			wp_dequeue_script( $handle );
		}
	}

	if ( $styles ) {
		foreach ( $styles as $handle ) {
			wp_dequeue_style( $handle );
		}
	}

	// global $wp_scripts, $wp_styles;
	// printf( '<pre>%s</pre>', print_r( $wp_scripts->queue, true ) );
	// printf( '<pre>%s</pre>', print_r( $wp_styles->queue, true ) );

}, 9999 );

Updated to 4.9.9, and after flushing all caches it seems to have fixed it for me. I’m not seeing the license check on every page load, or if it is, it’s much faster now. Thanks ??

FWIW the developer was notified by a security team and has updated with a patch shortly after.

Hi Andrew, this is the lead dev of Mai Theme. Our blocks are typically structured like this:

/wp-content/plugins/mai-engine/lib/blocks/{block-name}/block.json

Also, block.php is at the same level. For one set of blocks like mai-post-grid, we have post-block.json and term-block.json in that directly.

We call/load the blocks the ACF recommended way, via: https://www.advancedcustomfields.com/resources/acf-blocks-with-block-json/

Thanks.

• This reply was modified 1 year, 5 months ago by JiveDig.

@redyan I’m hitting the same thing on a custom theme. Did you ever figure this out? I’ve hit this on another site and it has me looking for an alternative.

When I dump the $variation variable, I get:

Array
(
[name] => woovr_name[16337]
[label] => Custom name
[value] =>
[placeholder] =>
[class] => short
[style] =>
[wrapper_class] =>
[type] => text
[desc_tip] =>
)

There is no key/index of id.

Seems like there should be a wp_parse_args() there or something to make sure all required attributes are there.

Same issue here, but not all content, just pages. I selected menu items but it’s showing pages in the generated file.

• This reply was modified 3 years, 6 months ago by JiveDig.

Hey Chouby,

I’m the lead dev of the theme in question. The issue we’ve hit is that we use this CPT as global content areas in the theme, similar to widget areas, but so we can use blocks. I’d like to add Polylang support but hit a few walls. The main issue here is that the CPT is queried by slug via get_page_by_path(). Even if I make the CPT translatable via your filter I’m still unable to check and swap the translated version if it’s available. Maybe you can point me in the right direction?

Getting the same error when importing here. Hard to see the error actually, but digging through it in console, I get:

call_user_func_array() expects parameter 1 to be a valid callback, function 'menusUnfilteredUpload' not found or invalid function name

FWIW I exported the menu from a multisite subsite, and imported into a different multisite subsite. Local to live, totally different domains.

• This reply was modified 4 years, 1 month ago by JiveDig. Reason: forgot to check follow-up
• This reply was modified 4 years, 1 month ago by JiveDig.

+1 on scoping. The entire bootstrap CSS library seems excessive IMO and likely causing other issues as well, but either way it needs to be scoped.

Just started using this plugin and it’s great. Came looking if anyone asked for this already, and you did only 4 days ago ??

I love the simplicity of this plugin but would welcome one more feature. I may just roll my own on top of this, but it would be cool to see it in the core plugin.

When we’ve seen this issue the /wp-admin/ link whitescreens but you are still able to login by directly visiting the login url example.com/wp-login.php. Note the wp-login.php instead wp-admin. Hope that helps.

Hey Jean, Mike from Mai Theme here. You’re getting the same error as the OP because our theme and the classic editor add-on seem to rely on the same dependency installer. We have a fix for the theme error by updating our Mai Theme Engine plugin to the latest (v1.10.4.1 at the time of posting this). That should fix it for you. Feel free to ping us via https://support.bizbudding.com if you need anything else.

??

Just found the official source of what caused it to break. This site had a comment with some broken/malformed HTML. I edited/fixed the comment and the issue went away. Still seems like it’d be safe to add the isset checks but the error is gone at least.

I’ll close this, but feel free to merge the PR. Thanks.

Submitted PR. Let me know if you’re interested in merging this, otherwise I need to come up with another solution. https://github.com/foliovision/thoughtful-comments/pull/36