[SiFor]

In vb 4 this was fairly simple for somebody like me with limited knowledge but in vb5 its a different story.

This looks to be the section in the header template:

	<vb:if condition="$page['crumbs']">
		{vb:set breadcrumbSchema.itemprop, breadcrumb}
		<ul id="breadcrumbs" class="h-clearfix" {vb:schema {vb:raw breadcrumbSchema}}>
			<li class="crumb ellipsis"><a class="crumb-link" href="{vb:raw baseurl}/">{vb:phrase home}</a></li>
			<vb:each from="page.crumbs" value="crumb">
				<vb:if condition="isset($crumb['phrase']) AND !empty($crumb['phrase'])">
					{vb:set crumbTitle, {vb:rawphrase {vb:raw crumb.phrase}}}
				<vb:else />
					<vb:comment><!-- Since we don't want phrase placeholders to be escaped, we escape user titles here. --></vb:comment>
					{vb:set crumbTitle, {vb:raw crumb.title}}
				</vb:if>
				<li class="vb-icon separator"></li>
				<li class="crumb ellipsis"><vb:if condition="$crumb['url']"><a class="crumb-link" href="{vb:raw baseurl}{vb:raw crumb.url}">{vb:raw crumbTitle}</a><vb:else />{vb:raw crumbTitle}</vb:if></li>
			</vb:each>
		</ul>
	<vb:else />
		<vb:comment>
			We still need the #breadcrumbs element (even though empty) to avoid having multiple CSS rules to deal with different scenarios
			where adjacent elements - breadcrumbs, channel-subtabbar, notices, announcements are available, visible, hidden or empty.
			Used div instead of ul to prevent having an empty ul which is invalid in XHTML 1.0 Strict (though valid in HTML5).
			Though we are currently using HTML5 doctype, using an emtpy div will ensure that this will validate even if we change the doctype in the future.
		</vb:comment>
		<div id="breadcrumbs"></div>
	</vb:if>