Zax

Thanks for adding $type argument to blocksy:hero:after (and blocksy:hero:before) in latest update. Unfortunately blocksy:header:after doesn’t seem to be covered by this change, is it still planned?

I understood that the HEADER action wouldn’t be called when HERO is disabled but if its not the case then its fine.

I don’t call the hero action when hero is disabled, although from what see in code the title with meta is considered “hero” internally, so type-1 is “disabled” and type-2 enabled, its never truly disabled? Sorry to bother you with these questions.

Any ETA when we can expect next update? Weeks, days, month?

1. I checked the result of blocksy_get_page_title_source and it wasn’t null, at least for search and blog pages. These are some returned values (it returns customizer even though I wasn’t in customizer, not sure if intended):

customizer,single_page
customizer,single_blog_post
customizer,blog
customizer,search
customizer,categories

The last 3 page types (blog, search, categories) returned NULL hero-type. All examples returned the correct hero-type in customizer. The page title was enabled for all of them, disabling page title makes it return NULL everywhere even in customizer.

2. I can’t rely on default return value here because it would be pure guessing (I can’t predict if some random blog post wasn’t set to different type) – correct me if I’m wrong please.

I need some reliable method that works with unique pages, blog, search, archive etc. All my test results were with page titles enabled BUT I plan to have title disabled for some random pages, is there no way to get the correct result if “page title is disabled”?

3. Hero type as an argument to the blocksy:hero:after action could work but I’m also using blocksy:header:after and it wouldn’t make sense adding hero-type to some unrelated header action/event?

add_action('blocksy:header:after', 'add_content_after_header', 20);

function add_content_after_header() {

	$type = blocksy_akg_or_customizer('hero_section', blocksy_get_page_title_source());
	
	if ($type == 'type-1') {	
		$breadcrumbs_builder = new Blocksy_Breadcrumbs_Builder();
		echo $breadcrumbs_builder->render();	
	}
}

add_action('blocksy:hero:after', 'add_content_after_hero', 20);

function add_content_after_hero() {

	$type = blocksy_akg_or_customizer('hero_section', blocksy_get_page_title_source());
	
	if ($type == 'type-2') {	
		$breadcrumbs_builder = new Blocksy_Breadcrumbs_Builder();
		echo $breadcrumbs_builder->render();	
	}
}

If page name is inaccessible by other means (with page title is disabled), perhaps adding page-title as additional argument for some events would make more sense?

Exactly what I needed, thanks! Added padding-top: 20px and it looks good now.

I modified the code snippet from my first post to only work on type-2 style:

add_action('blocksy:hero:after', 'add_content_after_hero', 20);

function add_content_after_hero() {

	$type = blocksy_akg_or_customizer('hero_section', blocksy_get_page_title_source());
	
	if ($type == 'type-2') {	
		$breadcrumbs_builder = new Blocksy_Breadcrumbs_Builder();
		echo $breadcrumbs_builder->render();	
	}
}

Wondering if it wouldn’t be better to generate breadcrumbs for type-1 separately on different action/event? blocksy:head:end ? Not sure how it would work with sticky header though.

Hey, this isn’t “blocks hooking” feature available in pro version. I’m just hooking manually with code snippets by registering to actions. 🙂

Yes thanks, its fixed in latest update.

Thanks, I will most likely use your second answer as workaround (hopefully temporarily), but I think that its more of a bug than feature and should be passed to dev team for fixing.

For example switching to Breadcrumb NavXT engine detects the page name correctly, but I would rather not use additional dependencies.