linux4me2

@whatthecup You can find the instructions to create a child theme here. There’s a lot of detail there, but it’s not as complicated as it seems, and almost always a good idea.

Without knowing what modifications you’ve made, I can’t say what you’ll lose, but, for example, if you have added some custom CSS to Appearance -> Customize -> Additional CSS, you can just copy it and paste it into your child theme’s style.css and you’ll be good to go. Other than that, as noted in the article:

You may need to re-save your menu from Appearance > Menus and theme options (including background and header images) after activating the child theme.

It takes a little work the first time, but the whole point in having a child theme is that your modifications are preserved when you update the parent theme, so it will save you work in the long run, and enables you to make all kinds of custom changes easily.

One way to do this is to create your own shortcode and add the following to your child theme’s functions.php:

add_shortcode('custom_create_category_list', 'custom_create_category_list_fxn');
function custom_create_category_list_fxn() {
  $args = array(
  'orderby'  => 'name',
  'order'    => 'asc',
  'hide_empty' => 1  // Change this to 0 to show empty categories.
   );
  
   $product_categories = get_terms( 'product_cat', $args );
  
   if(!empty($product_categories)){
   echo '<ul>';
     foreach ($product_categories as $key => $category) {
        echo '<li>';
        echo '<a href="'.get_term_link($category).'" >';
        echo $category->name;
        echo '</a>';
        echo '</li>';
      }
   echo '</ul>';
   }
}

Then, on the page where you want the list to appear, you’d add the following in a Shortcode Block:

[custom_create_category_list]

You didn’t mention if you only needed this to handle top-level categories or subcategories, too. This code just handles top-level categories.

@polycellroot You’re welcome, though I’m not sure I helped. There are a couple things I should pass along.

First of all, if you use the external/affiliate products to link to your landing page, you’re going to need to have a way for customers to purchase the products from the landing page when they arrive there. To do that, you’d have to create duplicate products of simple or variable product types with their catalog visibility set to “hidden” so they only show up on the landing page, not on the Shop page or search.

An alternative that doesn’t require duplicate products would be to set a custom field called something like “landing_page_url” for the products you want to link to a landing page, then set the value of the field to the URL of the corresponding landing page. You can then use code to set the link to the product image when the products are displayed outside of the landing page to that URL if the meta value is present for a product.

Have you seen this post?

It seems like there should be an action that would govern both the initial display in the shop page and the filters. Maybe the action in the accepted answer, “woocommerce_product_query_meta_query,” might do it? It looks like it would alter any query passed to the shop page, and it’s a pretty simple way to handle your “sell_product_online” meta key.

Hi @oringeverything

You’re welcome! I’m glad you got it working.

There is a hook (action) called “woocommerce_order_status_changed” that it looks like you could use in your child theme’s functions.php to check the order status, get the product id(s) involved in the order, and then run some PHP to communicate to OtherStore2.

Ordinarily, WooCommerce uses an AJAX call to set the available variations when you select a variation on which subsequent ones are dependent. For example, when you select the Model on your sample page, WooCommerce sends an AJAX call to the server to populate the Sub-model with the correct options. However, if you exceed the default 30 variations, WooCommerce doesn’t use AJAX, and you end up with options that don’t exist in the drop-down boxes, and your customers see the confusing “Sorry, this product is unavailable. Please choose a different combination.”

The fix for that issue is to increase the default number of variations that are allowed to generate an AJAX call. To do that, figure out what your maximum number of variations will be, and add the following code snippet to your child theme’s functions.php:

add_filter( 'woocommerce_ajax_variation_threshold', 'wc_ajax_variation_threshold' );
	function wc_ajax_variation_threshold() {
	    return 150;
	}

Change the “150” in the snippet to something higher than your maximum number of variations.

Keep in mind that WooCommerce added the default of 30 to reduce the load on your server. If your server is underpowered and the threshold is set too high, you can end up with problems.

Give that a try and see if it fixes both issue #1 and issue #2.

Adding the following code snippet into your child theme’s functions.php should do the trick:

add_filter('woocommerce_get_availability', 'custom_get_availability', 1, 2);
function custom_get_availability($availability, $product) {
  if ($availability['availability'] == '') {
    $availability['availability'] = __('In Stock', 'woocommerce');
  }
  return $availability;
}

This was discussed in detail in this post.