Support Forums

This is *not* a WooCommerce issue. This is an issue in Boss.

WooCommerce has two ways to handle templates, the right way, and the fast way.

The right way, is /themes/yourtheme/woocommerce/…… with templates modified from /plugins/woocommerce/templates. By doing it this way, all pages can be properly customized.

The fast way, is /themes/yourtheme/woocommerce.php. This is what Boss does. The problem with woocommerce.php is it’s a “catch all” for WooCommerce, and does not allow any customization of actual template files. It will break a lot of WooCommerce plugins that rely on customizing the archive-products.php, including the one I author, because you don’t have all the right hooks/actions to play with.

http://docs.woothemes.com/document/third-party-custom-theme-compatibility/

So, the problem is Boss related, not WooCommerce related, unfortunately……

Most likely because you have copied it into /themes/yourtheme/archive-product.php, which is the wrong location. The correct location would be /themes/yourtheme/woocommerce/archive-product.php. That’s my guess based on your first posts screenshot showing it in the wrong directory.

Oddly, that’s a completely different problem, but with the way Boss uses woocommerce.php to override it, it wouldnt matter if it was in the right directory for Boss anyway.

1.) Test with TwentyFifteen, not TwentyThirteen.

2.) The issue will always be Boss related, because of Boss using woocommerce.php, which overrides archive-product.php.

These are two separate issues, they just happen to be the same problem, but with two completely separate reasons why. 🙂

If you cant get it to work with TwentyFifteen, you’re either doing it wrong (most likely) or FacetWP has a bug (very unlikely).

@matthewjamesboyd1984 just found this tutorial for placement: https://v4.datafeedr.com/documentation/580
We also follow the directions here: http://docs.woothemes.com/document/third-party-custom-theme-compatibility/

You could try removing woocommerce.php from the parent theme and then add this to functions.php:

remove_action( 'woocommerce_before_main_content', 'woocommerce_output_content_wrapper', 10);
remove_action( 'woocommerce_after_main_content', 'woocommerce_output_content_wrapper_end', 10);

add_action('woocommerce_before_main_content', 'buddyboss_theme_wrapper_start', 10);
add_action('woocommerce_after_main_content', 'buddyboss_theme_wrapper_end', 10);

function buddyboss_theme_wrapper_start() {
  echo '<div id="primary" class="site-content">
		<div id="woo-content" role="main">';
}

function buddyboss_theme_wrapper_end() {
  echo '</div><!-- #content -->
	</div><!-- #primary -->';
}

NOTE: Not tested and you may need to remove the woo-content div.

@matthewjamesboyd1984 nope, this is upgrade safe, the only thing you would need to do is remove the woocommerce.php file every time you update the Boss theme, but if this solution does work for you then we can implement it into the theme and remove the woocommerce.php file.