Split taxonomies on different pages

To show all the Products, I’ve created taxonomy-activity.php which already shows all the products that have an activity taxonomy.

That’s not what taxonomy-activity.php is for. That template is the template that is used for displaying posts for each activity taxonomy term. So if you view Museum activity, that template will be used to display all Museum products, or if you view the Food & Drink activity the same template will be use to view Food & Drink products.

The template itself should not be choosing which posts to display. WordPress has already done that. All this template should be used for is presenting those posts. To loop through the products that WordPress has already query, you need to just use The Loop, not a custom query:

<?php 
if ( have_posts() ) : 
    while ( have_posts() ) : the_post(); 
        // Display product content
    endwhile; 
endif; 
?>

So WordPress will automatically make an archive available for each activity taxonomy which displays products that belong to it. You should not need to create a page or template for each one.

The same applies to post types. When you register a post type, like Products, it WordPress will automatically make an archive of all Products available if has_archive is set to true or a slug. To create a unique template for this archive, you need to create archive-product.php. This will then automatically be used at https://example.com/products/, where products is the post type name, or the slug pass to has_archive.

So what you need is archive-product.php which will be used when viewing all products at something like https://example.com/products/, and taxonomy-activity.php which will be used when viewing each activity links like https://example.com/activity/museum/ or https://example.com/activity/attractions/, as examples.

When is comes to adding FacetWP support for filtering these archives, you will need to consult their documentation, since 3rd-party plugins are off topic here, but when it comes to the required built in WordPress templates you need them set up like I described as a starting point.

Hata!: SQLSTATE[HY000] [1045] Access denied for user 'divattrend_liink'@'localhost' (using password: YES)