Search Results

I'd say you want to look at the relations https://craftcms.com/docs/relations#the-relatedTo-param You would then use craft.entries.section( 'sectionHandle' ).relatedTo( category ) to grab all entries …

I would add the brand category field to the assets field set. This way you can add brands to images and use .relatedTo to find them. <ul> {% for category in craft.categories.group( 'brands' ) %} …

You should be able to use {{ entry.categoryFieldHandle[0].slug }}. The [0] simply grabs the first category in the field. You will need to make sure there is always at least one category allocated to …

An example of how this would be implemented in the above use case would be as follows {% set categories = craft.categories.slug( 'not preferential' ) %} {% set entries = craft.entries.relatedTo( categories … ( 'sectionHandle' ).relatedTo( categories ) %} …

You can then output each product grouped by category with something along the lines of: {% for cat in categories %} {% set products = products.relatedTo( cat ) %} {% for product in products %} …

You can use the relatedTo param on craft.tags like you can with any Element inside Craft. All Elements inside Craft can be related to one another. There is a .relatedTo parameter available on all of …

The Twig code to fetch entries occurs on page load - Your JS code will run after the page loads and won't be able to update/fetch new entries. Instead, you should look at building a system that uses q …