Thread

Have gone through the documentation but not found a solution.

{exp:channel:entries channel="movies"}
        
        <div class="category">
            {categories}
                        <a href="http://{path=/movies/wiki}">{category_name}</a>
            {/categories}                                
              </div> <!-- end category -->
              
        {/exp:channel:entries}

This is spitting out all of the categories within the movies channel. I want only the one(s) for each movie entry. This is in a template that outputs multiple movie entries, each of which has one or multiple categories attached to it.
Could anyone please help? Am I missing something?

I’m sure there’s a less hacky way of doing it, but, this is what we do…

{exp:query sql="SELECT exp_categories.cat_name AS cat_name, exp_categories.cat_url_title AS cat_url FROM exp_categories, exp_category_posts WHERE exp_categories.cat_id = exp_category_posts.cat_id AND exp_category_posts.entry_id = '{entry_id}'" backspace="2"}<a href="http://{path=%27/template-group/category/{cat_url">{cat_name}</a>, {/exp:query}

That’ll output a comma separated list of the categories an entry belongs to.  You’ll have to enable the query module if it isn’t already.

Take a look at the absolutely fantastic GWcode Categories add-on. There literally isn’t another add-on like this one.

It will do exactly what you need here and an absolute ton more.

Best wishes,

Mark

You shouldn’t need an addon for this.  Your code sample should be correct - the purpose of the {categories} looping variable pair is to do exactly what you are looking for - output the entries a single category is assigned to.

As a test try:

{exp:channel:entries channel="movies"}
{title} <br / >     
       {categories}<a href="http://{path=/movies/wiki}">{category_name} | </a>{/categories}                                     
<hr >
              
{/exp:channel:entries}

The {exp:channel:categories} tag is for outputting all categories in a channel.

Oops sorry Mike is quite correct. I had completely mis-read what you were after.

That said the add-on I linked to is absolutely fantastic and will definitely allow you to do more than you can ever do with the built-in categories tags.

Best wishes,

Mark

Your code sample should be correct - the purpose of the {categories} looping variable pair is to do exactly what you are looking for - output the entries a single category is assigned to.

Yes it was Mike. Awesome - I got exactly what I wanted. As a newbie I keep separating channel entries related information from category related info. Would it be right to assume that both are served up in the same bucket? As in are both available on the same page with the use of ee’s channel entries tag?

@Bowen: I already have the GWcode plugin installed, professor. Would like to know how to do what I am doing right now using the plugin too. Went through the examples but most of them seemed like they were about spitting category trees. How would I output entry-category related information?

@NickBenson - Thanks for the advanced hack - I got to start learning the query module too. This snippet should get me started.

Yes it was Mike. Awesome - I got exactly what I wanted. As a newbie I keep separating channel entries related information from category related info. Would it be right to assume that both are served up in the same bucket? As in are both available on the same page with the use of ee’s channel entries tag?

It’s a bit of a paradigm jump, but you need to understand that anything in EE’s content database is available on any page.  Pages don’t store content.  Pages present content - through the templates that you code.  Templates are the connection point between EE content and final “pages” - but they are entirely defined by you and the EE tags you use.

Conceptually entries do and don’t live in the same bucket as categories.  Entries get categorized, but a category group can be applied to more than one channel, so the same categories could be used in multiple buckets.

Categories are simply a filtering mechanism - a way to select a sub-set of entries in a channel, with some meta to describe the filter.

Pages don’t store content.  Pages present content - through the templates that you code.  Templates are the connection point between EE content and final “pages” - but they are entirely defined by you and the EE tags you use.

Now that’s exactly the kind of insight I was looking for. You should teach man - oops!! you already do 😊

Thanks Mike. Excellent insight as always. Feel free dgink, to start anew thread if you have any more questions