Because $limit = 0 usual means no limit there is hard to change it in J3.x.

It can help only in the blog:

diff --git a/components/com_content/models/category.php b/components/com_content/models/category.php
index 50c66d0efa..a4f4128daa 100644
--- a/components/com_content/models/category.php
+++ b/components/com_content/models/category.php
@@ -190,6 +190,13 @@ class ContentModelCategory extends JModelList
                if (($app->input->get('layout') === 'blog') || $params->get('layout_type') === 'blog')
                {
                        $limit = $params->get('num_leading_articles') + $params->get('num_intro_articles') + $params->get('num_links');
+
+                       if ($limit === 0)
+                       {
+                               // We want 0 articles but 0 means no limit
+                               $limit = -1;
+                       }
+
                        $this->setState('list.links', $params->get('num_links'));
                }
                else

@csthomas

So you are saying that limit zero for DB model

• means 'retrieve all'

but then

• some com_content layouts will show zero items (blog layout)
• and all other layots will show all of them

Since the category DB model already has special handling for blog layout as you are showing above
I think your fix suggestion is valid

If this is OK then I will make PR when I have more time.

That sounds like a good fix, simple and effective :)

The fix is not complete because there is a second query SELECT COUNT(*)..., which still is executed.

@AndySDH Can you confirm this issue still exists in J3?

Yup still an issue

Closing this because it is expected behaviour.

To be a bit more specific: A value of 0 means no limit. A Category Blog Menu Item is for displaying articles of a category. If you want to show only the category description you can create a special view by copy the view to your template and remove the showing of articles.

@rdeutz Sorry but that's stupid. If 0 meant no limit, then entering 0 would show all articles. But it doesn't.

Instead, entering 0 shows 0 articles. While still loading all their data in the background as if it was showing all.

It should be either one way (show 0 articles, load 0 data), or the other (show & load all articles)

Currently it's inconsistent and a mess

#32612 new way to get this issue.

It happends on my site. I'm using com_content to store articles, but doesn't use it to display. If someone know this issue, he can easily break my site. So i have to block access to com_content.

So annoying.

For me it is a missuse of the Category Blog for something that it is not made for. But I am open to look at a PR so that we can check what the side effects are.

@rdeutz

For me it is a missuse of the Category Blog for something that it is not made for.

Maybe, but then it should be made consistent when you enter the '0' value. Right now it's not even consistent, as explained in my previous post and opening post.

But I am open to look at a PR so that we can check what the side effects are.

Then maybe don't go around closing tickets on your own volition? :) Otherwise, a PR will never be made.

Like it or like it not, it's my job to make decisions on issues. PRs can be made without an issue, but seems it is not so important, even in 4 years we haven't seen a PR.

PRs can be made without an issue

Nobody will make a PR if there's no issue opened for it.

Nobody will make a PR if there's no issue opened for it.

Maybe, same as the last 4 years.

Nobody will ever see this again if this gets closed.

@Quy @SharkyKZ @richard67

This is my last message about this issue if this gets closed, why should I care if you don't care about improving Joomla yourself.

PR here #32626 . But it is an backward incompatible change, so I don't think it will be accepted :) .

@joomdonation Why is this issue and PR closed? This is still an issue in Joomla 4 and 5...

Reopening as the pull request has been closed.